public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Raag Jadav <raag.jadav@intel.com>
Cc: mika.westerberg@linux.intel.com, linusw@kernel.org,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org,
	Guido Trentalancia <guido@trentalancia.com>
Subject: Re: [PATCH] pinctrl: tigerlake: Add Alder Lake-P documentation
Date: Tue, 20 Jan 2026 15:46:46 +0200	[thread overview]
Message-ID: <aW-HRvqc40ja60cF@smile.fi.intel.com> (raw)
In-Reply-To: <20260120110042.1021199-1-raag.jadav@intel.com>

On Tue, Jan 20, 2026 at 04:30:42PM +0530, Raag Jadav wrote:
> Intel Alder Lake-P PCH reuses pinctrl IP from Tiger Lake-LP. Add user
> friendly documentation for it.

Thanks for doing this!

Side note, though: this is not the only driver suffering of the similar issue.
Can you address them all?

...

>  	select PINCTRL_INTEL
>  	help
>  	  This pinctrl driver provides an interface that allows configuring
> -	  of Intel Tiger Lake PCH pins and using them as GPIOs.
> +	  PCH pins of the following platforms and using them as GPIOs.
> +	  - Tiger Lake

We also have letter suffix for the above. Does this driver covers _all_ Tiger
Lake modifications?

If so, I would do

	  - Tiger Lake (all modifications)

> +	  - Alder Lake-P

I can tweak this when applying if confirmed, otherwise we would need
a revisit v2.

-- 
With Best Regards,
Andy Shevchenko



      parent reply	other threads:[~2026-01-20 13:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20 11:00 [PATCH] pinctrl: tigerlake: Add Alder Lake-P documentation Raag Jadav
2026-01-20 11:20 ` Mika Westerberg
2026-01-20 12:52 ` Guido Trentalancia
2026-01-20 13:48   ` Andy Shevchenko
2026-01-20 13:46 ` Andy Shevchenko [this message]

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=aW-HRvqc40ja60cF@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=guido@trentalancia.com \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=raag.jadav@intel.com \
    --cc=stable@vger.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