From: Code Kipper <codekipper@gmail.com>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-sunxi <linux-sunxi@googlegroups.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
"Andrea Venturi (pers)" <be17068@iperbole.bo.it>
Subject: Re: [PATCH 1/2] ASoC: sunxi: Add bindings for sun6i to SPDIF
Date: Sat, 30 Jul 2016 17:34:11 +0200 [thread overview]
Message-ID: <CAEKpxBn6aC0o7nixq-gjCCwFkAy+sb-hE5DTp5ikm+4LaPfCzw@mail.gmail.com> (raw)
In-Reply-To: <20160730151724.GS6215@lukather>
On 30 July 2016 at 17:17, Maxime Ripard
<maxime.ripard@free-electrons.com> wrote:
> On Sat, Jul 30, 2016 at 04:27:15PM +0200, codekipper@gmail.com wrote:
>> From: Marcus Cooper <codekipper@gmail.com>
>>
>> The A31 SoC uses the same SPDIF block as found in earlier SoCs, but its
>> reset is controlled via a separate reset controller.
>>
>> Signed-off-by: Marcus Cooper <codekipper@gmail.com>
>> ---
>> Documentation/devicetree/bindings/sound/sunxi,sun4i-spdif.txt | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/sound/sunxi,sun4i-spdif.txt b/Documentation/devicetree/bindings/sound/sunxi,sun4i-spdif.txt
>> index 13503aa..4fe80f7 100644
>> --- a/Documentation/devicetree/bindings/sound/sunxi,sun4i-spdif.txt
>> +++ b/Documentation/devicetree/bindings/sound/sunxi,sun4i-spdif.txt
>> @@ -9,6 +9,7 @@ Required properties:
>>
>> - compatible : should be one of the following:
>> - "allwinner,sun4i-a10-spdif": for the Allwinner A10 SoC
>> + - "allwinner,sun6i-a31-spdif": for the Allwinner A31 SoC
>>
>> - reg : Offset and length of the register set for the device.
>>
>> @@ -25,6 +26,8 @@ Required properties:
>> "apb" clock for the spdif bus.
>> "spdif" clock for spdif controller.
>>
>> + - reset : reset specifier for the ahb reset (A31 and newer only)
>
> Isn't it resets ? (plural)
Dohh..yes it is. Do you want me to send an updated patch series, a
single patch change or could I beg for your commit massaging?
Thanks,
CK
>
> Thanks,
> Maxime
>
> --
> Maxime Ripard, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
next prev parent reply other threads:[~2016-07-30 15:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-30 14:27 [PATCH 0/2] ASoC: Extended SPDIF support to Allwinner A31 SoCs codekipper
2016-07-30 14:27 ` [PATCH 1/2] ASoC: sunxi: Add bindings for sun6i to SPDIF codekipper
2016-07-30 15:17 ` Maxime Ripard
2016-07-30 15:34 ` Code Kipper [this message]
2016-07-30 15:40 ` Maxime Ripard
2016-07-30 14:27 ` [PATCH 2/2] ASoC: sunxi: compatibility " codekipper
2016-07-30 14:40 ` [linux-sunxi] " Julian Calaby
2016-07-30 15:21 ` Maxime Ripard
2016-07-30 15:19 ` Maxime Ripard
[not found] ` <170941469890365@web9j.yandex.ru>
2016-07-30 15:20 ` maxime.ripard
2016-08-01 13:39 ` [linux-sunxi] " Chen-Yu Tsai
2016-08-22 16:04 ` Maxime Ripard
2016-08-12 12:29 ` Applied "ASoC: sunxi: compatibility for sun6i to SPDIF" to the asoc tree 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=CAEKpxBn6aC0o7nixq-gjCCwFkAy+sb-hE5DTp5ikm+4LaPfCzw@mail.gmail.com \
--to=codekipper@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=be17068@iperbole.bo.it \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=maxime.ripard@free-electrons.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).