From: Alexander Stein <alexanders83@web.de>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v2] ALSA: sound/atmel/ac97c.c: Add device tree support
Date: Wed, 10 Dec 2014 21:09:19 +0100 [thread overview]
Message-ID: <2706097.m58HT92L1r@kongar> (raw)
In-Reply-To: <5488A766.5070206@metafoo.de>
On Wednesday 10 December 2014, 21:04:54 wrote Lars-Peter Clausen:
> On 12/10/2014 08:59 PM, Alexander Stein wrote:
> > This adds device tree support for the AC97 controller. It uses the
> > soc-ac97link bindings, but actually only ac97-reset is used.
> >
> > Signed-off-by: Alexander Stein <alexanders83@web.de>
> > ---
> > Changes in v2:
> > * It now uses the soc-ac97link bindings (partly) instead of defining its own.
> > This should ease the transition to ASoC once a new driver has been written.
>
> Partly? How do they differ? And why do they differ? The devicetree should
> describe the hardware, which I guess is the same in both cases.
The devicetree is defined the same way, but not all set properties are used.
The soc-ac97link binding defines 3 GPIOs where 2 are used in conjunction with different pinctl modes for different reset modes.
The rather old atmel_ac97c driver only supports reset per Reset-GPIO which is the 3rd one given in devicetree. Because this driver only
uses the 3rd GPIO I've written 'partly'.
Best regards,
Alexander
next prev parent reply other threads:[~2014-12-10 20:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 19:59 [PATCH v2] ALSA: sound/atmel/ac97c.c: Add device tree support Alexander Stein
2014-12-10 20:04 ` Lars-Peter Clausen
2014-12-10 20:09 ` Alexander Stein [this message]
2014-12-19 20:42 ` Alexandre Belloni
2014-12-19 20:47 ` Alexandre Belloni
2014-12-19 20:51 ` Alexander Stein
2014-12-19 21:10 ` Alexandre Belloni
2014-12-19 21:05 ` Alexander Stein
2014-12-19 21:12 ` Alexandre Belloni
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=2706097.m58HT92L1r@kongar \
--to=alexanders83@web.de \
--cc=alexandre.belloni@free-electrons.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=lars@metafoo.de \
--cc=tiwai@suse.de \
/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