From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: GaryWang <is0124@gmail.com>
Cc: Andy Shevchenko <andy@kernel.org>,
Linus Walleij <linusw@kernel.org>,
Thomas Richard <thomas.richard@bootlin.com>,
Daniele Cleri <danielecleri@aaeon.eu>,
JunYingLai <junyinglai@aaeon.com.tw>,
Louis Chen <louischen@aaeon.com.tw>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] pinctrl: tigerlake: add some pin groups and functions for INTC1055
Date: Wed, 10 Jun 2026 16:24:09 +0200 [thread overview]
Message-ID: <20260610142409.GT2990@black.igk.intel.com> (raw)
In-Reply-To: <20260610-upboard-pinctrl-add-upboard-intc1055-support-v1-1-8185d2abbfb1@gmail.com>
On Wed, Jun 10, 2026 at 04:34:23PM +0800, GaryWang wrote:
> Add i2c0, i2c1, pwm0, uart1, ssp2 pin groups & functions in tgllp_soc_data
> for device id INTC1055.
Okay we can see that from the code but why? Can you explain it here too?
>
> Signed-off-by: GaryWang <is0124@gmail.com>
> ---
> drivers/pinctrl/intel/pinctrl-tigerlake.c | 32 +++++++++++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
>
> diff --git a/drivers/pinctrl/intel/pinctrl-tigerlake.c b/drivers/pinctrl/intel/pinctrl-tigerlake.c
> index ae231f7fba49..aeb031570536 100644
> --- a/drivers/pinctrl/intel/pinctrl-tigerlake.c
> +++ b/drivers/pinctrl/intel/pinctrl-tigerlake.c
> @@ -330,6 +330,34 @@ static const struct pinctrl_pin_desc tgllp_pins[] = {
> PINCTRL_PIN(276, "SPI0_CLK_LOOPBK"),
> };
>
> +static const unsigned int tgllp_i2c0_pins[] = { 5, 6 };
> +static const unsigned int tgllp_i2c1_pins[] = { 7, 8 };
> +static const unsigned int tgllp_pwm0_pins[] = { 99 };
> +static const unsigned int tgllp_uart1_pins[] = { 85, 86, 87, 88 };
> +static const unsigned int tgllp_ssp2_pins[] = { 108, 109, 110, 111 };
> +
> +static const struct intel_pingroup tgllp_groups[] = {
> + PIN_GROUP("i2c0_grp", tgllp_i2c0_pins, 2),
> + PIN_GROUP("i2c1_grp", tgllp_i2c1_pins, 2),
> + PIN_GROUP("pwm0_grp", tgllp_pwm0_pins, 1),
> + PIN_GROUP("uart1_grp", tgllp_uart1_pins, 1),
> + PIN_GROUP("ssp2_grp", tgllp_ssp2_pins, 7),
> +};
> +
> +static const char * const tgllp_i2c0_groups[] = { "i2c0_grp" };
> +static const char * const tgllp_i2c1_groups[] = { "i2c1_grp" };
> +static const char * const tgllp_pwm0_groups[] = { "pwm0_grp" };
> +static const char * const tgllp_uart1_groups[] = { "uart1_grp" };
> +static const char * const tgllp_ssp2_groups[] = { "ssp2_grp" };
> +
> +static const struct intel_function tgllp_functions[] = {
> + FUNCTION("i2c0", tgllp_i2c0_groups),
> + FUNCTION("i2c1", tgllp_i2c1_groups),
> + FUNCTION("pwm0", tgllp_pwm0_groups),
> + FUNCTION("uart1", tgllp_uart1_groups),
> + FUNCTION("ssp2", tgllp_ssp2_groups),
> +};
> +
> static const struct intel_padgroup tgllp_community0_gpps[] = {
> INTEL_GPP(0, 0, 25, 0), /* GPP_B */
> INTEL_GPP(1, 26, 41, 32), /* GPP_T */
> @@ -367,6 +395,10 @@ static const struct intel_community tgllp_communities[] = {
> static const struct intel_pinctrl_soc_data tgllp_soc_data = {
> .pins = tgllp_pins,
> .npins = ARRAY_SIZE(tgllp_pins),
> + .groups = tgllp_groups,
> + .ngroups = ARRAY_SIZE(tgllp_groups),
> + .functions = tgllp_functions,
> + .nfunctions = ARRAY_SIZE(tgllp_functions),
> .communities = tgllp_communities,
> .ncommunities = ARRAY_SIZE(tgllp_communities),
> };
>
> --
> 2.43.0
next prev parent reply other threads:[~2026-06-10 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 8:34 [PATCH 0/2] upboard pinctrl support for device id INTC1055 GaryWang
2026-06-10 8:34 ` [PATCH 1/2] pinctrl: tigerlake: add some pin groups and functions for INTC1055 GaryWang
2026-06-10 14:24 ` Mika Westerberg [this message]
2026-06-10 14:37 ` Andy Shevchenko
2026-06-10 8:34 ` [PATCH 2/2] pinctrl: upboard: add device id INTC1055 based UP boards support GaryWang
2026-06-10 14:13 ` [PATCH 0/2] upboard pinctrl support for device id INTC1055 Andy Shevchenko
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=20260610142409.GT2990@black.igk.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andy@kernel.org \
--cc=danielecleri@aaeon.eu \
--cc=is0124@gmail.com \
--cc=junyinglai@aaeon.com.tw \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=louischen@aaeon.com.tw \
--cc=thomas.richard@bootlin.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