[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3dccc5af-2df1-8374-e4e8-0a8b9ea1ae99@ti.com>
Date: Tue, 1 May 2018 14:55:50 +0530
From: Sekhar Nori <nsekhar@...com>
To: Bartosz Golaszewski <brgl@...ev.pl>,
Kevin Hilman <khilman@...nel.org>,
Russell King <linux@...linux.org.uk>,
Boris Brezillon <boris.brezillon@...tlin.com>,
Richard Weinberger <richard@....at>,
David Woodhouse <dwmw2@...radead.org>,
Brian Norris <computersforpeace@...il.com>,
Marek Vasut <marek.vasut@...il.com>,
Tony Lindgren <tony@...mide.com>,
Krzysztof Kozlowski <krzk@...nel.org>
CC: <linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <linux-mtd@...ts.infradead.org>,
Bartosz Golaszewski <bgolaszewski@...libre.com>
Subject: Re: [PATCH 01/12] mtd: nand: davinci: store the core chipselect
number in platform data
On Monday 30 April 2018 01:54 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bgolaszewski@...libre.com>
>
> 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 filed - core_chipsel - to the platform_data.
s/filed/field
> Subsequent patches will convert the platforms to using this new field.
Can you add a comment for this new field too, like how we have for most
other fields?
Curious on what 'core' in core_chipsel means. Something to do with
chip-select offset we have on DA850?
>
> Signed-off-by: Bartosz Golaszewski <bgolaszewski@...libre.com>
Thanks,
Sekhar
Powered by blists - more mailing lists