Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: ckeepax@opensource.cirrus.com (Charles Keepax)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 2/2] ASoC: select sysclk clock from mlck clock provider in wm8994 driver
Date: Fri, 15 Dec 2017 11:46:06 +0000	[thread overview]
Message-ID: <20171215114606.6wxw2m5rykmb7ak2@localhost.localdomain> (raw)
In-Reply-To: <20171214173624.GM9788@sirena.org.uk>

On Thu, Dec 14, 2017 at 05:36:24PM +0000, Mark Brown wrote:
> On Thu, Dec 14, 2017 at 05:53:58PM +0100, Olivier Moysan wrote:
> > When defined in device tree, MCLK1 and MCLK2 are used
> > as sysclk for aif1 and aif2 interfaces respectively.
> 
> That's not a valid assumption as far as I remember?  The AIFs can use
> either MCLK depending on the system configuration I think.
> 

Indeed yes the code added here is literally just above the code
that selects that, it should be fairly simple to update the patch
to take this into account.

Thanks,
Charles

  parent reply	other threads:[~2017-12-15 11:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14 16:53 [RFC PATCH 0/2] select master clock in wm8994 driver based on DT clocks configuration Olivier Moysan
2017-12-14 16:53 ` [RFC PATCH 1/2] ASoC: add support of mclk clock providers in wm8894 driver Olivier Moysan
     [not found]   ` <20171214173025.GL9788@sirena.org.uk>
2017-12-15 11:51     ` Charles Keepax
2017-12-14 16:53 ` [RFC PATCH 2/2] ASoC: select sysclk clock from mlck clock provider in wm8994 driver Olivier Moysan
     [not found]   ` <20171214173624.GM9788@sirena.org.uk>
2017-12-15 11:46     ` Charles Keepax [this message]
2017-12-15 15:15     ` Olivier MOYSAN
2017-12-19  9:35       ` Mark Brown
2017-12-20 12:42         ` Olivier MOYSAN
     [not found]           ` <20171220155000.GD17890@sirena.org.uk>
2017-12-21 10:51             ` Olivier MOYSAN

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=20171215114606.6wxw2m5rykmb7ak2@localhost.localdomain \
    --to=ckeepax@opensource.cirrus.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