Devicetree
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Hans de Goede <johannes.goede@oss.qualcomm.com>,
	Sudeep Holla <sudeep.holla@kernel.org>,
	"Rafael J . Wysocki" <rafael@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Srinivas Kandagatla <srini@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Dmitry Baryshkov <lumag@kernel.org>,
	Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
	Abel Vesa <abel.vesa@oss.qualcomm.com>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-acpi@vger.kernel.org
Subject: Re: [RFC 00/12] RFC: Devicetree-ACPI hybrid mode
Date: Mon, 29 Jun 2026 09:22:02 +0100	[thread overview]
Message-ID: <20260629-optimal-vermilion-salamander-0190fc@sudeepholla> (raw)
In-Reply-To: <2dbfkh3djdrvklsin7zcy53g3wpc76dd4iosxgahbd26zssmx5@zpkplzscllx3>

On Sun, Jun 28, 2026 at 10:23:15PM +0300, Dmitry Baryshkov wrote:
> On Sat, Jun 27, 2026 at 03:12:31PM +0100, Sudeep Holla wrote:
> > On Fri, Jun 26, 2026 at 11:57:47PM +0300, Dmitry Baryshkov wrote:
> > > On Fri, Jun 26, 2026 at 04:52:41PM +0100, Sudeep Holla wrote:
> > > > On Tue, Jun 23, 2026 at 04:52:13PM +0200, Hans de Goede wrote:
> > > > > Hi All,
> > > > > 
> > > > > Currently as soon as the kernel boots with a populated DT provided then
> > > > > the arch/arm64 code sets acpi_disabled=1 and the complete ACPI subsystem
> > > > > gets disabled. On WoA Snapdragon laptops where the factory Windows OS
> > > > > actually boots using these tables this is not necessarily desirable.
> > > > > 
> > > > 
> > > > I am bit lost reading the very first statement here.
> > > > 
> > > > Who is populating DT and why ? It seems that is the source of the problem.
> > > > 
> > > > If windows can boot with ACPI tables, why is it causing issues for the
> > > > Linux kernel, any specifics?
> > > 
> > > Windows uses a separate beast called PEP, which nobody wanted to
> > > implement for these platforms up to now. You can find a lot of ACPI
> > > dumps for these devices at [1].
> > > 
> > 
> > Agreed and I assume that is the reason why we want DT.
> 
> Not completely... Using DT forces us to reimplement bits and pieces for
> these laptops. E.g. drivers for EC, battery, etc.
> 

Not entirely clear still. I mean use ACPI for those as well.

> > 
> > > > IOW why is DT populated which creates the problem you are trying to address
> > > > here.
> > > 
> > > Most of the laptops resemble other Qualcomm platforms, which use DT for
> > > hardware description. In some cases, it is the same platform being used
> > > for both mobile, IoT and laptops. It was more or less natural to reuse
> > > existing support.
> > > 
> > 
> > Sure, just use DT then, why are we even talking about mixed/hybrid mode.
> > It gives no incentive to OEMs using PEP to get away from it and use
> > standard ACPI or improve if anything is missing.
> 
> Well. Here we are talking about the laptops which were being sold since
> 2018. I doubt there will be a UEFI update for all these models.
> 

This problem is discussed multiple times and yet OEMs are not interested in
fixing it 🙁.

> > 
> > So I don't like this idea of mixing at all. Use ACPI or DT, make up you
> > mind. You can't expect to get the best of both worlds if you are not improving
> > the missing parts in either of those. This is just a shortcut.
> 
> So, if we need to append the DSDT, what would be the best way to do it?
> Something like Surface platform drivers, providing extra device nodes?
> 

CONFIG_ACPI_TABLE_UPGRADE allows to override the ACPI tables via initrd IIRC.

-- 
Regards,
Sudeep

  reply	other threads:[~2026-06-29  8:22 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <pskkNka1-QtLVb1tcyyUSjNNeMAWUUOLyvn0XSpq55AyeqXnEjOWDCXF1pWVAufJEya52NTx6ZCXz5dMHcMlyQ==@protonmail.internalid>
2026-06-23 14:52 ` [RFC 00/12] RFC: Devicetree-ACPI hybrid mode Hans de Goede
2026-06-23 14:52   ` [RFC 01/12] ACPI: Introduce DT-ACPI " Hans de Goede
2026-06-23 14:52   ` [RFC 02/12] arm64: acpi: Cleanup acpi=[on|off|force] handling Hans de Goede
2026-06-23 14:52   ` [RFC 03/12] arm64: acpi: add acpi=hybrid support Hans de Goede
2026-06-23 14:52   ` [RFC 04/12] ACPI: Add helpers for dealing with ACPI fwnode as secondary fwnode Hans de Goede
2026-06-23 14:52   ` [RFC 05/12] ACPI: glue: Implement setting secondary-fwnode for DT-ACPI hybrid mode Hans de Goede
2026-06-23 14:52   ` [RFC 06/12] ACPI: scan: Retry acpi_device_notify() in " Hans de Goede
2026-06-23 14:52   ` [RFC 07/12] ACPI: Make device_match_acpi_handle() also check the secondary fwnode Hans de Goede
2026-06-23 14:52   ` [RFC 08/12] irqchip/gic-v3: Always call acpi_set_irq_model() Hans de Goede
2026-06-23 14:52   ` [RFC 09/12] pinctrl: qcom: Add support for WoA ACPI tables virtual TLMM pin numbers Hans de Goede
2026-06-29  1:59     ` Bjorn Andersson
2026-06-29 10:30       ` Hans de Goede
2026-06-23 14:52   ` [RFC 10/12] i2c: acpi: Also register ACPI i2c_clients for adapters with a secondary ACPI fwnode Hans de Goede
2026-06-23 14:52   ` [RFC 11/12] i2c: qcom-geni: Fall back to i2c_acpi_find_bus_speed() Hans de Goede
2026-06-23 14:52   ` [RFC 12/12] arm64: dts: qcom: x1e78100-thinkpad-t14s: Move keyb and touchpad to ACPI enumeration Hans de Goede
2026-06-29  1:43     ` Bjorn Andersson
2026-06-29 10:19       ` Hans de Goede
2026-06-25 10:18   ` [RFC 00/12] RFC: Devicetree-ACPI hybrid mode Konrad Dybcio
2026-06-26 14:33   ` Bryan O'Donoghue
2026-06-26 14:43     ` Bryan O'Donoghue
2026-06-29  1:34       ` Bjorn Andersson
2026-06-29  8:41         ` Bryan O'Donoghue
2026-06-26 15:52   ` Sudeep Holla
2026-06-26 20:57     ` Dmitry Baryshkov
2026-06-27 14:12       ` Sudeep Holla
2026-06-28 19:23         ` Dmitry Baryshkov
2026-06-29  8:22           ` Sudeep Holla [this message]
2026-06-29  2:27   ` Bjorn Andersson
2026-06-29 10:07     ` Hans de Goede
2026-06-29 11:48   ` Hanjun Guo

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=20260629-optimal-vermilion-salamander-0190fc@sudeepholla \
    --to=sudeep.holla@kernel.org \
    --cc=abel.vesa@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=bartosz.golaszewski@oss.qualcomm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=johannes.goede@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=lumag@kernel.org \
    --cc=rafael@kernel.org \
    --cc=srini@kernel.org \
    /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