Re: t1040 IFC flash driver Extended Chip Select

On 07/07/2016 04:49 PM, Daniel Walker wrote:=0A=

On 07/07/2016 02:23 PM, Scott Wood wrote:=0A=

quoted

=0A=
I suspect that add the usage of cspr_ext into the driver would fix the=

=0A=

quoted

issue we have. It reads like you would find that acceptable ?=0A=
What specifically is the problem you're having?  Is it that CSPR_EXT is=

=0A=

quoted

not getting written to, and thus the device does not appear at the=0A=
address that it should?=0A=
=0A=
Or is the driver matching incorrectly?  The only way the driver's lack=

=0A=

quoted

of using CSPR_EXT to match would be a problem would be if you have=0A=
multiple chipselects with the same address in the lower 32 bits, and=0A=
only CSPR_EXT distinguishing them.  Since you proposed a device tree=0A=
binding that assumes all devices have the same CSPR_EXT, I doubt that's=

=0A=

quoted

the case, so I doubt adding CSPR_EXT matching to the driver will solve=

=0A=

quoted

your problem.=0A=
=0A=
-Scott=0A=
=0A=

=0A=
I didn't do the debug on this. From my perspective it's either flash =0A=
works, or it doesn't work. We need the code below for it to work,=0A=

=0A=
Adding CSPR_EXT matching to the driver will not accomplish the same=0A=
thing as that code.=0A=
=0A=
-Scott=0A=
=0A=