From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Maximilian Luz <luzmaximilian@gmail.com>
Cc: "Konrad Dybcio" <konradybcio@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Len Brown" <lenb@kernel.org>,
"Hans de Goede" <hdegoede@redhat.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Marijn Suijten" <marijn.suijten@somainline.org>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-acpi@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <quic_kdybcio@quicinc.com>
Subject: Re: [PATCH v3 3/3] platform/surface: Add OF support
Date: Wed, 28 Aug 2024 22:06:29 +0300 [thread overview]
Message-ID: <CAHp75VdsksKPrj-CwmR4QLBrm_FfaG4aZys-_jnee_L=3ZnRPQ@mail.gmail.com> (raw)
In-Reply-To: <53a56539-1d95-42ac-ad07-1b689702b2ed@gmail.com>
On Wed, Aug 28, 2024 at 8:40 PM Maximilian Luz <luzmaximilian@gmail.com> wrote:
> On 8/28/24 6:56 PM, Andy Shevchenko wrote:
> > On Wed, Aug 28, 2024 at 12:10 PM Maximilian Luz <luzmaximilian@gmail.com> wrote:
...
> > Yes, and software nodes for DT are quite strange things! Why can't you
> > simply fix the DT to begin with?
>
> For the ARM/DT variants we could do that. But we still have to deal with
> the x86/ACPI ones here.
So, then fix it there! Currently it's an abuse of software nodes
inside the Linux kernel.
> So for me it makes more sense to have it unified
> and just deal with everything in this module.
I understand the desire, but DT is DT and ACPI is ACPI, they are
different despite having some common APIs in the Linux kernel.
Moreover, DT has a validation tools and everything, making that being
a software nodes has at least these disadvantages:
- no official schema that must be supported and users are known of
- no validation done
- bloating of the Linux kernel binary and hence memory footprint
> Also, if we consider that at some point we might get ACPI PEP support (I
> know, far fetched right now): With that, ACPI on ARM might be feasible
> and then we'd have to manage the same thing in two places...
This (PEP) is something I have no knowledge about. But I think it's
still orthogonal to the software nodes usage.
> And lastly, the EC subdevices are quite contained and I don't see them
> interacting with any other components in the DT, so it's more of a
> stylistic choice where to put them.
They are still part of hardware and DT describes hardware.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-08-28 19:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 10:27 [PATCH v3 0/3] OF support for Surface System Aggregator Module Konrad Dybcio
2024-08-14 10:27 ` [PATCH v3 1/3] dt-bindings: serial: Allow embedded-controller as child node Konrad Dybcio
2024-08-14 10:27 ` [PATCH v3 2/3] dt-bindings: platform: Add Surface System Aggregator Module Konrad Dybcio
2024-08-14 14:06 ` Krzysztof Kozlowski
2024-08-14 10:27 ` [PATCH v3 3/3] platform/surface: Add OF support Konrad Dybcio
2024-08-16 18:23 ` Maximilian Luz
2024-08-26 20:54 ` Andy Shevchenko
2024-08-27 9:07 ` Hans de Goede
2024-08-27 13:52 ` Konrad Dybcio
2024-08-27 14:04 ` Hans de Goede
2024-08-28 9:10 ` Maximilian Luz
2024-08-28 16:56 ` Andy Shevchenko
2024-08-28 17:40 ` Maximilian Luz
2024-08-28 19:06 ` Andy Shevchenko [this message]
2024-08-30 12:57 ` Konrad Dybcio
2024-08-19 11:57 ` [PATCH v3 0/3] OF support for Surface System Aggregator Module Hans de Goede
2024-08-19 13:27 ` Konrad Dybcio
2024-08-19 20:07 ` Maximilian Luz
2024-08-26 20:55 ` 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='CAHp75VdsksKPrj-CwmR4QLBrm_FfaG4aZys-_jnee_L=3ZnRPQ@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=luzmaximilian@gmail.com \
--cc=marijn.suijten@somainline.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=quic_kdybcio@quicinc.com \
--cc=rafael@kernel.org \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).