From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Jyri Sarha <jsarha-l0cyMroinI0@public.gmane.org>
Cc: linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kuninori.morimoto.gx-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org,
Xiubo.Lee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
peter.ujfalusi-l0cyMroinI0@public.gmane.org,
liam.r.girdwood-VuQAYsv1563Yd54FQh9/CA@public.gmane.org
Subject: Re: [PATCH RFC] ASoC: simple-card: Update clocks binding for simple-card DAI subnodes
Date: Sat, 19 Sep 2015 11:42:25 -0700 [thread overview]
Message-ID: <20150919184225.GR30445@sirena.org.uk> (raw)
In-Reply-To: <1441977482-29215-1-git-send-email-jsarha-l0cyMroinI0@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 496 bytes --]
On Fri, Sep 11, 2015 at 04:18:02PM +0300, Jyri Sarha wrote:
> The updated binding provides a way to set clock-ID and direction
> parameters for DAI drivers set_sysclk() call back.
> I proposed something similar about a year ago, but Mark rejected that
> at the time. This RFC is to start that discussion again. This time
> before I do any code changes.
What's the use case again? Can we address this by converting the
relevant drivers to the clock API (or improving their clock API
support)?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-09-19 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 13:18 [PATCH RFC] ASoC: simple-card: Update clocks binding for simple-card DAI subnodes Jyri Sarha
[not found] ` <1441977482-29215-1-git-send-email-jsarha-l0cyMroinI0@public.gmane.org>
2015-09-19 18:42 ` Mark Brown [this message]
[not found] ` <20150919184225.GR30445-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-09-28 18:49 ` Jyri Sarha
[not found] ` <56098BBF.2010700-l0cyMroinI0@public.gmane.org>
2015-10-06 11:06 ` Mark Brown
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=20150919184225.GR30445@sirena.org.uk \
--to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=Xiubo.Lee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jsarha-l0cyMroinI0@public.gmane.org \
--cc=kuninori.morimoto.gx-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org \
--cc=liam.r.girdwood-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=peter.ujfalusi-l0cyMroinI0@public.gmane.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;
as well as URLs for NNTP newsgroup(s).