[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a2ae92ad-63c0-42bf-8695-c7e3967c776a@linaro.org>
Date: Thu, 9 Nov 2023 17:52:49 +0000
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: Konrad Dybcio <konrad.dybcio@...aro.org>, hverkuil-cisco@...all.nl,
laurent.pinchart@...asonboard.com, Andy Gross <agross@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Robert Foss <rfoss@...nel.org>,
Todor Tomov <todor.too@...il.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>, vincent.knecht@...loo.org,
matti.lehtimaki@...il.com, quic_grosikop@...cinc.com
Cc: linux-arm-msm@...r.kernel.org, linux-media@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 4/6] media: qcom: camss: Add sc8280xp resource details
On 09/11/2023 13:44, Konrad Dybcio wrote:
>> + .clock_rate = { { 400000000, 400000000, 480000000, 600000000,
>> 600000000, 600000000 },
> (why is it 400, 400, 480, 600, 600, 600 and not 400, 480, 600?)
Because I've listed every operating point clock instead of just the list
of frequencies..
I will change.
---
bod
Powered by blists - more mailing lists