Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: Nikita Travkin <nikita@trvn.ru>,
	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
Subject: Re: [PATCH v4 2/4] platform: Add ARM64 platform directory
Date: Tue, 12 Mar 2024 13:45:25 +0200 (EET)	[thread overview]
Message-ID: <cc8c8b42-1f6e-3b2c-0e1a-b71b57ab43c8@linux.intel.com> (raw)
In-Reply-To: <5d4434fc-862e-4430-a2a0-758887d7596d@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 2715 bytes --]

On Tue, 12 Mar 2024, Bryan O'Donoghue wrote:

> On 12/03/2024 08:42, 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).
> > 
> > Signed-off-by: Nikita Travkin <nikita@trvn.ru>
> > ---
> >   MAINTAINERS                     |  9 +++++++++
> >   drivers/platform/Kconfig        |  2 ++
> >   drivers/platform/Makefile       |  1 +
> >   drivers/platform/arm64/Kconfig  | 19 +++++++++++++++++++
> >   drivers/platform/arm64/Makefile |  6 ++++++
> >   5 files changed, 37 insertions(+)
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index b43102ca365d..ec8d706a99aa 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -3050,6 +3050,15 @@ F:	drivers/mmc/host/sdhci-of-arasan.c
> >   N:	zynq
> >   N:	xilinx
> >   +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
> 
> Surely some sort of Arm specific mailing list should be added here ?
> platform-drivers-x86 for arm64 platform drivers standalone, makes little
> sense.
> 
> Perhaps for each new SoC class added - you could add the appropriate mailing
> list linux-arm-msm is suspiciously missing from the list even though the only
> driver that will live in this directory after this series is a qcom based
> device.
> 
> And if tomorrow someone added a Rockchip based EC controller then you'd assume
> the rockchip mailing list should get a ping.

While generic arm mailing list is perhaps lacking too, for specific 
driver related lists it is better to add separate MAINTAINERS entries for 
the particular driver and put L: there.

-- 
 i.

  reply	other threads:[~2024-03-12 11:45 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 [this message]
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
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=cc8c8b42-1f6e-3b2c-0e1a-b71b57ab43c8@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=cros-qcom-dts-watchers@chromium.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hdegoede@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox