From: khilman@baylibre•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/4] ARM64: dts: meson: hhi syscon and clock controllers
Date: Thu, 19 Apr 2018 10:41:20 -0700 [thread overview]
Message-ID: <7h1sfb5c1r.fsf@baylibre.com> (raw)
In-Reply-To: <20180315115545.1884-1-jbrunet@baylibre.com> (Jerome Brunet's message of "Thu, 15 Mar 2018 12:55:41 +0100")
Jerome Brunet <jbrunet@baylibre•com> writes:
> The HHI register region provides more than just clocks. Several drivers may
> need to access this region, such as the clock controllers and the display
> driver.
>
> Meson-gx clock controllers has been developed and merged before we knew the
> hhi could be needed elsewhere, which is why it requests the region directly.
> Meson-axg was built following the model of meson-gx.
>
> To fix this situation, the clock controller should be a child of the hhi
> system controllers. The hhi system controller node already exists on meson-gx.
> It needs to be added on the axg.
>
> This changeset depends on [0]. This dependency has been merged in
> clk-next. A topic branch is available here [1]
As the dependencies are now merged for v4.17, applying this to
v4.18/dt64,
Thanks,
Kevin
prev parent reply other threads:[~2018-04-19 17:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 11:55 [PATCH 0/4] ARM64: dts: meson: hhi syscon and clock controllers Jerome Brunet
2018-03-15 11:55 ` [PATCH 1/4] dt-bindings: clock: meson: update documentation with hhi syscon Jerome Brunet
2018-03-18 12:52 ` Rob Herring
2018-03-18 15:09 ` Jerome Brunet
2018-03-23 3:04 ` Rob Herring
2018-03-26 7:49 ` Neil Armstrong
2018-03-15 11:55 ` [PATCH 2/4] ARM64: dts: meson-gx: sysctrl is the parent of the clock controller Jerome Brunet
2018-03-15 11:55 ` [PATCH 3/4] ARM64: dts: meson-axg: use hhi syscon for " Jerome Brunet
2018-03-15 11:55 ` [PATCH 4/4] ARM64: dts: meson-gx: fix gxl clock controller compatible Jerome Brunet
2018-04-19 17:41 ` 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=7h1sfb5c1r.fsf@baylibre.com \
--to=khilman@baylibre$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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