Re: [PATCH] cmd: fuse: add switch for quiet operation

[Rogerio Guerra Borin <rogerio.borin@toradex.com>]

Hello Quentin,

Thanks for you feedback.

On 3/24/25 06:55, Quentin Schulz wrote:
> I think this is a reasonable expectation. I'm wondering if we shouldn't 
> think about using the log architecture we have to have a generic 
> solution rather than expecting each command driver to handle (possibly 
> in their own way) a quiet flag.
> 
> https://docs.u-boot.org/en/latest/develop/logging.html
> 
> The idea I have in mind is that we could dynamically set the loglevel 
> for a specific command driver (or at least for the command subsystem (by 
> e.g. defining an LOG_CATEGORY LOGC_CMD) and use log_* functions in the 
> command driver rather than IF_NOT_QUIET() below. This would also allow 
> different log levels to be used. Maybe there's something to be done with 
> filters, or something new needs to be added to set the log level for a 
> category maybe? I don't know, not too verse in our log system.
> 
> Another option to have a generic logic would be to depend on an 
> environment variable instead of needing to expand each command driver's 
> logic.

That's a great idea. I'll look into it and get back when I have something.

Regards,
Rogerio