From: Roger Quadros <rogerq@kernel.org>
To: "B. Niedermayr" <benedikt.niedermayr@siemens.com>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org
Cc: tony@atomide.com, krzysztof.kozlowski@linaro.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 11:56:31 +0300 [thread overview]
Message-ID: <d75ff1cf-64a6-e794-87a2-204e93c852cf@kernel.org> (raw)
In-Reply-To: <20220905071717.1500568-4-benedikt.niedermayr@siemens.com>
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?
> + with "gpmc,wait-pin".
> + $ref: /schemas/types.yaml#/definitions/uint32
Why can't type be boolean?
> + default: 0
> +
> gpmc,wait-on-read:
> description: Enables wait monitoring on reads.
> type: boolean
cheers,
-roger
next prev parent reply other threads:[~2022-09-05 8:56 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 [this message]
2022-09-05 9:14 ` Niedermayr, BENEDIKT
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=d75ff1cf-64a6-e794-87a2-204e93c852cf@kernel.org \
--to=rogerq@kernel.org \
--cc=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=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;
as well as URLs for NNTP newsgroup(s).