[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bd17efe9-04bf-4cf5-6527-8fdba8d39419@linux.intel.com>
Date: Fri, 26 Jul 2019 12:31:53 -0500
From: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
To: Guennadi Liakhovetski <guennadi.liakhovetski@...ux.intel.com>
Cc: alsa-devel@...a-project.org, tiwai@...e.de,
gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
vkoul@...nel.org, broonie@...nel.org,
srinivas.kandagatla@...aro.org, jank@...ence.com,
slawomir.blauciak@...el.com, Sanyog Kale <sanyog.r.kale@...el.com>
Subject: Re: [alsa-devel] [RFC PATCH 37/40] soundwire: cadence_master: add
hw_reset capability in debugfs
>> +static int cdns_hw_reset(void *data, u64 value)
>> +{
>> + struct sdw_cdns *cdns = data;
>> + int ret;
>> +
>> + if (value != 1)
>> + return 0;
>> +
>> + dev_info(cdns->dev, "starting link hw_reset\n");
>> +
>> + ret = sdw_cdns_exit_reset(cdns);
>> +
>> + dev_info(cdns->dev, "link hw_reset done\n");
>
> Both really should be dev_info()? Maybe at least one of them can be dev_dbg()?
I have to walk back on what I explained to Greg. The idea was to have a
dmesg trace when this function as called when the user plays with
debugfs, otherwise the dmesg log is difficult to interpret (devices can
go off the bus on their own). I'll keep the first one only and demote it
to dev_dbg.
Powered by blists - more mailing lists