From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: "BillyChou 周博倫" <BillyChou@aaeon.com.tw>
Cc: GaryWang <is0124@gmail.com>,
"JunYingLai 賴俊穎" <JunYingLai@aaeon.com.tw>,
"Thomas Richard" <thomas.richard@bootlin.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"JasonHuang 黃仁杰" <JasonHuang@aaeon.com.tw>
Subject: Re: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?
Date: Thu, 20 Aug 2026 09:23:39 +0300 [thread overview]
Message-ID: <aoadazG84iGSWCuI@ashevche-desk.local> (raw)
In-Reply-To: <KL1PR02MB7239DF2E12270CC4B58F55429FA42@KL1PR02MB7239.apcprd02.prod.outlook.com>
On Thu, Aug 20, 2026 at 05:19:06AM +0000, BillyChou 周博倫 wrote:
> > On Mon, Aug 10, 2026 at 04:17:43AM +0000, BillyChou 周博倫 wrote:
> > > Dear Andy,
> > >
> > > Thank you for your feedback, and we sincerely apologize for the delay.
> > >
> > > We are currently updating the BIOS to configure the HAT connector pins
> > > to GPIO/GPO mode, which will ensure interrupt support on the OS side.
> > > We will update the BIOS as soon as possible and share it with you for testing.
> > >
> > > Thanks again for your patience and support.
> >
> > Thanks for the good news, I'm looking forward to test it!
> >
> The updated BIOS for the UPN-ADLN01 project with the HAT connector pin configurations is ready. Kindly download it here for testing:
> https://aaeon365-my.sharepoint.com/personal/nas_aaeon_com_tw/_layouts/15/onedrive.aspx?id=%2Fpersonal%2Fnas%5Faaeon%5Fcom%5Ftw%2FDocuments%2F007%E8%BB%9F%E9%AB%94%E9%96%8B%E7%99%BC%E8%99%95%2FBIOS%2F%5FReleased%5FBIOS%2FUPN%2DADLN01%2FUNASAM36%2Ezip&parent=%2Fpersonal%2Fnas%5Faaeon%5Fcom%5Ftw%2FDocuments%2F007%E8%BB%9F%E9%AB%94%E9%96%8B%E7%99%BC%E8%99%95%2FBIOS%2F%5FReleased%5FBIOS%2FUPN%2DADLN01&ga=1&LOF=1
Hmm... I can't login there with my @intel.com account. I suppose that share is
only for your company. Maybe MS Teams will work better?
> > > -----Original Message-----
> > > From: JunYingLai 賴俊穎 <JunYingLai@aaeon.com.tw>
> > > Sent: Thursday, July 23, 2026 2:48 PM
> > > To: BillyChou 周博倫 <BillyChou@aaeon.com.tw>
> > > Subject: FW: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?
> > >
> > > FYI
> > >
> > > Best Regards,
> > > JunYing Lai
> > >
> > > JunYing Lai
> > > AAEON Technology Inc.
> > > 5F, No. 135, Lane 235, Pao Chiao Rd.
> > > Hsin-Tien Dist, New Taipei City, 231
> > > Taiwan, R.O.C.
> > >
> > >
> > > TEL: +886-2-8919-1234 Ext.1891
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Andy Shevchenko <andriy.shevchenko@intel.com>
> > > Sent: Friday, July 10, 2026 5:11 PM
> > > To: GaryWang <is0124@gmail.com>
> > > Cc: JunYingLai 賴俊穎 <JunYingLai@aaeon.com.tw>; Thomas Richard
> > > <thomas.richard@bootlin.com>; linux-gpio@vger.kernel.org; JasonHuang
> > > 黃仁杰 <JasonHuang@aaeon.com.tw>
> > > Subject: Re: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?
> > >
> > > 這是外部郵件:在打開連結和附件之前,請確保電子郵件是安全的。 This
> > is an external email: please make sure the email is secure before opening links
> > and attachments.
> > >
> > > On Fri, Jul 10, 2026 at 04:37:56PM +0800, GaryWang wrote:
> > > > Add AAEON software JunYing.
> > >
> > > Thanks, waiting for the response!
> > >
> > > > yeah the ACPI flag should not set for HAT pins, JunYin knows it,
> > > > They clear the ACPI flag from the driver now, their BIOS uses the
> > > > default from CRB, but they should fix it from the BIOS to match the right
> > usage.
> > >
> > > How do they clean it from the driver? IIRC the ownership registers are
> > > locked when BIOS hands over to the OS. Technically any pin that marked
> > > as GPIO input must not be owned by ACPI to allow users to connect
> > > whatever they want there and get an interrupts. Many of them also have
> > > "Locked full" permissions, that's also may not be convenient. Another
> > > thing is the absence of bi-di GPIO configuration (or did I miss
> > > that?), which people may want to have (my use case, for instance).
> > >
> > > In any case I have latest and greatest BIOS version (r3.5 of this
> > > year) and problem still persists. Can AAEON share a BIOS for testing?
> > > (Note, if you want, it can be done under our Intel-AAEON existing NDA,
> > > I believe.)
> > >
> > > > On Fri, Jul 10, 2026 at 4:48 AM Andy Shevchenko
> > > > <andriy.shevchenko@intel.com> wrote:
> > > > >
> > > > > Since I have been playing with the $Subject board, I wondering if
> > > > > I miss something or the BIOS configuration is utterly broken. The
> > > > > problem what I see is that most of the pins on the SoC are marked
> > > > > with [ACPI] if you look at the debugfs 'pins' file for INTC1057:00 device
> > instance.
> > > > >
> > > > > This means *none* of them (which are user visible via HAT
> > > > > connector) may serve as an interrupt resource to the OS. How the
> > > > > OS should request interrupts on those pins?
> > > > >
> > > > > As far as I understand that the BIOS does initial settings of CPLD
> > > > > and basically I can use transparently the pins as per their
> > > > > configuration done in BIOS. Right?
> > > > >
> > > > > Btw, do we have any contacts to engineers in AAEON or whoever who
> > > > > does these UP boards nowadays?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-08-20 6:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 20:48 Up Squared Pro 7000 (UPN-ADLN01) broken BIOS? Andy Shevchenko
2026-07-10 8:37 ` GaryWang
2026-07-10 9:11 ` Andy Shevchenko
[not found] ` <TY1PPFA4928F5D95D0BFF5F087E44F8B166F0C02@TY1PPFA4928F5D9.apcprd02.prod.outlook.com>
2026-08-10 4:17 ` BillyChou 周博倫
2026-08-10 7:22 ` Andy Shevchenko
2026-08-20 5:19 ` BillyChou 周博倫
2026-08-20 6:23 ` Andy Shevchenko [this message]
2026-08-20 6:24 ` Andy Shevchenko
2026-08-20 10:04 ` BillyChou 周博倫
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=aoadazG84iGSWCuI@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=BillyChou@aaeon.com.tw \
--cc=JasonHuang@aaeon.com.tw \
--cc=JunYingLai@aaeon.com.tw \
--cc=is0124@gmail.com \
--cc=linux-gpio@vger.kernel.org \
--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