From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Codrin Ciubotariu <codrin.ciubotariu@microchip.com>
Cc: nicolas.ferre@microchip.com, Claudiu.Beznea@microchip.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Cristian.Birsan@microchip.com
Subject: Re: [PATCH v7 0/3] ARM: dts: at91: sama5d2: Add nodes for I2S
Date: Mon, 27 Aug 2018 16:40:49 +0200 [thread overview]
Message-ID: <20180827144049.GC23428@piout.net> (raw)
In-Reply-To: <20180806111948.4522-1-codrin.ciubotariu@microchip.com>
On 06/08/2018 14:19:45+0300, Codrin Ciubotariu wrote:
> These are the remaining dts patches from the series:
> [PATCH v5 0/5] ASoC: add driver for Atmel I2S controller
>
> v6 -> v7
> - addressed some comments regarding pin conflicts;
>
> v5 -> v6
> - removed unnecessary phandles to audio PLL clock from the I2S nodes;
> - using assigned clocks to set gclk as parent of i2smuxclk;
>
> Codrin Ciubotariu (1):
> ARM: dts: at91: sama5d2: add I2S clock muxing nodes
>
> Cyrille Pitchen (2):
> ARM: dts: at91: sama5d2: add nodes for I2S controllers
> ARM: dts: at91: sama5d2 Xplained: add pin muxing for I2S
>
> arch/arm/boot/dts/at91-sama5d2_xplained.dts | 30 +++++++++++
> arch/arm/boot/dts/sama5d2.dtsi | 56 +++++++++++++++++++++
> 2 files changed, 86 insertions(+)
>
All applied, thanks!
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-08-27 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 11:19 [PATCH v7 0/3] ARM: dts: at91: sama5d2: Add nodes for I2S Codrin Ciubotariu
2018-08-06 11:19 ` [PATCH v7 1/3] ARM: dts: at91: sama5d2: add I2S clock muxing nodes Codrin Ciubotariu
2018-08-06 11:19 ` [PATCH v7 2/3] ARM: dts: at91: sama5d2: add nodes for I2S controllers Codrin Ciubotariu
2018-08-06 11:19 ` [PATCH v7 3/3] ARM: dts: at91: sama5d2 Xplained: add pin muxing for I2S Codrin Ciubotariu
2018-08-27 14:40 ` Alexandre Belloni [this message]
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=20180827144049.GC23428@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=Cristian.Birsan@microchip.com \
--cc=codrin.ciubotariu@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
/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).