From: Vinod Koul <vkoul@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
tiwai@suse.de, broonie@kernel.org, gregkh@linuxfoundation.org,
jank@cadence.com, srinivas.kandagatla@linaro.org,
slawomir.blauciak@intel.com,
Bard liao <yung-chuan.liao@linux.intel.com>,
Rander Wang <rander.wang@linux.intel.com>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
Hui Wang <hui.wang@canonical.com>,
Rander Wang <rander.wang@intel.com>,
Sanyog Kale <sanyog.r.kale@intel.com>
Subject: Re: [PATCH 5/7] soundwire: intel: follow documentation sequences for SHIM registers
Date: Mon, 23 Mar 2020 18:01:40 +0530 [thread overview]
Message-ID: <20200323123140.GM72691@vkoul-mobl> (raw)
In-Reply-To: <9e280e1b-178a-0ce8-be5b-03532c5507fe@linux.intel.com>
On 20-03-20, 09:20, Pierre-Louis Bossart wrote:
> > > @@ -283,11 +284,48 @@ static int intel_link_power_up(struct sdw_intel *sdw)
> > > {
> > > unsigned int link_id = sdw->instance;
> > > void __iomem *shim = sdw->link_res->shim;
> > > + u32 *shim_mask = sdw->link_res->shim_mask;
> >
> > this is a local pointer, so the one defined previously is not used.
>
> No idea what you are saying, it's the same address so changes to *shim_mask
> will be the same as in *sdw->link_res->shim_mask.
There seems to be too many shim_masks, in global structs, then pointer
and then local ones. It is really confusing...
> > > + struct sdw_bus *bus = &sdw->cdns.bus;
> > > + struct sdw_master_prop *prop = &bus->prop;
> > > int spa_mask, cpa_mask;
> > > - int link_control, ret;
> > > + int link_control;
> > > + int ret = 0;
> > > + u32 syncprd;
> > > + u32 sync_reg;
> > > mutex_lock(sdw->link_res->shim_lock);
> > > + /*
> > > + * The hardware relies on an internal counter,
> > > + * typically 4kHz, to generate the SoundWire SSP -
> > > + * which defines a 'safe' synchronization point
> > > + * between commands and audio transport and allows for
> > > + * multi link synchronization. The SYNCPRD value is
> > > + * only dependent on the oscillator clock provided to
> > > + * the IP, so adjust based on _DSD properties reported
> > > + * in DSDT tables. The values reported are based on
> > > + * either 24MHz (CNL/CML) or 38.4 MHz (ICL/TGL+).
> >
> > Sorry this looks quite bad to read, we have 80 chars, so please use
> > like below:
> >
> > /*
> > * The hardware relies on an internal counter, typically 4kHz,
> > * to generate the SoundWire SSP - which defines a 'safe'
> > * synchronization point between commands and audio transport
> > * and allows for multi link synchronization. The SYNCPRD value
> > * is only dependent on the oscillator clock provided to
> > * the IP, so adjust based on _DSD properties reported in DSDT
> > * tables. The values reported are based on either 24MHz
> > * (CNL/CML) or 38.4 MHz (ICL/TGL+).
> > */
>
> Are we really going to have an emacs vs vi discussion here?
What has that got to do with editor to use, nothing imo.
All I am asking is to use 80 chars here and make it look decent to
read. And not truncate at 60 ish chars which seems above
--
~Vinod
next prev parent reply other threads:[~2020-03-23 12:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 22:10 [PATCH 0/7] SoundWire: intel: fix SHIM programming sequences Pierre-Louis Bossart
2020-03-11 22:10 ` [PATCH 1/7] soundwire: intel: add helpers for link power down and shim wake Pierre-Louis Bossart
2020-03-11 22:10 ` [PATCH 2/7] soundwire: intel: reuse code for wait loops to set/clear bits Pierre-Louis Bossart
2020-03-20 13:38 ` Vinod Koul
2020-03-11 22:10 ` [PATCH 3/7] soundwire: intel: add mutex to prevent concurrent access to SHIM registers Pierre-Louis Bossart
2020-03-20 13:41 ` Vinod Koul
2020-03-20 14:07 ` Pierre-Louis Bossart
2020-03-23 12:18 ` Vinod Koul
2020-03-11 22:10 ` [PATCH 4/7] soundwire: intel: add definitions for shim_mask Pierre-Louis Bossart
2020-03-20 13:42 ` Vinod Koul
2020-03-20 14:13 ` Pierre-Louis Bossart
2020-03-23 12:28 ` Vinod Koul
2020-03-11 22:10 ` [PATCH 5/7] soundwire: intel: follow documentation sequences for SHIM registers Pierre-Louis Bossart
2020-03-20 13:51 ` Vinod Koul
2020-03-20 14:20 ` Pierre-Louis Bossart
2020-03-23 12:31 ` Vinod Koul [this message]
2020-03-11 22:10 ` [PATCH 6/7] soundwire: intel: introduce a helper to arm link synchronization Pierre-Louis Bossart
2020-03-11 22:10 ` [PATCH 7/7] soundwire: intel: introduce helper for " Pierre-Louis Bossart
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=20200323123140.GM72691@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--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@intel.com \
--cc=rander.wang@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--cc=slawomir.blauciak@intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.de \
--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