From: Sudeep Holla <sudeep.holla@arm.com>
To: ARM SoC Team <arm@kernel.org>, SoC Team <soc@kernel.org>,
ALKML <linux-arm-kernel@lists.infradead.org>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Arnd Bergmann <arnd@arndb.de>, Kevin Hilman <khilman@kernel.org>,
Liviu Dudau <liviu.dudau@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Olof Johansson <olof@lixom.net>
Subject: [GIT PULL] arm64: dts: juno: fixes for v5.5
Date: Mon, 2 Dec 2019 11:43:38 +0000 [thread overview]
Message-ID: <20191202114338.GA20965@bogus> (raw)
Hi ARM SoC Team,
Please pull !
Regards,
Sudeep
-->8
The following changes since commit 577dd5de09906e37a407a4326d17e58f6051fa2d:
arm64: dts: juno: add GPU subsystem (2019-10-21 15:32:56 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git tags/juno-fixes-5.5
for you to fetch changes up to 54fb3fe0f211d4729a2551cf9497bd612189af9d:
Revert "arm64: dts: juno: add dma-ranges property" (2019-11-28 16:40:51 +0000)
----------------------------------------------------------------
ARMv8 Juno fixes for v5.5
Couple of fixes:
1. Fix for UART clock frequency on all Juno variants that exist since
the platform was added. This is mainly due to incorrect Juno SoC
TRM that was referred during initial development days
2. Drop "dma-ranges" property for now as they are triggering loads of
warning on boot
----------------------------------------------------------------
Andre Przywara (1):
arm64: dts: juno: Fix UART frequency
Sudeep Holla (1):
Revert "arm64: dts: juno: add dma-ranges property"
arch/arm64/boot/dts/arm/juno-base.dtsi | 1 -
arch/arm64/boot/dts/arm/juno-clocks.dtsi | 4 ++--
2 files changed, 2 insertions(+), 3 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2019-12-02 11:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20191202114338.GA20965@bogus \
--to=sudeep.holla@arm.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=liviu.dudau@arm.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=olof@lixom.net \
--cc=soc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.