From: Stephen Boyd <sboyd@kernel.org>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: Kevin Hilman <khilman@baylibre.com>,
linux-clk@vger.kernel.org, linux-amlogic@lists.infradead.org
Subject: Re: [GIT PULL] clk: meson: updates for v5.8
Date: Thu, 14 May 2020 13:55:58 -0700 [thread overview]
Message-ID: <158948975864.215346.6720030658125416749@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <1j3686g6r6.fsf@starbuckisacylon.baylibre.com>
Quoting Jerome Brunet (2020-05-11 02:28:45)
> Hi Stephen,
>
> Here are the amlogic clock updates for v5.8.
> Nothing fancy, please pull.
>
> Cheers
>
> The following changes since commit 8f3d9f354286745c751374f5f1fcafee6b3f3136:
>
> Linux 5.7-rc1 (2020-04-12 12:35:55 -0700)
>
> are available in the Git repository at:
>
> git://github.com/BayLibre/clk-meson.git tags/clk-meson-v5.8-1
>
> for you to fetch changes up to a29ae8600d50ece1856b062a39ed296b8b952259:
>
> clk: meson: meson8b: Don't rely on u-boot to init all GP_PLL registers (2020-05-02 01:53:32 +0200)
>
> ----------------------------------------------------------------
> Amlogic clock updates for v5.8:
>
> * Meson8b: Updates and fixup HDMI and video clocks
> * Meson8b: Fixup reset polarity
> * Meson gx and g12: fix GPU glitch free mux switch
>
> ----------------------------------------------------------------
Should also mention that sparse on arm64 complains about
drivers/clk/meson/g12a.c:5074:43: warning: invalid access past the end of 'g12b_hw_onecell_data' (1472 8)
but I have no idea if that's a real problem. Maybe my sparse build is
bad?
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2020-05-14 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 9:28 [GIT PULL] clk: meson: updates for v5.8 Jerome Brunet
2020-05-14 20:38 ` Stephen Boyd
2020-05-14 20:55 ` Stephen Boyd [this message]
2020-05-14 21:42 ` 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=158948975864.215346.6720030658125416749@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-clk@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).