[PATCH v5 02/10] media: aspeed: use v4l2_info/v4l2_warn/v4l2_dbg for log

Sakari Ailus sakari.ailus at linux.intel.com
Thu Nov 18 22:56:04 AEDT 2021


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 at aspeedtech.com>

Just wondering: what's the purpose of switching to v4l2_*() functions for
printing when dev_*() equivalents already can do the same?

-- 
Sakari Ailus


More information about the openbmc mailing list