From: Krzysztof Kozlowski <krzk@kernel.org>
To: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
arm@kernel.org, soc@kernel.org
Cc: linux-samsung-soc@vger.kernel.org, Kukjin Kim <kgene@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Krzysztof Kozlowski <krzk@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL 3/5] ARM: dts: exynos: Second pull for v5.4
Date: Wed, 4 Sep 2019 19:50:00 +0200 [thread overview]
Message-ID: <20190904175002.10487-4-krzk@kernel.org> (raw)
In-Reply-To: <20190904175002.10487-1-krzk@kernel.org>
Hi,
On top of previous pull request.
Best regards,
Krzysztof
The following changes since commit bfb77169306d5d560a8b62eebaf6d69d02e8d152:
ARM: dts: exynos: Add CAM power domain to Exynos5422/5800 (2019-08-12 19:02:59 +0200)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git tags/samsung-dt-5.4-2
for you to fetch changes up to 51c88919e52873c83f8be0c8f5d0ffd654f1ef4a:
ARM: dts: exynos: Enable GPU/Mali T604 on Arndale board (2019-09-04 19:25:33 +0200)
----------------------------------------------------------------
Samsung DTS ARM changes for v5.4, part 2
1. Fix Exynos542x Chromebooks boot with multi_v7 defconfig,
2. Add GPU (Mali) support to Exynos5250 boards,
3. Minor cleanup for Exynos3250 ADC.
----------------------------------------------------------------
Guillaume Gardet (4):
ARM: dts: exynos: Fix min/max buck4 for GPU on Arndale board
ARM: dts: exynos: Add GPU/Mali T604 node to Exynos5250
ARM: dts: exynos: Enable GPU/Mali T604 on Chromebook Snow
ARM: dts: exynos: Enable GPU/Mali T604 on Arndale board
Krzysztof Kozlowski (1):
ARM: dts: exynos: Remove not accurate secondary ADC compatible
Marek Szyprowski (1):
ARM: dts: exynos: Mark LDO10 as always-on on Peach Pit/Pi Chromebooks
arch/arm/boot/dts/exynos3250.dtsi | 3 +-
arch/arm/boot/dts/exynos5250-arndale.dts | 9 +++--
arch/arm/boot/dts/exynos5250-snow-common.dtsi | 5 +++
arch/arm/boot/dts/exynos5250.dtsi | 47 +++++++++++++++++++++++++++
arch/arm/boot/dts/exynos5420-peach-pit.dts | 1 +
arch/arm/boot/dts/exynos5800-peach-pi.dts | 1 +
6 files changed, 62 insertions(+), 4 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-09-04 17:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 17:49 [GIT PULL 0/5] arm: exynos: Second round of pulls for v5.4 Krzysztof Kozlowski
2019-09-04 17:49 ` [GIT PULL 1/5] ARM: defconfig: exynos " Krzysztof Kozlowski
2019-09-04 20:38 ` Arnd Bergmann
2019-09-04 17:49 ` [GIT PULL 2/5] soc: samsung: Second pull " Krzysztof Kozlowski
2019-09-04 20:38 ` Arnd Bergmann
2019-09-04 17:50 ` Krzysztof Kozlowski [this message]
2019-09-04 20:38 ` [GIT PULL 3/5] ARM: dts: exynos: " Arnd Bergmann
2019-09-04 17:50 ` [GIT PULL 4/5] ARM: samsung: mach for v5.4, second (replacing previous) Krzysztof Kozlowski
2019-09-04 20:39 ` Arnd Bergmann
2019-09-04 17:50 ` [PATCH 5/5] arm64: exynos: Enable exynos-chipid driver Krzysztof Kozlowski
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=20190904175002.10487-4-krzk@kernel.org \
--to=krzk@kernel.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--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 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).