From: anarsoul@gmail.com (Vasily Khoruzhick)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: sun4i-i2s: don't try to start up or shut down DAI if it's active
Date: Mon, 15 Oct 2018 08:13:13 -0700 [thread overview]
Message-ID: <43997767.6bJE5D0JMY@anarsoul-thinkpad> (raw)
In-Reply-To: <20181015081151.rrn5xmso2hgckvh6@flea>
On Monday, October 15, 2018 1:11:51 AM PDT Maxime Ripard wrote:
> On Fri, Oct 12, 2018 at 09:28:56AM -0700, Vasily Khoruzhick wrote:
> > On Friday, October 12, 2018 9:09:05 AM PDT Mark Brown wrote:
> > > On Fri, Oct 12, 2018 at 08:32:54AM -0700, Vasily Khoruzhick wrote:
> > > > Otherwise we may end up with shutting down I2S if shutdown() was
> > > > called for capture substream, but playback is still running.
> > >
> > > Would it be cleaner and more robust to use runtime PM? I'm wondering
> > > what happens if some of the configuration stuff turns out to also need
> > > some of the clocks for example.
> >
> > I guess. I'm not sure why this code was put into startup and shutdown
> > callbacks in first place.
> >
> > Maybe Marcus or Maxime know?
>
> I can't really come up with a good explanation, so I guess there's
> none :)
>
> > As for configuration - only bus clock is necessary for configuration
> > and it's already enabled in runtime_resume() callback.
>
> Not really. Or at least, on the A64, yes, but shutting down the bus
> clock on older SoCs will reset the controller. I'd just put the enable
> bit on the runtime_pm hook.
OK, will do.
> Maxime
prev parent reply other threads:[~2018-10-15 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 15:32 [PATCH] ASoC: sun4i-i2s: don't try to start up or shut down DAI if it's active Vasily Khoruzhick
2018-10-12 16:09 ` Mark Brown
2018-10-12 16:28 ` Vasily Khoruzhick
2018-10-12 16:45 ` Mark Brown
2018-10-15 8:11 ` Maxime Ripard
2018-10-15 15:13 ` Vasily Khoruzhick [this message]
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=43997767.6bJE5D0JMY@anarsoul-thinkpad \
--to=anarsoul@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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