linux-kernel - Re: [PATCH v4 2/4] platform: Add ARM64 platform directory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4b65793d-0196-0118-6304-b078eaacd482@linux.intel.com>
Date: Tue, 12 Mar 2024 13:40:33 +0200 (EET)
From: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
To: Nikita Travkin <nikita@...n.ru>
cc: Hans de Goede <hdegoede@...hat.com>, Sebastian Reichel <sre@...nel.org>, 
    Rob Herring <robh+dt@...nel.org>, 
    Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>, 
    Conor Dooley <conor+dt@...nel.org>, cros-qcom-dts-watchers@...omium.org, 
    Andy Gross <agross@...nel.org>, Bjorn Andersson <andersson@...nel.org>, 
    Konrad Dybcio <konrad.dybcio@...aro.org>, Rob Herring <robh@...nel.org>, 
    devicetree@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>, 
    linux-arm-msm@...r.kernel.org, platform-driver-x86@...r.kernel.org
Subject: Re: [PATCH v4 2/4] platform: Add ARM64 platform directory

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@...hat.com>
> +M:	Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
> +L:	platform-driver-x86@...r.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.

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

-- 
 i.