From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Nikita Travkin" <nikita@trvn.ru>
Cc: Hans de Goede <hdegoede@redhat.com>,
Sebastian Reichel <sre@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
cros-qcom-dts-watchers@chromium.org,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-arm-msm@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Subject: Re: [PATCH v4 2/4] platform: Add ARM64 platform directory
Date: Tue, 12 Mar 2024 12:03:20 +0000 [thread overview]
Message-ID: <bc402b70-4b68-4768-b976-8fdbdc61d152@linaro.org> (raw)
In-Reply-To: <4b65793d-0196-0118-6304-b078eaacd482@linux.intel.com>
On 12/03/2024 11:40, Ilpo Järvinen wrote:
> On Tue, 12 Mar 2024, Nikita Travkin wrote:
>
>> Some ARM64 based laptops and computers require vendor/board specific
>> drivers for their embedded controllers. Even though usually the most
>> important functionality of those devices is implemented inside ACPI,
>> unfortunately Linux doesn't currently have great support for ACPI on
>> platforms like Qualcomm Snapdragon that are used in most ARM64 laptops
>> today. Instead Linux relies on Device Tree for Qualcomm based devices
>> and it's significantly easier to reimplement the EC functionality in
>> a dedicated driver than to make use of ACPI code.
>>
>> This commit introduces a new platform/arm64 subdirectory to give a
>> place to such drivers for EC-like devices.
>>
>> A new MAINTAINERS entry is added for this directory. Patches to files in
>> this directory will be taken up by the platform-drivers-x86 team (i.e.
>> Hans de Goede and Mark Gross).
>
> Mark -> me.
>
>> +ARM64 PLATFORM DRIVERS
>> +M: Hans de Goede <hdegoede@redhat.com>
>> +M: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
>> +L: platform-driver-x86@vger.kernel.org
>> +S: Maintained
>> +Q: https://patchwork.kernel.org/project/platform-driver-x86/list/
>> +T: git git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git
>> +F: drivers/platform/arm64/
>
> Is some ARM64 person going to pay attention to these patches (you or
> perhaps somebody else)?
>
> It's perfectly fine to have some ARM64 person(s) listed as an additional
> maintainer there even if the patches themselves are routed through Hans
> and me (and pdx86 tree). With Mellanox and Surface platform drivers which
> are also routed through pdx86 tree, we have Hans + me + 3rd person listed
> as maintainers.
You can add me as a +R.
Perhaps Dmitry and Konrad would want to be on the list too.
Actually since Dmitry has already done some work on this, I think he
should be on the review list for this series.
Adding..
>
> (This is not to force anything on anyone but it could be beneficial if
> somebody more familiar with ARM64 is in the loop.)
---
bod
next prev parent reply other threads:[~2024-03-12 12:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 8:42 [PATCH v4 0/4] platform: arm64: Acer Aspire 1 embedded controller Nikita Travkin
2024-03-12 8:42 ` [PATCH v4 1/4] dt-bindings: platform: Add Acer Aspire 1 EC Nikita Travkin
2024-03-12 14:39 ` Rob Herring
2024-03-12 8:42 ` [PATCH v4 2/4] platform: Add ARM64 platform directory Nikita Travkin
2024-03-12 11:36 ` Bryan O'Donoghue
2024-03-12 11:45 ` Ilpo Järvinen
2024-03-12 11:55 ` Nikita Travkin
2024-03-12 11:40 ` Ilpo Järvinen
2024-03-12 12:00 ` Nikita Travkin
2024-03-12 12:03 ` Bryan O'Donoghue [this message]
2024-03-12 8:42 ` [PATCH v4 3/4] platform: arm64: Add Acer Aspire 1 embedded controller driver Nikita Travkin
2024-03-12 11:58 ` Bryan O'Donoghue
2024-03-12 12:23 ` Nikita Travkin
2024-03-12 12:44 ` Bryan O'Donoghue
2024-03-12 14:09 ` Nikita Travkin
2024-03-12 12:31 ` Ilpo Järvinen
2024-03-12 14:03 ` Nikita Travkin
2024-03-12 8:42 ` [PATCH v4 4/4] arm64: dts: qcom: acer-aspire1: Add embedded controller Nikita Travkin
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=bc402b70-4b68-4768-b976-8fdbdc61d152@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikita@trvn.ru \
--cc=platform-driver-x86@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sre@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.