From: "Rob Herring (Arm)" <robh@kernel.org>
To: "Duje Mihanović" <duje@dujemihanovic.xyz>
Cc: ~postmarketos/upstreaming@lists.sr.ht,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Karel Balej <balejk@matfyz.cz>,
linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
phone-devel@vger.kernel.org, Ulf Hansson <ulf.hansson@linaro.org>,
Adrian Hunter <adrian.hunter@intel.com>,
David Wronek <david@mainlining.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC v2 1/2] dt-bindings: mmc: sdhci-pxa: add state_uhs pinctrl
Date: Tue, 5 Aug 2025 10:24:47 -0500 [thread overview]
Message-ID: <175440748721.1807566.14795455362522050804.robh@kernel.org> (raw)
In-Reply-To: <20250801-pxav3-uhs-v2-1-afc1c428c776@dujemihanovic.xyz>
On Fri, 01 Aug 2025 16:14:15 +0200, Duje Mihanović wrote:
> On the pxav3 controller, increasing the drive strength of the data pins
> might be required to maintain stability on fast bus clocks (above 100
> MHz). Add a state_uhs pinctrl to allow this.
>
> The existing state_cmd_gpio pinctrl is changed to apply only on pxav1 as
> it's unneeded on the other controllers.
>
> Signed-off-by: Duje Mihanović <duje@dujemihanovic.xyz>
> ---
> Changes in v2:
> - Newlines between properties in if:
> ---
> .../devicetree/bindings/mmc/sdhci-pxa.yaml | 47 +++++++++++++++++-----
> 1 file changed, 37 insertions(+), 10 deletions(-)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-08-05 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-01 14:14 [PATCH RFC v2 0/2] mmc: sdhci-pxav3: pinctrl setting for fast bus clocks Duje Mihanović
2025-08-01 14:14 ` [PATCH RFC v2 1/2] dt-bindings: mmc: sdhci-pxa: add state_uhs pinctrl Duje Mihanović
2025-08-05 15:24 ` Rob Herring (Arm) [this message]
2025-08-01 14:14 ` [PATCH RFC v2 2/2] mmc: sdhci-pxav3: add state_uhs pinctrl setting Duje Mihanović
2025-08-04 13:39 ` Adrian Hunter
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=175440748721.1807566.14795455362522050804.robh@kernel.org \
--to=robh@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=balejk@matfyz.cz \
--cc=conor+dt@kernel.org \
--cc=david@mainlining.org \
--cc=devicetree@vger.kernel.org \
--cc=duje@dujemihanovic.xyz \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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
all inboxes | Powered by JetHome®