devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Andrew Jeffery" <andrew@aj.id.au>
To: "Jae Hyun Yoo" <quic_jaehyoo@quicinc.com>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Joel Stanley" <joel@jms.id.au>, "Arnd Bergmann" <arnd@arndb.de>
Cc: "Jamie Iles" <quic_jiles@quicinc.com>,
	"Graeme Gregory" <quic_ggregory@quicinc.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org,
	"Johnny Huang" <johnny_huang@aspeedtech.com>
Subject: Re: [PATCH v3 4/7] pinctrl: pinctrl-aspeed-g6: add FWQSPI function-group
Date: Wed, 30 Mar 2022 12:32:41 +1030	[thread overview]
Message-ID: <484751b1-86d0-40e6-b5cd-013ef076f3e5@www.fastmail.com> (raw)
In-Reply-To: <20220329173932.2588289-5-quic_jaehyoo@quicinc.com>



On Wed, 30 Mar 2022, at 04:09, Jae Hyun Yoo wrote:
> From: Johnny Huang <johnny_huang@aspeedtech.com>
>
> Add FWSPIDQ2 (AE12) and FWSPIDQ3 (AF12) function-group to support
> AST2600 FW SPI quad mode. These pins can be used with dedicated FW
> SPI pins - FWSPICS0# (AB14), FWSPICK (AF13), FWSPIMOSI (AC14)
> and FWSPIMISO (AB13).
>
> Signed-off-by: Johnny Huang <johnny_huang@aspeedtech.com>
> Signed-off-by: Jae Hyun Yoo <quic_jaehyoo@quicinc.com>

Reviewed-by: Andrew Jeffery <andrew@aj.id.au>

  reply	other threads:[~2022-03-30  2:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 17:39 [PATCH v3 0/7] Fix AST2600 quad mode SPI pinmux settings Jae Hyun Yoo
2022-03-29 17:39 ` [PATCH v3 1/7] ARM: dts: aspeed-g6: remove FWQSPID group in pinctrl dtsi Jae Hyun Yoo
2022-03-29 17:39 ` [PATCH v3 2/7] pinctrl: pinctrl-aspeed-g6: remove FWQSPID group in pinctrl Jae Hyun Yoo
2022-03-30  2:00   ` Andrew Jeffery
2022-03-29 17:39 ` [PATCH v3 3/7] dt-bindings: pinctrl: aspeed-g6: remove FWQSPID group Jae Hyun Yoo
2022-03-29 23:38   ` Rob Herring
2022-03-30  2:01   ` Andrew Jeffery
2022-03-29 17:39 ` [PATCH v3 4/7] pinctrl: pinctrl-aspeed-g6: add FWQSPI function-group Jae Hyun Yoo
2022-03-30  2:02   ` Andrew Jeffery [this message]
2022-03-29 17:39 ` [PATCH v3 5/7] dt-bindings: pinctrl: aspeed-g6: add FWQSPI function/group Jae Hyun Yoo
2022-03-29 23:38   ` Rob Herring
2022-03-30  2:03   ` Andrew Jeffery
2022-03-29 17:39 ` [PATCH v3 6/7] ARM: dts: aspeed-g6: add FWQSPI group in pinctrl dtsi Jae Hyun Yoo
2022-03-30  2:03   ` Andrew Jeffery
2022-03-29 17:39 ` [PATCH v3 7/7] ARM: dts: aspeed-g6: fix SPI1/SPI2 quad pin group Jae Hyun Yoo
2022-03-31  5:50 ` [PATCH v3 0/7] Fix AST2600 quad mode SPI pinmux settings Joel Stanley
2022-03-31 15:44   ` Jae Hyun Yoo
2022-03-31 15:56     ` Cédric Le Goater
2022-03-31 16:06       ` Jae Hyun Yoo
2022-04-01 14:10         ` Jae Hyun Yoo
2022-04-01 22:07           ` Cédric Le Goater
2022-04-01 22:25             ` Jae Hyun Yoo
2022-04-17 23:28 ` Linus Walleij
2022-04-18 14:07   ` Jae Hyun Yoo

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=484751b1-86d0-40e6-b5cd-013ef076f3e5@www.fastmail.com \
    --to=andrew@aj.id.au \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=joel@jms.id.au \
    --cc=johnny_huang@aspeedtech.com \
    --cc=krzk+dt@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=quic_ggregory@quicinc.com \
    --cc=quic_jaehyoo@quicinc.com \
    --cc=quic_jiles@quicinc.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).