From: Rob Herring <robh@kernel.org>
To: Alexander Stein <Alexander.Stein@tq-systems.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Pratyush Yadav <p.yadav@ti.com>, Michael Walle <michael@walle.cc>,
Tudor Ambarus <tudor.ambarus@microchip.com>,
Alexander Stein <alexander.stein@ew.tq-group.com>,
linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: mtd: spi-nor: Add output-driver-strength property
Date: Tue, 12 Oct 2021 07:52:17 -0500 [thread overview]
Message-ID: <YWWFAXeekLS80bOR@robh.at.kernel.org> (raw)
In-Reply-To: <20211004111529.211089-1-Alexander.Stein@tq-systems.com>
On Mon, Oct 04, 2021 at 01:15:28PM +0200, Alexander Stein wrote:
> From: Alexander Stein <alexander.stein@ew.tq-group.com>
>
> This property is for optimizing output voltage impedance and is
> specific to each board.
>
> Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> ---
> I checked Micron and Macronix datasheets. Both have similar but not
> identical supported values. Also the register locations are different.
> For those reasons I decided to specify the Ohms value directly and let
> the device specfic driver figure out if it is supported where to write
> it to.
> BTW: Are the Ohm values and the corresponding register bits standardized
> somewhere?
>
> Documentation/devicetree/bindings/mtd/jedec,spi-nor.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mtd/jedec,spi-nor.yaml b/Documentation/devicetree/bindings/mtd/jedec,spi-nor.yaml
> index ed590d7c6e37..7d7f20a741b5 100644
> --- a/Documentation/devicetree/bindings/mtd/jedec,spi-nor.yaml
> +++ b/Documentation/devicetree/bindings/mtd/jedec,spi-nor.yaml
> @@ -72,6 +72,12 @@ properties:
> be used on such systems, to denote the absence of a reliable reset
> mechanism.
>
> + output-driver-strength:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description:
> + Output driver strength in Ohms which optimizes the impedance at Vcc/2
> + output voltage.
Use a standard unit suffix.
Though, specifying 'drive strength' in ohms rather than amps is a bit
strange.
prev parent reply other threads:[~2021-10-12 12:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 11:15 [PATCH 1/2] dt-bindings: mtd: spi-nor: Add output-driver-strength property Alexander Stein
2021-10-04 11:15 ` [PATCH 2/2] mtd: spi-nor: micron-st: Add support for output-driver-strength Alexander Stein
2021-10-04 11:26 ` Tudor.Ambarus
2021-10-08 11:18 ` Pratyush Yadav
2021-10-04 11:25 ` [PATCH 1/2] dt-bindings: mtd: spi-nor: Add output-driver-strength property Tudor.Ambarus
2021-10-05 12:26 ` Rob Herring
2021-10-12 12:52 ` Rob Herring [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=YWWFAXeekLS80bOR@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=Alexander.Stein@tq-systems.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=p.yadav@ti.com \
--cc=richard@nod.at \
--cc=tudor.ambarus@microchip.com \
--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).