[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YZY/VCt8WZx/4dFt@paasikivi.fi.intel.com>
Date: Thu, 18 Nov 2021 13:56:04 +0200
From: Sakari Ailus <sakari.ailus@...ux.intel.com>
To: Jammy Huang <jammy_huang@...eedtech.com>
Cc: eajames@...ux.ibm.com, mchehab@...nel.org, joel@....id.au,
andrew@...id.au, hverkuil-cisco@...all.nl,
gregkh@...uxfoundation.org, laurent.pinchart@...asonboard.com,
linux-media@...r.kernel.org, openbmc@...ts.ozlabs.org,
linux-arm-kernel@...ts.infradead.org,
linux-aspeed@...ts.ozlabs.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 02/10] media: aspeed: use v4l2_info/v4l2_warn/v4l2_dbg
for log
Hi Jammy,
On Thu, Nov 18, 2021 at 03:40:23PM +0800, Jammy Huang wrote:
> The debug log level, 0~3, is controlled by module_param, debug.
> The higher the value, the more the information.
> 0: off
> 1: info
> 2: debug
> 3: register operations
>
> Signed-off-by: Jammy Huang <jammy_huang@...eedtech.com>
Just wondering: what's the purpose of switching to v4l2_*() functions for
printing when dev_*() equivalents already can do the same?
--
Sakari Ailus
Powered by blists - more mailing lists