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 v3 3/3] dt-bindings: memory-controllers: gpmc-child: add wait-pin polarity
Date: Thu, 8 Sep 2022 15:09:08 +0300 [thread overview]
Message-ID: <70a2fec4-e7b9-e8ed-4d8a-d547003dbb9e@kernel.org> (raw)
In-Reply-To: <20220906124747.1767318-5-benedikt.niedermayr@siemens.com>
Benedikt,
On 06/09/2022 15:47, B. Niedermayr wrote:
> From: Benedikt Niedermayr <benedikt.niedermayr@siemens.com>
>
> The GPMC controller has the ability to configure the polarity for the
> wait pin. The current properties do not allow this configuration.
> This binding directly configures the WAITPIN<X>POLARITY bit
> in the GPMC_CONFIG register.
>
> Signed-off-by: Benedikt Niedermayr <benedikt.niedermayr@siemens.com>
> ---
> .../bindings/memory-controllers/ti,gpmc-child.yaml | 6 ++++++
> 1 file changed, 6 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..a115b544a407 100644
> --- a/Documentation/devicetree/bindings/memory-controllers/ti,gpmc-child.yaml
> +++ b/Documentation/devicetree/bindings/memory-controllers/ti,gpmc-child.yaml
> @@ -230,6 +230,12 @@ properties:
> Wait-pin used by client. Must be less than "gpmc,num-waitpins".
> $ref: /schemas/types.yaml#/definitions/uint32
>
> + gpmc,wait-pin-active-low:
> + description: |
> + Set the polarity for the selected wait pin to active low.
> + Defaults to active high if this is not set.
> + type: boolean
> +
I just checked that the default behaviour is active low.
Reset value of the polarity register field is 0, which means active low.
We will need to use the property "gpmc,wait-pin-active-high" instead.
Sorry for not catching this earlier.
> gpmc,wait-on-read:
> description: Enables wait monitoring on reads.
> type: boolean
cheers,
-roger
next prev parent reply other threads:[~2022-09-08 12:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 12:47 [PATCH v3 0/3] omap-gpmc wait pin additions B. Niedermayr
2022-09-06 12:47 ` [PATCH v3 1/3] memory: omap-gpmc: allow shared wait pins B. Niedermayr
2022-09-06 12:47 ` [PATCH v3 2/3] memory: omap-gpmc: add support for wait pin polarity B. Niedermayr
2022-09-06 12:47 ` [PATCH 3/3] dt-bindings: memory-controllers: gpmc-child: Add binding for wait-pin-polarity B. Niedermayr
2022-09-08 12:03 ` Roger Quadros
2022-09-12 7:07 ` Niedermayr, BENEDIKT
2022-09-06 12:47 ` [PATCH v3 3/3] dt-bindings: memory-controllers: gpmc-child: add wait-pin polarity B. Niedermayr
2022-09-08 12:09 ` Roger Quadros [this message]
2022-09-12 7:43 ` Niedermayr, BENEDIKT
2022-09-12 11:04 ` Roger Quadros
2022-09-13 8:23 ` Niedermayr, BENEDIKT
2022-09-13 13:18 ` Roger Quadros
2022-09-13 20:56 ` Niedermayr, BENEDIKT
2022-09-14 11:15 ` Roger Quadros
2022-09-06 12:47 ` [PATCH v3 0/3] omap-gpmc wait pin additions B. Niedermayr
2022-09-13 9:17 ` Krzysztof Kozlowski
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=70a2fec4-e7b9-e8ed-4d8a-d547003dbb9e@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).