From: Takashi Iwai <tiwai@suse.de>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Vinod Koul <vinod.koul@intel.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org,
Douglas Anderson <dianders@chromium.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: Intel: sst: Remove unused function sst_restore_shim64()
Date: Thu, 08 Jun 2017 09:02:23 +0200 [thread overview]
Message-ID: <s5ho9tz2c8w.wl-tiwai@suse.de> (raw)
In-Reply-To: <20170607215329.GD141096@google.com>
On Wed, 07 Jun 2017 23:53:29 +0200,
Matthias Kaehlcke wrote:
>
> Hi Takashi,
>
> El Wed, Jun 07, 2017 at 11:40:19PM +0200 Takashi Iwai ha dit:
>
> > On Tue, 23 May 2017 02:12:58 +0200,
> > Matthias Kaehlcke wrote:
> > >
> > > Looks like the function has never been used since it was added by commit
> > > b0d94acd634a ("ASoC: Intel: mrfld - add shim save restore"). Removing it
> > > fixes the following warning when building with clang:
> > >
> > > sound/soc/intel/atom/sst/sst.c:360:20: error: unused function
> > > 'sst_restore_shim64' [-Werror,-Wunused-function]
> > >
> > > Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
> >
> > Hmm, although this patch was already merged, I now think this is
> > rather a bug. If the restore is never executed, why the counterpart,
> > sst_save_shim64() is required at all at runtime suspend?
>
> Doug Anderson also noticed this and removed the function and struct
> sst_shim_regs64:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?h=for-next&id=98cf2c03b467fa67df58cb52adeb85b425cabcb2
Yes, I know. But I wonder it were a failure to remove before
confirming that.
thanks,
Takashi
>
> > > ---
> > > sound/soc/intel/atom/sst/sst.c | 16 ----------------
> > > 1 file changed, 16 deletions(-)
> > >
> > > diff --git a/sound/soc/intel/atom/sst/sst.c b/sound/soc/intel/atom/sst/sst.c
> > > index f9ba71315e33..fb608d3a90c8 100644
> > > --- a/sound/soc/intel/atom/sst/sst.c
> > > +++ b/sound/soc/intel/atom/sst/sst.c
> > > @@ -397,22 +397,6 @@ static inline void sst_save_shim64(struct intel_sst_drv *ctx,
> > > spin_unlock_irqrestore(&ctx->ipc_spin_lock, irq_flags);
> > > }
> > >
> > > -static inline void sst_restore_shim64(struct intel_sst_drv *ctx,
> > > - void __iomem *shim,
> > > - struct sst_shim_regs64 *shim_regs)
> > > -{
> > > - unsigned long irq_flags;
> > > -
> > > - /*
> > > - * we only need to restore IMRX for this case, rest will be
> > > - * initialize by FW or driver when firmware is loaded
> > > - */
> > > - spin_lock_irqsave(&ctx->ipc_spin_lock, irq_flags);
> > > - sst_shim_write64(shim, SST_IMRX, shim_regs->imrx);
> > > - sst_shim_write64(shim, SST_CSR, shim_regs->csr);
> > > - spin_unlock_irqrestore(&ctx->ipc_spin_lock, irq_flags);
> > > -}
> > > -
> > > void sst_configure_runtime_pm(struct intel_sst_drv *ctx)
> > > {
> > > pm_runtime_set_autosuspend_delay(ctx->dev, SST_SUSPEND_DELAY);
>
next prev parent reply other threads:[~2017-06-08 7:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 0:12 [PATCH] ASoC: Intel: sst: Remove unused function sst_restore_shim64() Matthias Kaehlcke
2017-05-24 17:41 ` Applied "ASoC: Intel: sst: Remove unused function sst_restore_shim64()" to the asoc tree Mark Brown
2017-06-07 21:40 ` [PATCH] ASoC: Intel: sst: Remove unused function sst_restore_shim64() Takashi Iwai
2017-06-07 21:53 ` Matthias Kaehlcke
2017-06-08 7:02 ` Takashi Iwai [this message]
2017-06-09 3:40 ` Vinod Koul
2017-06-09 7:05 ` Takashi Iwai
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=s5ho9tz2c8w.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dianders@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=perex@perex.cz \
--cc=vinod.koul@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