From: alexanders83@web.de (Alexander Stein)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] ARM: at91/dt: sam9263: Add ac97 device node
Date: Thu, 08 Jan 2015 20:12:04 +0100 [thread overview]
Message-ID: <2066438.if5qXaBWRu@kongar> (raw)
In-Reply-To: <1419854922-29338-3-git-send-email-alexanders83@web.de>
Now that the implementation has been applied to sound/for-next (https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/log/?h=for-next
), who is going to pick the related patches (this one and the other two adding documentation and default config)?
Best regards,
Alexander
On Monday 29 December 2014, 13:08:41 wrote Alexander Stein:
> This adds the device node for the ac97 controller.
>
> Signed-off-by: Alexander Stein <alexanders83@web.de>
> Acked-By Alexandre Belloni <alexandre.belloni@free-electrons.com>
> ---
> Changes in v3:
> * Renamed the compatible string to atmel,at91sam9263-ac97c
> * Added 'Acked-By Alexandre Belloni <alexandre.belloni@free-electrons.com>'
>
> arch/arm/boot/dts/at91sam9263.dtsi | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/arch/arm/boot/dts/at91sam9263.dtsi b/arch/arm/boot/dts/at91sam9263.dtsi
> index 6283785..2e67e38 100644
> --- a/arch/arm/boot/dts/at91sam9263.dtsi
> +++ b/arch/arm/boot/dts/at91sam9263.dtsi
> @@ -700,6 +700,16 @@
> };
> };
>
> + ac97 {
> + pinctrl_ac97: ac97-0 {
> + atmel,pins =
> + <AT91_PIOB 0 AT91_PERIPH_A AT91_PINCTRL_NONE /* PB12 periph A AC97FS pin */
> + AT91_PIOB 1 AT91_PERIPH_A AT91_PINCTRL_NONE /* PB13 periph A AC97CK pin */
> + AT91_PIOB 2 AT91_PERIPH_A AT91_PINCTRL_NONE /* PB14 periph A AC97TX pin */
> + AT91_PIOB 3 AT91_PERIPH_A AT91_PINCTRL_NONE>; /* PB14 periph A AC97RX pin */
> + };
> + };
> +
> pioA: gpio at fffff200 {
> compatible = "atmel,at91rm9200-gpio";
> reg = <0xfffff200 0x200>;
> @@ -828,6 +838,17 @@
> status = "disabled";
> };
>
> + ac97: sound at fffa0000 {
> + compatible = "atmel,at91sam9263-ac97c";
> + reg = <0xfffa0000 0x4000>;
> + interrupts = <18 IRQ_TYPE_LEVEL_HIGH 5>;
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_ac97>;
> + clocks = <&ac97_clk>;
> + clock-names = "ac97_clk";
> + status = "disabled";
> + };
> +
> macb0: ethernet at fffbc000 {
> compatible = "cdns,at32ap7000-macb", "cdns,macb";
> reg = <0xfffbc000 0x100>;
>
next prev parent reply other threads:[~2015-01-08 19:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1419854922-29338-1-git-send-email-alexanders83@web.de>
2014-12-29 12:08 ` [PATCH v3] ARM: at91/dt: sam9263: Add ac97 device node Alexander Stein
2015-01-08 19:12 ` Alexander Stein [this message]
2015-01-08 19:16 ` Alexandre Belloni
2015-01-26 16:00 ` Nicolas Ferre
2014-12-29 12:08 ` [PATCH v3] ARM: at91/defconfig: add SND_ATMEL_AC97C to at91_dt Alexander Stein
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=2066438.if5qXaBWRu@kongar \
--to=alexanders83@web.de \
--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