From: Thomas Richard <thomas.richard@bootlin.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: GaryWang <is0124@gmail.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andy@kernel.org>,
Linus Walleij <linusw@kernel.org>,
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 2/2] pinctrl: upboard: add device id INTC1055 based UP boards support
Date: Wed, 8 Jul 2026 14:55:24 +0200 [thread overview]
Message-ID: <269d40d1-7783-4eca-8cee-3e2001cc6ccc@bootlin.com> (raw)
In-Reply-To: <CAHp75VcGGC8Z5vGN+RQtSA2N+s9ViH-tHi_BjT-_SWPVVoLQxA@mail.gmail.com>
On 7/8/26 11:21 AM, Andy Shevchenko wrote:
> On Wed, Jul 8, 2026 at 10:49 AM Thomas Richard
> <thomas.richard@bootlin.com> wrote:
>> On 7/7/26 5:55 PM, GaryWang wrote:
>>> On Tue, Jul 7, 2026 at 7:50 PM Thomas Richard
>>> <thomas.richard@bootlin.com> wrote:
>>>> On 7/6/26 12:36 PM, Gary Wang wrote:
>
> ...
>
>>>> I tested the IOs:
>>>> - pwm0 does not work.
>>> you have to use our pwm kernel module for pwm test, I'll provide later.
>>
>> Ack
>
> Can you, folks, elaborate why this is a requirement and what exactly
> is not working?
>
>>>> - uart1 partially works: TX is okay, but loopback doesn't work. Signal
>>>> is bad when I add a loopback. Looks like pinctrl misconfig on SoC side.
>>> uart1 tested ok on our side, if you loop TX/RX do not forget to turn off
>>> hardware flow control. and we have executed cmd as below to make sure
>>> direction is set all right.
>>> echo "uart1_grp uart1" >
>>> /sys/kernel/debug/pinctrl/upboard-pinctrl/pinmux-select
>>
>> I did some tests with/without flow control using linux-serial-test tool.
>
> I'm sorry it's not so clear to me, does it mean the serial interface
> is (still) not properly working or you have done that pinmux
> configuration and everything becomes fine (as Tested-by tag suggests)?
>
> ...
>
>>>> - for SPI, MOSI and CLK are okay, but not CS.
>>> Do you have enabled spi in BIOS HAT configuration?
>>> CS0 should be ok, it's SOC defined, CS1 is optional, users can activate low by
>>> himself before read/write, actually all gpio can be manually used as CS pin.
>>
>> I applied an ACPI overlay. I'll test it again.
>
> I suppose this part is not as critical and I just wonder what the test
> results are.
>
> ...
>
>> Anyway these are not related to this patch series.
>> Thanks for the clarification.
>>
>> Tested-by: Thomas Richard <thomas.richard@bootlin.com>
>
> So, after all, are they all good to go?
Yes,
I tested all functions and it is okay.
It was my fault, my test script did not select pingroup and function
correctly, so FPGA pins were misconfigured.
You can pick my TB tag.
Best Regards,
Thomas
next prev parent reply other threads:[~2026-07-08 12:55 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 [this message]
2026-07-08 14:29 ` [PATCH v4 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=269d40d1-7783-4eca-8cee-3e2001cc6ccc@bootlin.com \
--to=thomas.richard@bootlin.com \
--cc=andy.shevchenko@gmail.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 \
/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