Received-SPF: pass (google.com: domain of linux-kernel+bounces-100185-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
From: =?UTF-8?q?Ilpo=20J=C3=A4rvinen?= <ilpo.jarvinen@linux.intel.com>
Date: Tue, 12 Mar 2024 13:40:33 +0200 (EET)
To: 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
Subject: Re: [PATCH v4 2/4] platform: Add ARM64 platform directory
In-Reply-To: <20240312-aspire1-ec-v4-2-bd8e3eea212f@trvn.ru>
Message-ID: <4b65793d-0196-0118-6304-b078eaacd482@linux.intel.com>
References: <20240312-aspire1-ec-v4-0-bd8e3eea212f@trvn.ru> <20240312-aspire1-ec-v4-2-bd8e3eea212f@trvn.ru>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/mixed; BOUNDARY="8323328-1144789663-1710242525=:1770"
Content-ID: <b7f13e73-3ca3-ec79-a583-7abde67e6d5e@linux.intel.com>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--8323328-1144789663-1710242525=:1770
Content-Type: text/plain; CHARSET=ISO-8859-15
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-ID: <681a33ea-5fa2-89db-0a66-473a5eec5c16@linux.intel.com>

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.
>=20
> This commit introduces a new platform/arm64 subdirectory to give a
> place to such drivers for EC-like devices.
>=20
> 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:=09Hans de Goede <hdegoede@redhat.com>
> +M:=09Ilpo J=E4rvinen <ilpo.jarvinen@linux.intel.com>
> +L:=09platform-driver-x86@vger.kernel.org
> +S:=09Maintained
> +Q:=09https://patchwork.kernel.org/project/platform-driver-x86/list/
> +T:=09git git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-dr=
ivers-x86.git
> +F:=09drivers/platform/arm64/

Is some ARM64 person going to pay attention to these patches (you or=20
perhaps somebody else)?

It's perfectly fine to have some ARM64 person(s) listed as an additional=20
maintainer there even if the patches themselves are routed through Hans=20
and me (and pdx86 tree). With Mellanox and Surface platform drivers which=
=20
are also routed through pdx86 tree, we have Hans + me + 3rd person listed=
=20
as maintainers.

(This is not to force anything on anyone but it could be beneficial if=20
somebody more familiar with ARM64 is in the loop.)

--=20
 i.
--8323328-1144789663-1710242525=:1770--