From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Vinod Koul <vkoul@kernel.org>,
Bard Liao <yung-chuan.liao@linux.intel.com>
Cc: alsa-devel@alsa-project.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, hui.wang@canonical.com,
sanyog.r.kale@intel.com, rander.wang@linux.intel.com,
bard.liao@intel.com
Subject: Re: [PATCH 1/2] soundwire: add macro to selectively change error levels
Date: Thu, 1 Apr 2021 09:30:27 -0500 [thread overview]
Message-ID: <0834b9fc-9b3a-1184-fed2-6f9c7e66c6fb@linux.intel.com> (raw)
In-Reply-To: <YGV1HYL+XcVmxfQG@vkoul-mobl.Dlink>
On 4/1/21 2:24 AM, Vinod Koul wrote:
> On 31-03-21, 09:13, Bard Liao wrote:
>> From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
>>
>> We sometimes discard -ENODATA when reporting errors and lose all
>> traces of issues in the console log, add a macro to add use dev_dbg()
>> in such cases.
>>
>> Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
>> Reviewed-by: Rander Wang <rander.wang@intel.com>
>> Reviewed-by: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
>> Signed-off-by: Bard Liao <yung-chuan.liao@linux.intel.com>
>> ---
>> drivers/soundwire/bus.h | 8 ++++++++
>> 1 file changed, 8 insertions(+)
>>
>> diff --git a/drivers/soundwire/bus.h b/drivers/soundwire/bus.h
>> index 40354469860a..8370216f95d4 100644
>> --- a/drivers/soundwire/bus.h
>> +++ b/drivers/soundwire/bus.h
>> @@ -227,4 +227,12 @@ int sdw_bwrite_no_pm_unlocked(struct sdw_bus *bus, u16 dev_num, u32 addr, u8 val
>> void sdw_clear_slave_status(struct sdw_bus *bus, u32 request);
>> int sdw_slave_modalias(const struct sdw_slave *slave, char *buf, size_t size);
>>
>> +#define sdw_dev_dbg_or_err(dev, is_err, fmt, ...) \
>> + do { \
>> + if (is_err) \
>> + dev_err(dev, fmt, __VA_ARGS__); \
>> + else \
>> + dev_dbg(dev, fmt, __VA_ARGS__); \
>> + } while (0)
>
> I see a variant in sof code and now here, why not add in a
> dev_dbg_or_err() and use everywhere?
Good point, I hesitated back and forth on specific v. generic macro.
The main reason why I added this macro for SoundWire is that quite a few
subsystems have their own debug functions (DRM, ACPI, etc), and I wasn't
sure if there was any appetite to add more options in
include/linux/dev_printk.h. SOF also uses a different format due to history.
If at the end of the day SoundWire and SOF are the only users the value
of a common macro is limited.
But it's true that the macro could be used by others.
I really have no opinion here and will follow the consensus.
next prev parent reply other threads:[~2021-04-01 18:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 1:13 [PATCH 0/2] soundwire: bus: handle errors in clock stop/start sequences Bard Liao
2021-03-31 1:13 ` [PATCH 1/2] soundwire: add macro to selectively change error levels Bard Liao
2021-04-01 7:24 ` Vinod Koul
2021-04-01 14:30 ` Pierre-Louis Bossart [this message]
2021-04-01 16:46 ` Greg KH
2021-04-01 18:07 ` Pierre-Louis Bossart
2021-04-01 18:25 ` Greg KH
2021-04-01 18:43 ` Pierre-Louis Bossart
2021-04-01 20:56 ` Greg KH
2021-04-01 22:05 ` Pierre-Louis Bossart
2021-03-31 1:13 ` [PATCH 2/2] soundwire: bus: handle errors in clock stop/start sequences Bard Liao
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=0834b9fc-9b3a-1184-fed2-6f9c7e66c6fb@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hui.wang@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rander.wang@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@linux.intel.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