[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <33f40e44-fbfe-42d2-aa23-f77529ee904e@linaro.org>
Date: Sat, 2 Mar 2024 01:09:43 +0100
From: Konrad Dybcio <konrad.dybcio@...aro.org>
To: Unnathi Chalicheemala <quic_uchalich@...cinc.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Bjorn Andersson <andersson@...nel.org>, Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, kernel@...cinc.com
Subject: Re: [PATCH v3 4/5] arm64: dts: qcom: sm8550: Add mapping to llcc
Broadcast_AND region
On 28.02.2024 02:17, Unnathi Chalicheemala wrote:
> On 2/27/2024 7:49 AM, Krzysztof Kozlowski wrote:
>> On 23/02/2024 00:07, Unnathi Chalicheemala wrote:
>>> Mapping Broadcast_AND region for LLCC in SM8550.
"Map" would be grammatically connect here
>>
>> I don't understand this sentence and I still do not know why.
>>
>
> The check of whether status bit is 1 in the driver is being done
> with the wrong register all along (sm8450 onwards). So I am adding
> the base address of the right register region in the DeviceTree files.
>
> I can add this explanation to the commit message of these
> patches if you think that would help.
Yes, the commit message should definitely state the problem, and if
not obvious, the reason for the solution.
Paraphrasing Greg KH (I think?), the maintainers are going to assume
your patch is unnecessary and your job is to convince them that it's
not the case. You do it through good code and meaningful commit titles&
messages.
Please refer to [1].
Konrad
[1] https://www.kernel.org/doc/html/latest/process/submitting-patches.html#describe-your-changes
Powered by blists - more mailing lists