From: Potin Lai <potin.lai.pt@gmail.com>
To: Andrew Jeffery <andrew@codeconstruct.com.au>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>
Cc: linux-aspeed@lists.ozlabs.org, openbmc@lists.ozlabs.org,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Patrick Williams <patrick@stwcx.xyz>,
Cosmo Chou <cosmo.chou@quantatw.com>,
Potin Lai <potin.lai@quantatw.com>,
Potin Lai <potin.lai.pt@gmail.com>
Subject: [PATCH v2 0/2] add ast2600 NCSI pin group
Date: Thu, 20 Jun 2024 09:25:10 +0800 [thread overview]
Message-ID: <20240620012512.3109518-1-potin.lai.pt@gmail.com> (raw)
In the NCSI pin table, the reference clock output pin (RMIIXRCLKO) is not
needed on the management controller side.
LINK: [v1] https://lore.kernel.org/all/20240613080725.2531580-1-potin.lai.pt@gmail.com/
changes v1 --> v2:
- add NCSI pin group in dt-bindings document
Potin Lai (2):
pinctrl: aspeed-g6: Add NCSI pin group config
dt-bindings: pinctrl: aspeed,ast2600-pinctrl: add NCSI group
.../bindings/pinctrl/aspeed,ast2600-pinctrl.yaml | 2 ++
drivers/pinctrl/aspeed/pinctrl-aspeed-g6.c | 10 ++++++++--
2 files changed, 10 insertions(+), 2 deletions(-)
--
2.31.1
next reply other threads:[~2024-06-20 1:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 1:25 Potin Lai [this message]
2024-06-20 1:25 ` [PATCH v2 1/2] pinctrl: aspeed-g6: Add NCSI pin group config Potin Lai
2024-06-20 6:08 ` Paul Menzel
2024-06-20 1:25 ` [PATCH v2 2/2] dt-bindings: pinctrl: aspeed,ast2600-pinctrl: add NCSI group Potin Lai
2024-06-20 7:15 ` 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=20240620012512.3109518-1-potin.lai.pt@gmail.com \
--to=potin.lai.pt@gmail.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=cosmo.chou@quantatw.com \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
--cc=potin.lai@quantatw.com \
--cc=robh+dt@kernel.org \
/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).