[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4495a6a7-7b43-4c22-a415-55b346528a7d@linaro.org>
Date: Tue, 20 May 2025 09:58:42 +0100
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Johan Hovold <johan@...nel.org>
Cc: Robert Foss <rfoss@...nel.org>, Todor Tomov <todor.too@...il.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>, linux-media@...r.kernel.org,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] media: qcom: camss: vfe: Stop spamming logs with
version
On 20/05/2025 09:51, Krzysztof Kozlowski wrote:
> qcom-camss ac5a000.camss: VFE:0 HW Version = 1.2.2
> qcom-camss ac5a000.camss: VFE:1 HW Version = 1.2.2
> qcom-camss ac5a000.camss: VFE:2 HW Version = 1.2.2
> qcom-camss ac5a000.camss: VFE:3 HW Version = 1.2.2
> qcom-camss ac5a000.camss: VFE:4 HW Version = 1.3.0
> qcom-camss ac5a000.camss: VFE:5 HW Version = 1.3.0
> qcom-camss ac5a000.camss: VFE:6 HW Version = 1.3.0
> qcom-camss ac5a000.camss: VFE:7 HW Version = 1.3.0
This prints the hardware version of eight distinct hardware blocks VFE
index increases.
TBH I still find this useful when debugging hardware.
My personal preference is to print it once on boot and skip subsequent.
Which I think is perfectly reasonable for DEBUG scenario.
---
bod
Powered by blists - more mailing lists