devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arseniy Krasnov <avkrasnov@sberdevices.ru>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Liang Yang <liang.yang@amlogic.com>,
	Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Kevin Hilman <khilman@baylibre.com>,
	Jerome Brunet <jbrunet@baylibre.com>,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	<oxffffaa@gmail.com>, <kernel@sberdevices.ru>,
	<linux-mtd@lists.infradead.org>, <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-amlogic@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] dt-bindings: nand: meson: Fix 'nand-rb' property
Date: Wed, 7 Jun 2023 11:40:59 +0300	[thread overview]
Message-ID: <166bdc27-f77c-9076-f866-180cfa5bff76@sberdevices.ru> (raw)
In-Reply-To: <20230607095802.3adcd4f9@xps-13>

Hello Miquel, 

On 07.06.2023 10:58, Miquel Raynal wrote:

> Hi Arseniy,
> 
> AVKrasnov@sberdevices.ru wrote on Tue, 6 Jun 2023 22:35:07 +0300:
> 
>> Add description of 'nand-rb' property. Use "Fixes" because this property
>> must be supported since the beginning. For this controller 'nand-rb' is
>> stored in the controller node (not in chip), because it has only single
>> r/b wire for all chips.
> 
> Sorry if I mislead you in the first place, but you could definitely
> have two chips and only one with RB wired. It needs to be defined in
> the chips.

Ok, so to clarify: is it ok, that in bindings this property will be placed in the
chip, but in driver, i'm trying to read it from the controller node (thus  in
dts file it will be also in controller node)? Because in driver there is no sense
to store this value in chip structure. In fact, in driver, I can read it from the
chip node, but set 'no_rb_pin' flag in the controller structure.

Thanks, Arseniy

> 
> Please keep the bindings and driver changes related to this in the same
> series.

Ack

> 
>>
>> Fixes: fbc00b5e746f ("dt-bindings: nand: meson: convert txt to yaml")
>> Signed-off-by: Arseniy Krasnov <AVKrasnov@sberdevices.ru>
>> ---
>>  Documentation/devicetree/bindings/mtd/amlogic,meson-nand.yaml | 3 +++
>>  1 file changed, 3 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/mtd/amlogic,meson-nand.yaml b/Documentation/devicetree/bindings/mtd/amlogic,meson-nand.yaml
>> index 28fb9a7dd70f..866edf800b81 100644
>> --- a/Documentation/devicetree/bindings/mtd/amlogic,meson-nand.yaml
>> +++ b/Documentation/devicetree/bindings/mtd/amlogic,meson-nand.yaml
>> @@ -37,6 +37,8 @@ properties:
>>        - const: core
>>        - const: device
>>  
>> +  nand-rb: true
>> +
>>  patternProperties:
>>    "^nand@[0-7]$":
>>      type: object
>> @@ -81,6 +83,7 @@ examples:
>>  
>>        pinctrl-0 = <&nand_pins>;
>>        pinctrl-names = "default";
>> +      nand-rb = "true";
>>  
>>        #address-cells = <1>;
>>        #size-cells = <0>;
> 
> 
> Thanks,
> Miquèl

  reply	other threads:[~2023-06-07  8:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06 19:35 [PATCH v1] dt-bindings: nand: meson: Fix 'nand-rb' property Arseniy Krasnov
2023-06-06 20:12 ` Rob Herring
2023-06-07  7:58 ` Miquel Raynal
2023-06-07  8:40   ` Arseniy Krasnov [this message]
2023-06-07  8:53     ` Krzysztof Kozlowski
2023-06-07  8:57       ` Arseniy Krasnov
2023-06-07  9:08         ` Krzysztof Kozlowski
2023-06-07  9:04           ` Arseniy Krasnov
2023-06-07  9:36             ` Miquel Raynal
2023-06-07 14:52               ` Arseniy Krasnov
2023-06-07 14:58                 ` Krzysztof Kozlowski
2023-06-07 14:55                   ` Arseniy Krasnov
2023-06-07 15:07                     ` Krzysztof Kozlowski
2023-06-07 15:21                       ` Arseniy Krasnov

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=166bdc27-f77c-9076-f866-180cfa5bff76@sberdevices.ru \
    --to=avkrasnov@sberdevices.ru \
    --cc=devicetree@vger.kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=kernel@sberdevices.ru \
    --cc=khilman@baylibre.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=liang.yang@amlogic.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=neil.armstrong@linaro.org \
    --cc=oxffffaa@gmail.com \
    --cc=richard@nod.at \
    --cc=robh+dt@kernel.org \
    --cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).