From: Kevin Hilman <khilman@baylibre.com>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
linux-amlogic@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] arm64: dts: meson: audio updates
Date: Tue, 24 Sep 2019 11:34:51 -0700 [thread overview]
Message-ID: <7hk19x7dbo.fsf@baylibre.com> (raw)
In-Reply-To: <20190905125956.4384-1-jbrunet@baylibre.com>
Jerome Brunet <jbrunet@baylibre.com> writes:
> The patchset features a few updates to prepare the addition of the audio
> on sm1. It fixes the register range of audio fifo which was incorrect.
>
> It also create another layer of dtsi, common to g12a and g12b but not sm1.
> The audio related device are moved to this file.
>
> This was done because the audio bus, which was at 0xff642000 on g12, has
> moved 0xff660000 on sm1. Overwriting the reg property was option but it
> would have left confusing node names on the sm1.
>
> Jerome Brunet (5):
> arm64: dts: meson: axg: fix audio fifo reg size
> arm64: dts: meson: g12: fix audio fifo reg size
> arm64: dts: meson: g12: add a g12 layer
> arm64: dts: meson: g12: factor the power domain.
> arm64: dts: meson: g12: move audio bus out of g12-common
Queued for v5.5,
Kevin
prev parent reply other threads:[~2019-09-24 18:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 12:59 [PATCH 0/5] arm64: dts: meson: audio updates Jerome Brunet
2019-09-05 12:59 ` [PATCH 1/5] arm64: dts: meson: axg: fix audio fifo reg size Jerome Brunet
2019-09-05 12:59 ` [PATCH 2/5] arm64: dts: meson: g12: " Jerome Brunet
2019-09-05 12:59 ` [PATCH 3/5] arm64: dts: meson: g12: add a g12 layer Jerome Brunet
2019-09-05 12:59 ` [PATCH 4/5] arm64: dts: meson: g12: factor the power domain Jerome Brunet
2019-09-05 12:59 ` [PATCH 5/5] arm64: dts: meson: g12: move audio bus out of g12-common Jerome Brunet
2019-09-24 18:34 ` Kevin Hilman [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=7hk19x7dbo.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@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).