From: Vinod Koul <vkoul@kernel.org>
To: Bard Liao <yung-chuan.liao@linux.intel.com>
Cc: pierre-louis.bossart@linux.intel.com,
alsa-devel@alsa-project.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, ranjani.sridharan@linux.intel.com,
hui.wang@canonical.com, srinivas.kandagatla@linaro.org,
jank@cadence.com, sanyog.r.kale@intel.com,
rander.wang@linux.intel.com, bard.liao@intel.com
Subject: Re: [PATCH 1/3] soundwire: bus: clear bus clash interrupt before the mask is enabled
Date: Mon, 1 Feb 2021 16:08:25 +0530 [thread overview]
Message-ID: <20210201103825.GV2771@vkoul-mobl> (raw)
In-Reply-To: <20210201102844.GU2771@vkoul-mobl>
On 01-02-21, 15:58, Vinod Koul wrote:
> On 26-01-21, 16:37, Bard Liao wrote:
> > struct sdw_master_prop {
> > u32 revision;
> > @@ -421,8 +422,11 @@ struct sdw_master_prop {
> > u32 err_threshold;
> > u32 mclk_freq;
> > bool hw_disabled;
> > + u32 quirks;
>
> Can we do u64 here please.. I dont know where we would end up.. but
> would hate if we start running out of space ..
Also, is the sdw_master_prop right place for a 'quirk' property. I think
we can use sdw_master_device or sdw_bus as this seems like a bus
quirk..?
--
~Vinod
next prev parent reply other threads:[~2021-02-01 10:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 8:37 [PATCH 0/3] soundwire: clear bus clash/parity interrupt before the mask is enabled Bard Liao
2021-01-26 8:37 ` [PATCH 1/3] soundwire: bus: clear bus clash " Bard Liao
2021-02-01 10:28 ` Vinod Koul
2021-02-01 10:38 ` Vinod Koul [this message]
2021-02-01 16:18 ` Pierre-Louis Bossart
2021-02-02 4:39 ` Vinod Koul
2021-02-02 16:52 ` Pierre-Louis Bossart
2021-02-03 11:03 ` Vinod Koul
2021-01-26 8:37 ` [PATCH 2/3] soundwire: intel: add SDW_MASTER_QUIRKS_CLEAR_INITIAL_CLASH quirk Bard Liao
2021-02-01 10:42 ` Vinod Koul
2021-02-01 16:20 ` Pierre-Louis Bossart
2021-02-02 4:41 ` Vinod Koul
2021-02-02 16:53 ` Pierre-Louis Bossart
2021-01-26 8:37 ` [PATCH 3/3] soundwire: bus: clear parity interrupt before the mask is enabled Bard Liao
2021-02-01 11:09 ` Vinod Koul
2021-02-01 16:29 ` Pierre-Louis Bossart
2021-02-02 4:44 ` Vinod Koul
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=20210201103825.GV2771@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hui.wang@canonical.com \
--cc=jank@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rander.wang@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--cc=srinivas.kandagatla@linaro.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