public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Niedermayr, BENEDIKT" <benedikt.niedermayr@siemens.com>
To: "rogerq@kernel.org" <rogerq@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Cc: "tony@atomide.com" <tony@atomide.com>,
	"krzysztof.kozlowski@linaro.org" <krzysztof.kozlowski@linaro.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>
Subject: Re: [PATCH v2 3/3] dt-bindings: memory-controllers: gpmc-child: Add binding for wait-pin-polarity
Date: Mon, 5 Sep 2022 09:14:45 +0000	[thread overview]
Message-ID: <e284855271a3fdf6bb2cd304629c2aa3bb8401f3.camel@siemens.com> (raw)
In-Reply-To: <d75ff1cf-64a6-e794-87a2-204e93c852cf@kernel.org>

On Mon, 2022-09-05 at 11:56 +0300, Roger Quadros wrote:
> Hi Benedikt,
> 
> On 05/09/2022 10:17, B. Niedermayr wrote:
> > From: Benedikt Niedermayr <benedikt.niedermayr@siemens.com>
> > 
> > Add a new dt-binding for the wait-pin-polarity property
> > 
> > Signed-off-by: Benedikt Niedermayr <benedikt.niedermayr@siemens.com
> > >
> > ---
> >  .../bindings/memory-controllers/ti,gpmc-child.yaml         | 7
> > +++++++
> >  1 file changed, 7 insertions(+)
> > 
> > diff --git a/Documentation/devicetree/bindings/memory-
> > controllers/ti,gpmc-child.yaml
> > b/Documentation/devicetree/bindings/memory-controllers/ti,gpmc-
> > child.yaml
> > index 6e3995bb1630..7c721206f10b 100644
> > --- a/Documentation/devicetree/bindings/memory-controllers/ti,gpmc-
> > child.yaml
> > +++ b/Documentation/devicetree/bindings/memory-controllers/ti,gpmc-
> > child.yaml
> > @@ -230,6 +230,13 @@ properties:
> >        Wait-pin used by client. Must be less than "gpmc,num-
> > waitpins".
> >      $ref: /schemas/types.yaml#/definitions/uint32
> >  
> > +  gpmc,wait-pin-polarity:
> > +    description: |
> > +      Wait-pin polarity used by the clien. It relates to the pin
> > defined
> 
> did you mean "client?"
> Can you please specify what value is for Active Low vs Active High?

Yes, that makes sense. And yes I meant "client". My typo.....
> 
> > +      with "gpmc,wait-pin".
> > +    $ref: /schemas/types.yaml#/definitions/uint32
> 
> Why can't type be boolean?

Of course we can use the boolean there. In that case I should give the
property a more meaningful name e.g. wait-pin-active-high or wait-pin-
active-low. 
Since the default behavour of this pin is Active High,
a bool property "gpmc,wait-pin-active-low" would make more sense for
backwards compatibility. 
If the property is missing, than the polarity stays on Active High like
before.

> 
> > +    default: 0
> > +
> >    gpmc,wait-on-read:
> >      description: Enables wait monitoring on reads.
> >      type: boolean
> 
> cheers,
> -roger

cheers,
benedikt


  reply	other threads:[~2022-09-05  9:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05  7:17 [PATCH v2 0/3] omap-gpmc wait pin additions B. Niedermayr
2022-09-05  7:17 ` [PATCH v2 1/3] memory: omap-gpmc: allow shared wait pins B. Niedermayr
2022-09-05  7:17 ` [PATCH v2 2/3] memory: omap-gpmc: add support for wait pin polarity B. Niedermayr
2022-09-05  9:19   ` Roger Quadros
2022-09-05  9:47     ` Niedermayr, BENEDIKT
2022-09-05  7:17 ` [PATCH v2 3/3] dt-bindings: memory-controllers: gpmc-child: Add binding for wait-pin-polarity B. Niedermayr
2022-09-05  8:56   ` Roger Quadros
2022-09-05  9:14     ` Niedermayr, BENEDIKT [this message]
2022-09-05  9:21       ` Roger Quadros
2022-09-05  9:54         ` Krzysztof Kozlowski
2022-09-05 11:48           ` Niedermayr, BENEDIKT
2022-09-05 12:08             ` Krzysztof Kozlowski
2022-09-05 13:33               ` Niedermayr, BENEDIKT
2022-09-06 11:38                 ` Roger Quadros
2022-09-06 12:08                   ` Niedermayr, BENEDIKT
  -- strict thread matches above, loose matches on Subject: below --
2022-09-02  9:10 [PATCH v2 0/3] omap-gpmc wait pin additions B. Niedermayr
2022-09-02  9:10 ` [PATCH v2 3/3] dt-bindings: memory-controllers: gpmc-child: Add binding for wait-pin-polarity B. Niedermayr

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=e284855271a3fdf6bb2cd304629c2aa3bb8401f3.camel@siemens.com \
    --to=benedikt.niedermayr@siemens.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=rogerq@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