linux-kernel - Re: [PATCH v4 3/3] arm64: dts: qcom: lemans-evk-camera: Add DT overlay

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] [day] [month] [year] [list]

Message-ID: <060d79dc-af41-455e-8f64-29b6967e363a@qualcomm.com>
Date: Thu, 11 Sep 2025 19:02:48 +0800
From: Wenmeng Liu <quic_wenmliu@...lcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
CC: Loic Poulain <loic.poulain@....qualcomm.com>,
        Robert Foss
	<rfoss@...nel.org>, Andi Shyti <andi.shyti@...nel.org>,
        Rob Herring
	<robh@...nel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Conor Dooley
	<conor+dt@...nel.org>,
        Bjorn Andersson <andersson@...nel.org>,
        Konrad Dybcio
	<konradybcio@...nel.org>, <todor.too@...il.com>,
        <bryan.odonoghue@...aro.org>, <vladimir.zapolskiy@...aro.org>,
        <linux-i2c@...r.kernel.org>, <linux-arm-msm@...r.kernel.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <linux-media@...r.kernel.org>,
        Konrad Dybcio <konrad.dybcio@....qualcomm.com>
Subject: Re: [PATCH v4 3/3] arm64: dts: qcom: lemans-evk-camera: Add DT
 overlay



On 9/11/2025 6:15 PM, Dmitry Baryshkov wrote:
> On Thu, Sep 11, 2025 at 01:45:59PM +0800, Wenmeng Liu wrote:
>>
>>
>> On 9/10/2025 11:23 PM, Dmitry Baryshkov wrote:
>>> On Wed, Sep 10, 2025 at 07:06:23PM +0800, Wenmeng Liu wrote:
>>>> Enable IMX577 via CCI1 on LeMans EVK Core Kit.
>>>
>>> Is it a part of the Core Kit? Is it a part of some kind of mezzanine
>>> board? Why is it being enabled as an overlay instead of being a part of
>>> lemans-evk.dts?
>>>
>> Since the sensor is not part of the default hardware configuration on the
>> core kit, we adopt a device tree overlay solution to enable its integration
>> dynamically.
> 
> This is less helpful than a similar response to the similar monaco-evk
> question.
> 
> Is it the only configuration that we are going to support? If not, then
> the overlay should be named accordingly.
> 
> These details should be described in the commit message.
> 

Sure, I will update the commit message with an explanation in the next 
version.

Thanks,
Wenmeng