From: Willie Thai <wthai@nvidia.com>
To: <andrew@codeconstruct.com.au>
Cc: <conor+dt@kernel.org>, <devicetree@vger.kernel.org>,
<dkodihalli@nvidia.com>, <gpiccoli@igalia.com>, <joel@jms.id.au>,
<kees@kernel.org>, <krzk+dt@kernel.org>, <leohu@nvidia.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-aspeed@lists.ozlabs.org>,
<linux-hardening@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<openbmc@lists.ozlabs.org>, <robh@kernel.org>,
<tingkaic@nvidia.com>, <tony.luck@intel.com>, <wthai@nvidia.com>,
<harrys@nvidia.com>
Subject: Re: Re: [PATCH v4 2/3] dt-bindings: pinctrl: aspeed,ast2600-pinctrl
Date: Mon, 31 Mar 2025 17:18:57 +0000 [thread overview]
Message-ID: <20250331171857.262649-1-wthai@nvidia.com> (raw)
In-Reply-To: <d0f7003c22e19c8fc7617610043edc7be925a180.camel@codeconstruct.com.au>
>> Add EMMCG5 enum to compatible list of pinctrl binding for emmc
>> enabling.
>>
>> Cc: Andrew Jeffery <andrew@codeconstruct.com.au>
>> Signed-off-by: Willie Thai <wthai@nvidia.com>
>> ---
>> .../devicetree/bindings/pinctrl/aspeed,ast2600-pinctrl.yaml | 1
>> +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git
>> a/Documentation/devicetree/bindings/pinctrl/aspeed,ast2600-
>> pinctrl.yaml
>> b/Documentation/devicetree/bindings/pinctrl/aspeed,ast2600-
>> pinctrl.yaml
>> index 80974c46f3ef..cb75e979f5e0 100644
>> --- a/Documentation/devicetree/bindings/pinctrl/aspeed,ast2600-
>> pinctrl.yaml
>> +++ b/Documentation/devicetree/bindings/pinctrl/aspeed,ast2600-
>> pinctrl.yaml
>> @@ -276,6 +276,7 @@ additionalProperties:
>> - BMCINT
>> - EMMCG1
>> - EMMCG4
>> + - EMMCG5
>
> What pin configuration does this correspond to for the eMMC controller?
> These groups aren't arbitrary, they correspond to the 1, 4 and 8-bit
> bus modes.
>
> You may have added this squash a warning, but I suspect the pinctrl
> configuration in your devicetree is incorrect.
>
> Andrew
>
Thanks for your feedback !
We want to exclude AC5 pin in the default EMMCG4 pin group, because that pin is used for other purpose.
We define a new group called EMMCG5 as:
GROUP_DECL(EMMCG5, AB4, AA4, AC4, AA5, Y5, AB5, AB6)
The bus mode is still 4-bit mode.
Could you please advise if we can use the name "EMMCG5" ?
>> - EMMCG8
>> - ESPI
next prev parent reply other threads:[~2025-03-31 17:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 17:59 [PATCH v4 0/3] Add device tree for Nvidia's GB200NVL BMC Willie Thai
2025-03-24 17:59 ` [PATCH v4 1/3] dt-bindings: arm: aspeed: add " Willie Thai
2025-03-25 7:17 ` Krzysztof Kozlowski
2025-03-24 17:59 ` [PATCH v4 2/3] dt-bindings: pinctrl: aspeed,ast2600-pinctrl Willie Thai
2025-03-25 7:17 ` Krzysztof Kozlowski
2025-03-28 0:46 ` Andrew Jeffery
2025-03-31 17:18 ` Willie Thai [this message]
2025-04-01 0:52 ` Andrew Jeffery
2025-03-24 17:59 ` [PATCH v4 3/3] ARM: dts: aspeed: Add device tree for Nvidia's GB200NVL BMC Willie Thai
2025-03-25 3:13 ` [PATCH v4 0/3] " Rob Herring (Arm)
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=20250331171857.262649-1-wthai@nvidia.com \
--to=wthai@nvidia.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dkodihalli@nvidia.com \
--cc=gpiccoli@igalia.com \
--cc=harrys@nvidia.com \
--cc=joel@jms.id.au \
--cc=kees@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=leohu@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=robh@kernel.org \
--cc=tingkaic@nvidia.com \
--cc=tony.luck@intel.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
all inboxes | Powered by JetHome®