linux-mediatek.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Golle <daniel@makrotopia.org>
To: linux-mediatek@lists.infradead.org,
	Jean Thomas <jean.thomas@wifirst.fr>,
	sean.wang@kernel.org, linus.walleij@linaro.org,
	matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] pinctrl: mediatek: mt7981: add additional emmc groups
Date: Wed, 17 Jan 2024 14:08:56 +0000	[thread overview]
Message-ID: <B51A9EE5-1C7A-48C9-A546-61C269AD266F@makrotopia.org> (raw)
In-Reply-To: <20240117124234.3137050-2-jean.thomas@wifirst.fr>



On 17 January 2024 12:42:34 UTC, Jean Thomas <jean.thomas@wifirst.fr> wrote:
>Add new emmc groups in the pinctrl driver for the
>MediaTek MT7981 SoC:
>* emmc reset, with pin 15.
>* emmc 4-bit bus-width, with pins 16 to 19, and 24 to 25.
>* emmc 8-bit bus-width, with pins 16 to 25.
>
>The existing emmc_45 group is kept for legacy reasons, even
>if this is the union of emmc_reset and emmc_8 groups.
>
>Signed-off-by: Jean Thomas <jean.thomas@wifirst.fr>

Reviewed-by: Daniel Golle <daniel@makrotopia.org>

>---
> drivers/pinctrl/mediatek/pinctrl-mt7981.c | 17 ++++++++++++++++-
> 1 file changed, 16 insertions(+), 1 deletion(-)
>
>diff --git a/drivers/pinctrl/mediatek/pinctrl-mt7981.c b/drivers/pinctrl/mediatek/pinctrl-mt7981.c
>index ca667ed25a4d..ef6123765885 100644
>--- a/drivers/pinctrl/mediatek/pinctrl-mt7981.c
>+++ b/drivers/pinctrl/mediatek/pinctrl-mt7981.c
>@@ -700,6 +700,15 @@ static int mt7981_drv_vbus_pins[] = { 14, };
> static int mt7981_drv_vbus_funcs[] = { 1, };
> 
> /* EMMC */
>+static int mt7981_emmc_reset_pins[] = { 15, };
>+static int mt7981_emmc_reset_funcs[] = { 2, };
>+
>+static int mt7981_emmc_4_pins[] = { 16, 17, 18, 19, 24, 25, };
>+static int mt7981_emmc_4_funcs[] = { 2, 2, 2, 2, 2, 2, };
>+
>+static int mt7981_emmc_8_pins[] = { 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, };
>+static int mt7981_emmc_8_funcs[] = { 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, };
>+
> static int mt7981_emmc_45_pins[] = { 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, };
> static int mt7981_emmc_45_funcs[] = { 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, };
> 
>@@ -854,6 +863,12 @@ static const struct group_desc mt7981_groups[] = {
> 	PINCTRL_PIN_GROUP("udi", mt7981_udi),
> 	/* @GPIO(14) DRV_VBUS(1) */
> 	PINCTRL_PIN_GROUP("drv_vbus", mt7981_drv_vbus),
>+	/* @GPIO(15): EMMC_RSTB(2) */
>+	PINCTRL_PIN_GROUP("emmc_reset", mt7981_emmc_reset),
>+	/* @GPIO(16,17,18,19,24,25): EMMC_DATx, EMMC_CLK, EMMC_CMD */
>+	PINCTRL_PIN_GROUP("emmc_4", mt7981_emmc_4),
>+	/* @GPIO(16,17,18,19,20,21,22,23,24,25): EMMC_DATx, EMMC_CLK, EMMC_CMD */
>+	PINCTRL_PIN_GROUP("emmc_8", mt7981_emmc_8),
> 	/* @GPIO(15,25): EMMC(2) */
> 	PINCTRL_PIN_GROUP("emmc_45", mt7981_emmc_45),
> 	/* @GPIO(16,21): SNFI(3) */
>@@ -957,7 +972,7 @@ static const char *mt7981_i2c_groups[] = { "i2c0_0", "i2c0_1", "u2_phy_i2c",
> static const char *mt7981_pcm_groups[] = { "pcm", };
> static const char *mt7981_udi_groups[] = { "udi", };
> static const char *mt7981_usb_groups[] = { "drv_vbus", };
>-static const char *mt7981_flash_groups[] = { "emmc_45", "snfi", };
>+static const char *mt7981_flash_groups[] = { "emmc_reset", "emmc_4", "emmc_8", "emmc_45", "snfi", };
> static const char *mt7981_ethernet_groups[] = { "smi_mdc_mdio", "gbe_ext_mdc_mdio",
> 	"wf0_mode1", "wf0_mode3", "mt7531_int", };
> static const char *mt7981_ant_groups[] = { "ant_sel", };


  reply	other threads:[~2024-01-17 14:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 12:42 [PATCH 1/2] pinctrl: mediatek: mt7981: add additional uart group Jean Thomas
2024-01-17 12:42 ` [PATCH 2/2] pinctrl: mediatek: mt7981: add additional emmc groups Jean Thomas
2024-01-17 14:08   ` Daniel Golle [this message]
2024-01-17 13:47 ` [PATCH 1/2] pinctrl: mediatek: mt7981: add additional uart group Daniel Golle
2024-01-27 23:52 ` Linus Walleij

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=B51A9EE5-1C7A-48C9-A546-61C269AD266F@makrotopia.org \
    --to=daniel@makrotopia.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=jean.thomas@wifirst.fr \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=sean.wang@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).