From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: GaryWang <is0124@gmail.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
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 v3 0/2] upboard pinctrl support for device id INTC1055
Date: Thu, 2 Jul 2026 11:46:28 +0300 [thread overview]
Message-ID: <akYlZCn9LKWGWM9e@ashevche-desk.local> (raw)
In-Reply-To: <20260702-upboard-pinctrl-add-upboard-intc1055-support-v3-0-e6bda3032914@gmail.com>
On Thu, Jul 02, 2026 at 03:10:37PM +0800, GaryWang wrote:
> Add missing groups and functions in Tigerlake's pinctrl driver for INTC1055.
> Add support "UP Xtreme i12" board.
>
> The pinctrl-upboard is provide additional driving power & pin mux function
> through native SOC pins -> FPGA/CPLD -> hat pins for flexable board level
> applications. it's probe from ACPI device id AANT0F01 & AANT0F04.
I don't see neither Linus' nor Mika's tags. Can you explain why you dropped them?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-07-02 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 7:10 [PATCH v3 0/2] upboard pinctrl support for device id INTC1055 GaryWang
2026-07-02 7:10 ` [PATCH v3 1/2] pinctrl: tigerlake: add some pin groups and functions for INTC1055 GaryWang
2026-07-02 8:55 ` Andy Shevchenko
2026-07-03 9:24 ` GaryWang
2026-07-02 7:10 ` [PATCH v3 2/2] pinctrl: upboard: add device id INTC1055 based UP boards support GaryWang
2026-07-02 8:46 ` Andy Shevchenko [this message]
2026-07-02 8:53 ` [PATCH v3 0/2] upboard pinctrl support for device id INTC1055 Andy Shevchenko
2026-07-03 9:23 ` GaryWang
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=akYlZCn9LKWGWM9e@ashevche-desk.local \
--to=andriy.shevchenko@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=mika.westerberg@linux.intel.com \
--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