linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: alexandre.belloni@free-electrons.com (Alexandre Belloni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] ALSA: sound/atmel/ac97c.c: Add device tree support
Date: Tue, 15 Apr 2014 01:21:34 +0200	[thread overview]
Message-ID: <20140414232134.GB2967@piout.net> (raw)
In-Reply-To: <11572820.ByGz2BLudS@kongar>

On 13/04/2014 at 10:32:09 +0200, Alexander Stein wrote :
> On Saturday 12 April 2014, 14:48:17 wrote Alexander Shiyan:
> > Sat, 12 Apr 2014 12:42:18 +0200 ?? Alexander Stein <alexanders83@web.de>:
> > > On Saturday 12 April 2014, 14:31:28 wrote Alexander Shiyan:
> > > > Sat, 12 Apr 2014 11:08:26 +0200 ?? Alexander Stein <alexanders83@web.de>:
> > > > > Signed-off-by: Alexander Stein <alexanders83@web.de>
> > > > > ---
> > > > >  .../devicetree/bindings/sound/atmel_ac97c.txt      | 20 +++++++++
> > > > >  sound/atmel/ac97c.c                                | 52 ++++++++++++++++++++--
> > > > >  2 files changed, 69 insertions(+), 3 deletions(-)
> > > > >  create mode 100644 Documentation/devicetree/bindings/sound/atmel_ac97c.txt
> > > > > 
> > > > > diff --git a/Documentation/devicetree/bindings/sound/atmel_ac97c.txt b/Documentation/devicetree/bindings/sound/atmel_ac97c.txt
> > > > > new file mode 100644
> > > > > index 0000000..9839403
> > > > > --- /dev/null
> > > > > +++ b/Documentation/devicetree/bindings/sound/atmel_ac97c.txt
> > > > > @@ -0,0 +1,20 @@
> > > > > +* Atmel AC97 controller
> > > > > +
> > > > > +Required properties:
> > > > > +  - compatible: "atmel,atmel_ac97c"
> > > > > +  - reg: Address and length of the register set for the device
> > > > > +  - interrupts: Should contain AC97 interrupt
> > > > > +  - atmel,reset-pin: GPIO for resetting the codec
> > > > 
> > > > Why standard "gpios" property cannot be used here?
> > > 
> > > I guess they can. I have no experience defining a devicetree binding, so I just stuck to the platformdata member name.
> > > If this is the recommended way, I'll gladly change that.
> > 
> > Another question is whether this property should refer to the controller,
> > as it is clear that it refers to the codec ....
> 
> AFAICT the codec itself has no representation in the devicetree. It gets detected by the controller which uses the reset GPIO.
>

Yeah, maybe we can already go for ac97-gpios, there. It actually takes a
list of gpios: ac97-sync, ac97-sdata and ac97-reset. You may want to
have a look at Documentation/devicetree/bindings/sound/soc-ac97link.txt
and snd_soc_set_ac97_ops_of_reset(), snd_soc_ac97_parse_pinctl() in
sound/soc/core.c

The goal would be to be able to keep the same bindings when switching
over to ASoC.

-- 
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-04-14 23:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-12  9:08 Device tree support for Atmel AC97 controller on AT91SAM9263 Alexander Stein
2014-04-12  9:08 ` [PATCH 1/4] ALSA: sound/atmel/ac97c.c: Convert to module_platform_driver Alexander Stein
2014-04-14 22:48   ` Alexandre Belloni
2014-04-12  9:08 ` [PATCH 2/4] ALSA: sound/atmel-ac97c.h: Remove unused flags from platform data Alexander Stein
2014-04-14 22:51   ` Alexandre Belloni
2014-04-12  9:08 ` [PATCH 3/4] ALSA: sound/atmel/ac97c.c: Add device tree support Alexander Stein
2014-04-12 10:31   ` Alexander Shiyan
2014-04-12 10:42     ` Alexander Stein
2014-04-12 10:48       ` Alexander Shiyan
2014-04-13  8:32         ` Alexander Stein
2014-04-14 23:21           ` Alexandre Belloni [this message]
2014-04-15 19:17             ` Alexander Stein
2014-04-14 23:07   ` Alexandre Belloni
2014-04-12  9:08 ` [PATCH 4/4] ARM: at91/dt: sam9263: Add ac97 device node Alexander Stein
2014-04-14  8:39 ` Device tree support for Atmel AC97 controller on AT91SAM9263 Bo Shen
2014-04-14 18:34   ` Alexander Stein
2014-04-14  8:42 ` Takashi Iwai
2014-04-14 18:43   ` Alexander Stein
2014-04-14 22:47     ` Alexandre Belloni
2014-04-15  5:59       ` 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=20140414232134.GB2967@piout.net \
    --to=alexandre.belloni@free-electrons.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;
as well as URLs for NNTP newsgroup(s).