mtd: rawnand: davinci: store the core chipselect number in platform data
We have the 'ti,davinci-chipselect' property in the device tree, but when using platform data the driver silently uses the id field of struct platform_device as the chipselect. This is confusing and we almost broke the nand support again recently after converting the platform to common clock framework (which changed the device id in the clock lookup - the problem is gone now that we no longer acquire the clock in the nand driver. This patch adds a new field - core_chipsel - to the platform_data. Subsequent patches will convert the platforms to using this new field. Acked-by: Boris Brezillon <boris.brezillon@bootlin.com> Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com> Signed-off-by: Sekhar Nori <nsekhar@ti.com>
This commit is contained in:
parent
60cc43fc88
commit
bde1a3d846
1 changed files with 10 additions and 0 deletions
|
@ -56,6 +56,16 @@ struct davinci_nand_pdata { /* platform_data */
|
|||
uint32_t mask_ale;
|
||||
uint32_t mask_cle;
|
||||
|
||||
/*
|
||||
* 0-indexed chip-select number of the asynchronous
|
||||
* interface to which the NAND device has been connected.
|
||||
*
|
||||
* So, if you have NAND connected to CS3 of DA850, you
|
||||
* will pass '1' here. Since the asynchronous interface
|
||||
* on DA850 starts from CS2.
|
||||
*/
|
||||
uint32_t core_chipsel;
|
||||
|
||||
/* for packages using two chipselects */
|
||||
uint32_t mask_chipsel;
|
||||
|
||||
|
|
Loading…
Reference in a new issue