public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: broonie@kernel•org (Mark Brown)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v4 2/3] ASoC: cygnus: Add Cygnus audio DAI driver
Date: Wed, 2 Dec 2015 10:45:43 +0000	[thread overview]
Message-ID: <20151202104543.GD1929@sirena.org.uk> (raw)
In-Reply-To: <565E54D2.50806@broadcom.com>

On Tue, Dec 01, 2015 at 06:17:54PM -0800, Simran Rai wrote:
> On 11/22/2015 5:44 AM, Mark Brown wrote:

> >I would expect any initialisationn of clocks beyond the ones that the
> >device directly interacts with to be handled within the clock API
> >configuration rather than in a specific driver, this avoids the driver
> >being dependent on a particular system integration.

> I will have to figure out a way to propagate the frequency from leaf clocks to the parent
> clock. Will send out another patch with the fix.

The idea is that the clock API should take care of this.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20151202/70a271d5/attachment.sig>

  reply	other threads:[~2015-12-02 10:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-10  0:17 [PATCH v4 0/3]ASoC: cygnus: Add audio support for Broadcom Cygnus SoC Simran Rai
2015-11-10  0:17 ` [PATCH v4 1/3] ASoC: cygnus: Add DT bindings for Broadcom Cygnus audio Simran Rai
2015-11-10  0:17 ` [PATCH v4 2/3] ASoC: cygnus: Add Cygnus audio DAI driver Simran Rai
2015-11-22 13:44   ` Mark Brown
2015-12-02  2:17     ` Simran Rai
2015-12-02 10:45       ` Mark Brown [this message]
2015-11-10  0:17 ` [PATCH v4 3/3] ASoC: cygnus: Add Cygnus audio DMA driver Simran Rai

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=20151202104543.GD1929@sirena.org.uk \
    --to=broonie@kernel$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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