From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 59362440637 for ; Thu, 20 Aug 2026 06:23:44 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787207026; cv=none; b=IcHtBb2DtQx2Fp9u/U5EGoJ7bSh4toi67u8s7iG4sFigDCPajRQnr2Hjf82DR4Et0LXc/xLTE4vWxS9LiHsJc9KYF/2ycwzh9TGTKR6X8NP1D4h1nqWxkGTj9f8ytlr+6l2iiH9DmBEJBnhEcr0jEnwW+thEBi02ESediSE1awE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787207026; c=relaxed/simple; bh=b3tUFtai73ayhfA5LK1YBONB31/KHIilOqRtUKsS00c=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=FOs2tcs6OsjVAGz44AdexHTzjEX5cSpFhYYM7+dYge5uj1TBxZEb+b9ywvuEoP/d9ktalY1/CFRITyeYw7AghXKB3Qk+UrPC/YhzGck5/8ECxrqqBeM+46XrxbFTvWoZ05gnK8+d5M1aV7Q7EuhTG1O4bGvEBUWad7p2NVALW3I= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com; spf=pass smtp.mailfrom=intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=Xa7Q7T2O; arc=none smtp.client-ip=192.198.163.18 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="Xa7Q7T2O" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1787207024; x=1818743024; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=b3tUFtai73ayhfA5LK1YBONB31/KHIilOqRtUKsS00c=; b=Xa7Q7T2OwAYkIQog+JzSlN32PTIltjd24cIF5FHaxdNvm6KHJRbSWJ/X Xvu4T68RANb3C5mwWYtnhJdnS1Fl62UqifFOJWdpldHqbQFfdysq/9BJ5 /RZC4cjSqEN+riAS/+X2IGWVWteyHhQxhnHtQSk/Nek9K6QKaxCEnV5AM wQLBtLBiD4IYFW1p4GEe1pSuG4SN2pRH4MiIampAWeAlUJdw2W9PH1qao Ialu/e+EhwohBQ2iRXFtCj1yF3UNXoYcSLm8n5LTegs6Fwg8pAg6HdaFM g2Jt+MG4MDVJpt5nB3JJ0j/rhn+hn1qrYNZWcJE59gxngz716XF/or24y w==; X-CSE-ConnectionGUID: fVIcRkXTQBq5NW7UBR7xNw== X-CSE-MsgGUID: bVHeNRmxRee5gcQMGBg4Fg== X-IronPort-AV: E=McAfee;i="6800,10657,11880"; a="86850016" X-IronPort-AV: E=Sophos;i="6.25,232,1779174000"; d="scan'208";a="86850016" Received: from orviesa003.jf.intel.com ([10.64.159.143]) by fmvoesa112.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Aug 2026 23:23:44 -0700 X-CSE-ConnectionGUID: 2fAsQ9KeSzS+cjd6CeAH/A== X-CSE-MsgGUID: 0FZPZEJpQn2aJAQzMpJe7g== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.25,232,1779174000"; d="scan'208";a="269364405" Received: from rvuia-mobl.ger.corp.intel.com (HELO localhost) ([10.245.245.1]) by ORVIESA003-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Aug 2026 23:23:42 -0700 Date: Thu, 20 Aug 2026 09:23:39 +0300 From: Andy Shevchenko To: BillyChou =?utf-8?B?5ZGo5Y2a5YCr?= Cc: GaryWang , JunYingLai =?utf-8?B?6LO05L+K56mO?= , Thomas Richard , "linux-gpio@vger.kernel.org" , JasonHuang =?utf-8?B?6buD5LuB5p2w?= Subject: Re: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS? Message-ID: References: Precedence: bulk X-Mailing-List: linux-gpio@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - c/o Alberga Business Park, 6 krs, Bertel Jungin Aukio 5, 02600 Espoo 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 賴俊穎 > > > Sent: Thursday, July 23, 2026 2:48 PM > > > To: BillyChou 周博倫 > > > 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 > > > Sent: Friday, July 10, 2026 5:11 PM > > > To: GaryWang > > > Cc: JunYingLai 賴俊穎 ; Thomas Richard > > > ; linux-gpio@vger.kernel.org; JasonHuang > > > 黃仁杰 > > > 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 > > > > 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