From: Roger Quadros <rogerq@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
tony@atomide.com
Cc: robh+dt@kernel.org, grygorii.strashko@ti.com, nm@ti.com,
lokeshvutla@ti.com, nsekhar@ti.com, miquel.raynal@bootlin.com,
devicetree@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 8/8] memory: gpmc-omap: "gpmc,device-width" DT property is optional
Date: Fri, 17 Sep 2021 10:17:10 +0300 [thread overview]
Message-ID: <d574837c-b42a-53be-7885-9feb7183ce96@kernel.org> (raw)
In-Reply-To: <35643319-e3b0-bde1-c51b-57c3b5474146@canonical.com>
On 16/09/2021 13:48, Krzysztof Kozlowski wrote:
> On 15/09/2021 11:11, Roger Quadros wrote:
>> Hi Krzysztof,
>>
>> On 07/09/2021 15:36, Krzysztof Kozlowski wrote:
>>> On 07/09/2021 13:32, Roger Quadros wrote:
>>>> Check for valid gpmc,device-width, nand-bus-width and bank-width
>>>> at one place. Default to 8-bit width if none present.
>>>
>>> I don't understand the message in the context of the patch. The title
>>> says one property is optional - that's it. The message says you
>>> consolidate checks. How is this related to the title?
>>>
>>> The patch itself moves around checking of properties and reads
>>> nand-bus-width *always*. It does not "check at one place" but rather
>>> "check always". In the same time, the patch does not remove
>>> gpmc,device-width check in other place.
>>>
>>> All three elements - the title, message and patch - do different things.
>>> What did you want to achieve here? Can you help in clarifying it?
>>>
>>
>> OK I will explain it better in commit log in next revision. Let me explain here a bit.
>>
>> Prior to this patch it was working like this
>>
>> /* in gpmc_read_settings_dt() */
>> s->device_width = 0; /* invalid width, should be 1 for 8-bit, 2 for 16-bit */
>> of_property_read_u32(np, "gpmc,device-width", s->device_width);
>>
>> /* in gpmc_probe_generic_child () */
>> if (of_device_is_compatible(child, "ti,omap2-nand")) {
>> /* check for nand-bus-width, if absent set s->device_width to 1 (i.e. 8-bit) */
>> } else {
>> /* check for bank-width, if absent and s->device_width not set, error out */
>> }
>>
>> So that means if all three, "gpmc,device-width". "nand-bus-width" and "bank-width" are missing then
>> it would create an error situation.
>>
>> The patch is doing 3 things.
>> 1) Make sure all DT checks related to bus width are being done at one place for better readability.
>
> Not entirely. The gpmc,device-width is still done in the other place
> because you did not remove it from the code. Unless you meant parsing of
> gpmc,device-width not reading from DT? But then another round of checks
> is in gpmc_cs_program_settings() so not in one place.
By checking I meant parsing. But you are right, I missed the part in gpmc_cs_program_settings().
>
> If you consolidate the checks to one place, I would expect the code to
> be removed from other places, so from gpmc_cs_program_settings() and
> gpmc_read_settings_dt(). Since this is not happening, the message
> confuses me.
>
>> 2) even if all 3 width properties are absent, we will not treat it as error and default to 8-bit.
>
> This is not mentioned in commit msg.
>
>> 3) check for nand-bus-width regardless of whether compatible to "ti,omap2-nand" or not.
>
> Also not mentioned in commit msg.
>
> Your commit reorganizes parsing and validating the child DT properties
> but it does not change from "multiple place" to "one place".
>
> At least I don't see it.
OK. I will write a better commit log next time. Thanks for the review :)
cheers,
-roger
prev parent reply other threads:[~2021-09-17 7:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 11:32 [PATCH v3 0/8] dt-bindings: memory-controllers: ti,gpmc: Convert to yaml Roger Quadros
2021-09-07 11:32 ` [PATCH v3 1/8] ARM: dts: omap: Fixup GPMC child nodes Roger Quadros
2021-09-07 12:44 ` Krzysztof Kozlowski
2021-09-15 8:53 ` Roger Quadros
2021-09-07 11:32 ` [PATCH v3 2/8] dt-bindings: mtd: Remove gpmc-nor.txt Roger Quadros
2021-09-07 11:32 ` [PATCH v3 3/8] dt-bindings: net: Remove gpmc-eth.txt Roger Quadros
2021-09-07 11:32 ` [PATCH v3 4/8] dt-bindings: memory-controllers: Introduce ti,gpmc-child Roger Quadros
2021-09-07 11:32 ` [PATCH v3 5/8] dt-bindings: mtd: ti,gpmc-nand: Convert to yaml Roger Quadros
2021-09-07 14:03 ` Miquel Raynal
2021-09-07 15:27 ` Grygorii Strashko
2021-09-07 16:35 ` Miquel Raynal
2021-09-07 16:57 ` Roger Quadros
2021-09-07 22:24 ` Rob Herring
2021-09-08 6:55 ` Roger Quadros
2021-09-07 17:01 ` Rob Herring
2021-09-08 11:14 ` Roger Quadros
2021-09-08 12:46 ` Rob Herring
2021-09-07 11:32 ` [PATCH v3 6/8] dt-bindings: mtd: ti,gpmc-onenand: " Roger Quadros
2021-09-07 11:32 ` [PATCH v3 7/8] dt-bindings: memory-controllers: ti,gpmc: " Roger Quadros
2021-09-07 11:32 ` [PATCH v3 8/8] memory: gpmc-omap: "gpmc,device-width" DT property is optional Roger Quadros
2021-09-07 12:36 ` Krzysztof Kozlowski
2021-09-15 9:11 ` Roger Quadros
2021-09-16 10:48 ` Krzysztof Kozlowski
2021-09-17 7:17 ` Roger Quadros [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d574837c-b42a-53be-7885-9feb7183ce96@kernel.org \
--to=rogerq@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=miquel.raynal@bootlin.com \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox