From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: GaryWang <is0124@gmail.com>
Cc: Linus Walleij <linusw@kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andy@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 v2 0/2] upboard pinctrl support for device id INTC1055
Date: Mon, 15 Jun 2026 18:00:06 +0300 [thread overview]
Message-ID: <ajATdk_OlOKoXEXa@ashevche-desk.local> (raw)
In-Reply-To: <CANYHO6pmq+YE3M3kUOegsYwxjfV3qBasX56RSTtwRvVMaFCgPg@mail.gmail.com>
On Mon, Jun 15, 2026 at 10:25:32PM +0800, GaryWang wrote:
> On Mon, 15 Jun 2026 at 22:07, Andy Shevchenko
> <andriy.shevchenko@intel.com> wrote:
> > On Mon, Jun 15, 2026 at 02:32:51PM +0200, Linus Walleij wrote:
> > > On Fri, Jun 12, 2026 at 12:13 PM GaryWang <is0124@gmail.com> wrote:
> > >
> > > > Add missing groups and functions in Tigerlake's pinctrl driver for INTC1055.
> > > > Add support "UP Xtreme i12", "UP Squared Pro 7000", "UP Squared i12", "UP 7000" boards.
> > > >
> > > > 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.
> > > >
> > > > Signed-off-by: GaryWang <is0124@gmail.com>
> > >
> > > LGTM
> > > Acked-by: Linus Walleij <linusw@kernel.org>
> > >
> > > Since these touch Tigerlake, I expect Andy to queue and send me
> > > the patches from his tree.
> >
> > Yes, this is the idea, but first I want to hear form Gary about Up 7000, which
> > seems doesn't work with this.
> >
> It's my bad, the up squared pro has p & n series processor, I only checked the
> p series.
> The p series is used INTC1055 and n series is using INTC1057 has confirmed.
> I need remove n series boards, until we finished testing, thanks.
Okay, please finish testing, update commit messages (and code if necessary),
collected tags, and send a v3. Take your time as it won't be proceeded within
two weeks (merge window is ongoing).
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-06-15 15:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 10:13 [PATCH v2 0/2] upboard pinctrl support for device id INTC1055 GaryWang
2026-06-12 10:13 ` [PATCH v2 1/2] pinctrl: tigerlake: add some pin groups and functions for INTC1055 GaryWang
2026-06-12 10:13 ` [PATCH v2 2/2] pinctrl: upboard: add device id INTC1055 based UP boards support GaryWang
2026-06-15 8:01 ` Thomas Richard
2026-06-15 9:37 ` Thomas Richard
2026-06-15 11:23 ` GaryWang
2026-06-15 12:13 ` Thomas Richard
2026-06-15 4:35 ` [PATCH v2 0/2] upboard pinctrl support for device id INTC1055 Mika Westerberg
2026-06-15 7:01 ` GaryWang
2026-06-15 9:47 ` Mika Westerberg
2026-06-15 12:32 ` Linus Walleij
2026-06-15 14:07 ` Andy Shevchenko
2026-06-15 14:25 ` GaryWang
2026-06-15 15:00 ` 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=ajATdk_OlOKoXEXa@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