From: Johan Hovold <johan@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Robert Foss <rfoss@kernel.org>, Todor Tomov <todor.too@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] media: qcom: camss: vfe: Stop spamming logs with version
Date: Wed, 30 Apr 2025 14:31:24 +0200 [thread overview]
Message-ID: <aBIYHD3o3wTfvg_g@hovoldconsulting.com> (raw)
In-Reply-To: <3e34ce09-1207-4dba-bff8-38c01cad9b78@linaro.org>
On Wed, Apr 30, 2025 at 10:19:13AM +0200, Krzysztof Kozlowski wrote:
> On 30/04/2025 09:25, Johan Hovold wrote:
> > On Tue, Apr 29, 2025 at 08:08:29PM +0200, Krzysztof Kozlowski wrote:
> >> Camss drivers spam kernel dmesg with 64 useless messages during boot:
> >>
> >> qcom-camss acb7000.isp: VFE:1 HW Version = 3.0.2
> >> qcom-camss acb7000.isp: VFE:2 HW Version = 2.4.0
> >>
> >> All of these messages are the same, so it makes no sense to print same
> >> information 32 times.
> >
> > It's even worse then that (several hundred messages during use) and I
> > sent fixes for these regressions a few weeks ago:
> >
> > https://lore.kernel.org/lkml/20250407104828.3833-1-johan+linaro@kernel.org/
> > https://lore.kernel.org/lkml/20250407085125.21325-1-johan+linaro@kernel.org/
>
> Oh damn...
>
> I developed this on top of next, so already with your fixes included,
> but - following standard kernel coding practice that drivers should be
> silent on success - I think even debug messages are not needed here.
Ah, ok, it's based on my fixes and just removing the debug printks.
I think that should be made more clear in the commit message as debug
printks are not enabled by default and the rules for those are less
strict.
> There is really no point in printing (even as debug) version of hw block
> EVERY TIME I boot the hardware. It does not change, does it?
Well, it doesn't hurt to print it once on probe if this is something
read out from the hardware, but clearly printing it hundreds of times
during use make that debug statement pretty useless.
Johan
next prev parent reply other threads:[~2025-04-30 12:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 18:08 [PATCH 1/3] media: qcom: camss: vfe: Stop spamming logs with version Krzysztof Kozlowski
2025-04-29 18:08 ` [PATCH 2/3] media: qcom: camss: csid: " Krzysztof Kozlowski
2025-04-29 18:08 ` [PATCH 3/3] media: qcom: camss: csiphy: " Krzysztof Kozlowski
2025-04-29 18:11 ` [PATCH 1/3] media: qcom: camss: vfe: " Krzysztof Kozlowski
2025-04-29 19:40 ` Bryan O'Donoghue
2025-04-30 6:15 ` Krzysztof Kozlowski
2025-04-30 7:25 ` Johan Hovold
2025-04-30 8:19 ` Krzysztof Kozlowski
2025-04-30 8:30 ` Bryan O'Donoghue
2025-04-30 8:33 ` Krzysztof Kozlowski
2025-05-20 6:06 ` Krzysztof Kozlowski
2025-05-20 7:53 ` Johan Hovold
2025-05-20 8:02 ` Krzysztof Kozlowski
2025-05-20 8:23 ` Johan Hovold
2025-05-20 8:30 ` Krzysztof Kozlowski
2025-05-20 8:39 ` Johan Hovold
2025-05-20 8:44 ` Bryan O'Donoghue
2025-05-20 8:51 ` Krzysztof Kozlowski
2025-05-20 8:58 ` Bryan O'Donoghue
2025-05-20 9:16 ` Krzysztof Kozlowski
2025-05-20 9:17 ` Johan Hovold
2025-04-30 12:31 ` Johan Hovold [this message]
2025-04-30 8:24 ` Bryan O'Donoghue
2025-04-30 12:34 ` Johan Hovold
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aBIYHD3o3wTfvg_g@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rfoss@kernel.org \
--cc=todor.too@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox