[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bee6062d-55ad-4577-8478-d20881c5047d@linaro.org>
Date: Wed, 15 Nov 2023 17:09:09 +0000
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: Konrad Dybcio <konrad.dybcio@...aro.org>,
Satya Priya Kakitapalli <quic_skakitap@...cinc.com>,
Andy Gross <agross@...nel.org>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>
Cc: Bjorn Andersson <andersson@...nel.org>,
linux-arm-msm@...r.kernel.org, linux-clk@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH 2/4] clk: qcom: videocc-sm8150: Update the videocc resets
On 15/11/2023 16:48, Konrad Dybcio wrote:
>> + [VIDEO_CC_INTERFACE_BCR] = { 0x9ac },
>> + [VIDEO_CC_MVS0_BCR] = { 0x870 },
>> + [VIDEO_CC_MVS1_BCR] = { 0x8b0 },
>> + [VIDEO_CC_MVSC_BCR] = { 0x810 },
> FWIW this seems to be a copypaste from
>
> https://git.codelinaro.org/clo/la/kernel/msm-5.4/-/blame/92b31370d31d22e910120f6a875bf0919b3f1773/drivers/clk/qcom/videocc-sm8150.c
>
> so if it's an issue, it should probably be fixed downstream too
More of a question than a gotcha - 0x9ac is valid for sm8250 so curious
to me that its a different address on sm8150.
---
bod
Powered by blists - more mailing lists