From: Andre Przywara <andre.przywara@arm.com>
To: Iota Hydrae <writeforever@foxmail.com>
Cc: Jagan Teki <jagan@amarulasolutions.com>, u-boot@lists.denx.de
Subject: Re: [PATCH] pinctrl: sunxi: add SPI1 pinmuxes for f1c100s
Date: Thu, 24 Aug 2023 14:56:21 +0100 [thread overview]
Message-ID: <20230824145621.33370e53@slackpad.lan> (raw)
In-Reply-To: <tencent_807B704C8CF66453A9723C0E19D28E962607@qq.com>
On Wed, 23 Aug 2023 14:47:16 +0800
Iota Hydrae <writeforever@foxmail.com> wrote:
Hi,
> SPI1 is also usable on port A.
>
> But there's nothing about SPI1 pinmux there for now.
>
> This should be set when you are using SPI1.
>
> According to the manual, the mux value would be 6.
So technically that looks alright, but what do you need that for? We
try to not add pinmux values to that table unless they are used
somewhere, especially if there are potential conflicting values: SPI1
on PE is on pinmux 4.
So do you have a board that needs that? Any chance you could upstream
the DT (to the kernel list!) and defconfig for that board? That would
it make it a no-brainer to merge this patch.
Cheers,
Andre
> Signed-off-by: Iota Hydrae <writeforever@foxmail.com>
> ---
> drivers/pinctrl/sunxi/pinctrl-sunxi.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/pinctrl/sunxi/pinctrl-sunxi.c b/drivers/pinctrl/sunxi/pinctrl-sunxi.c
> index e5102180902..c448e40ab07 100644
> --- a/drivers/pinctrl/sunxi/pinctrl-sunxi.c
> +++ b/drivers/pinctrl/sunxi/pinctrl-sunxi.c
> @@ -240,6 +240,7 @@ static const struct sunxi_pinctrl_function suniv_f1c100s_pinctrl_functions[] = {
> { "mmc0", 2 }, /* PF0-PF5 */
> { "mmc1", 3 }, /* PC0-PC2 */
> { "spi0", 2 }, /* PC0-PC3 */
> + { "spi1", 6 }, /* PA0-PA3 */
> #if IS_ENABLED(CONFIG_UART0_PORT_F)
> { "uart0", 3 }, /* PF2-PF4 */
> #else
next prev parent reply other threads:[~2023-08-24 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 6:47 [PATCH] pinctrl: sunxi: add SPI1 pinmuxes for f1c100s Iota Hydrae
2023-08-24 13:56 ` Andre Przywara [this message]
[not found] ` <tencent_33B0F669D3B672650E0BD2D91656FB1ACC07@qq.com>
2023-08-30 9:18 ` Andre Przywara
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=20230824145621.33370e53@slackpad.lan \
--to=andre.przywara@arm.com \
--cc=jagan@amarulasolutions.com \
--cc=u-boot@lists.denx.de \
--cc=writeforever@foxmail.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