public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Szuying Chen <chensiying21@gmail.com>
Cc: akpm@linux-foundation.org, dan.j.williams@intel.com,
	gourry@gourry.net, jhubbard@nvidia.com, akinobu.mita@gmail.com,
	sumanthk@linux.ibm.com, peterz@infradead.org,
	huang.ying.caritas@gmail.com, linux-kernel@vger.kernel.org,
	Andrew_Su@asmedia.com.tw, Yd_Tseng@asmedia.com.tw,
	Ed_Huang@asmedia.com.tw, Cindy1_Hsu@asmedia.com.tw,
	Jesse1_Chang@asmedia.com.tw, Richard_Hsu@asmedia.com.tw,
	Chloe_Chen@asmedia.com.tw
Subject: Re: [PATCH] kernel: resourse: Add conditional handling for ACPI device
Date: Thu, 23 Oct 2025 11:51:18 +0300	[thread overview]
Message-ID: <aPnshvGceDWVmtze@smile.fi.intel.com> (raw)
In-Reply-To: <20251023080455.19443-1-Chloe_Chen@asmedia.com.tw>

On Thu, Oct 23, 2025 at 04:04:55PM +0800, Szuying Chen wrote:
> On Sun, Oct 19, 2025 at 03:07AM, Andy Shevchenko wrote:
> > On Fri, Oct 17, 2025 at 10:35:31AM +0800, Szuying Chen wrote:
> > > To avoid address conflicts and related errors, specific checks for
> > > the ACPI device "AMDIF031" should be bypassed.
> > 
> > TL;DR: NAK.
> > 
> > No, this is not how we should do the quirks (besides the use of CamelCase).
> > Also, please provide more info why firmware may not be fixed properly at
> > the same time, so we won't need this on an updated version?
> 
> The ACPI device AMDIF031 is a virtual (non-PCI) device located on the PCI
> upstream port. Its memory resource is assigned by the BIOS within the bridge
> windows of the PCI upstream port.
> 
> When the kernel creates ACPI/AMDIF031 and verifies memory resources, it may
> detect an address conflict between AMDIF031 and the PCI upstream port. The
> kernel then attempts to reassign resources for the PCI upstream port tree,
> causing AMDIF031's memory resource to fall outside the bridge windows. This
> makes the device inaccessible.
> 
> To prevent this and allow AMDIF031 to use the BIOS-assigned memory range,
> skip resource reallocation when an address conflict is detected for this 
> device.

We have such devices in many platforms, older ones use MFD framework with
specific flag set, you may check how it's done there. But for this change is
definitely NAK, take your time to find proper solution (see above for the
hint).

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-10-23  8:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17  2:35 [PATCH] kernel: resourse: Add conditional handling for ACPI device Szuying Chen
2025-10-17 14:11 ` Gregory Price
2025-10-18 19:07 ` Andy Shevchenko
2025-10-23  8:04   ` Szuying Chen
2025-10-23  8:51     ` Andy Shevchenko [this message]
2025-10-20  8:46 ` kernel test robot
2025-10-20 10:01   ` Andy Shevchenko
  -- strict thread matches above, loose matches on Subject: below --
2025-10-27  6:36 Szuying Chen

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=aPnshvGceDWVmtze@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=Andrew_Su@asmedia.com.tw \
    --cc=Chloe_Chen@asmedia.com.tw \
    --cc=Cindy1_Hsu@asmedia.com.tw \
    --cc=Ed_Huang@asmedia.com.tw \
    --cc=Jesse1_Chang@asmedia.com.tw \
    --cc=Richard_Hsu@asmedia.com.tw \
    --cc=Yd_Tseng@asmedia.com.tw \
    --cc=akinobu.mita@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=chensiying21@gmail.com \
    --cc=dan.j.williams@intel.com \
    --cc=gourry@gourry.net \
    --cc=huang.ying.caritas@gmail.com \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=sumanthk@linux.ibm.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