Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Gary Wang <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 v4 0/2] upboard pinctrl support for device id INTC1055
Date: Wed, 8 Jul 2026 17:29:18 +0300	[thread overview]
Message-ID: <ak5evtAHnMrwVqvM@ashevche-desk.local> (raw)
In-Reply-To: <20260706-upboard-pinctrl-add-upboard-intc1055-support-v4-0-cedce0802d3d@gmail.com>

On Mon, Jul 06, 2026 at 06:36:33PM +0800, Gary Wang 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.

Pushed to my review and testing queue, thanks!

-- 
With Best Regards,
Andy Shevchenko



      parent reply	other threads:[~2026-07-08 14:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06 10:36 [PATCH v4 0/2] upboard pinctrl support for device id INTC1055 Gary Wang
2026-07-06 10:36 ` [PATCH v4 1/2] pinctrl: tigerlake: add some pin groups and functions for INTC1055 Gary Wang
2026-07-06 10:36 ` [PATCH v4 2/2] pinctrl: upboard: add device id INTC1055 based UP boards support Gary Wang
2026-07-07 11:50   ` Thomas Richard
2026-07-07 15:55     ` GaryWang
2026-07-08  7:49       ` Thomas Richard
2026-07-08  9:21         ` Andy Shevchenko
2026-07-08 10:39           ` GaryWang
2026-07-08 12:55           ` Thomas Richard
2026-07-08 14:29 ` 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=ak5evtAHnMrwVqvM@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