linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Armstrong <narmstrong@baylibre.com>
To: Jerome Brunet <jbrunet@baylibre.com>,
	Kevin Hilman <khilman@baylibre.com>
Cc: linux-amlogic@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] arm64: dts: meson: g12a: add tdm resets
Date: Wed, 21 Aug 2019 16:23:36 +0200	[thread overview]
Message-ID: <69a85842-3933-3965-9f4b-9d6a8432f766@baylibre.com> (raw)
In-Reply-To: <20190820121551.18398-1-jbrunet@baylibre.com>

On 20/08/2019 14:15, Jerome Brunet wrote:
> This patchset adds the dedicated reset of the tdm formatters which
> have been added on the g12a SoC family. Using these help with the channel
> mapping when the formatter uses more than 1 i2s lane.
> 
> Kevin, please note that to build, this patchset depends on the new reset
> bindings of the audio clock controller. I've prepared a tag for you [0]
> 
> [0]: git://github.com/BayLibre/clk-meson.git - clk-meson-dt-v5.4-2
> 
> Jerome Brunet (2):
>   arm64: dts: meson: g12a: audio clock controller provides resets
>   arm64: dts: meson: g12a: add reset to tdm formatters
> 
>  arch/arm64/boot/dts/amlogic/meson-g12a.dtsi | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 

For the serie,

Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>

Neil

  parent reply	other threads:[~2019-08-21 14:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-20 12:15 [PATCH 0/2] arm64: dts: meson: g12a: add tdm resets Jerome Brunet
2019-08-20 12:15 ` [PATCH 1/2] arm64: dts: meson: g12a: audio clock controller provides resets Jerome Brunet
2019-08-20 12:15 ` [PATCH 2/2] arm64: dts: meson: g12a: add reset to tdm formatters Jerome Brunet
2019-08-21 14:23 ` Neil Armstrong [this message]
2019-08-27 23:42 ` [PATCH 0/2] arm64: dts: meson: g12a: add tdm resets Kevin Hilman
2019-08-28  8:03   ` Jerome Brunet
2019-08-28 15:05     ` Kevin Hilman
2019-08-28 15:12       ` Jerome Brunet

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=69a85842-3933-3965-9f4b-9d6a8432f766@baylibre.com \
    --to=narmstrong@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.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).