From: Michal Simek <monstr@monstr.eu>
To: arm-soc <arm@kernel.org>
Cc: linux-arm <linux-arm-kernel@lists.infradead.org>
Subject: [GIT PULL] arm64: dts: Xilinx DT changes for v5.2
Date: Mon, 15 Apr 2019 10:44:46 +0200 [thread overview]
Message-ID: <f7c97dc7-0aa1-ea3b-b788-7fdf686181ed@monstr.eu> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 2426 bytes --]
Hi,
please pull these patches to your tree. It is just 3 patches where two
are related to firmware clock. One is file rename and second is binding
doc separation. And the last is adding standard TI quirk to phy node.
Thanks,
Michal
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
are available in the git repository at:
https://github.com/Xilinx/linux-xlnx.git tags/zynqmp-dt-for-v5.2
for you to fetch changes up to 78c484a55d915e36891be5bae92e516fdac8609d:
arm64: zynqmp: dt: Add TI PHY quirk (2019-03-18 15:59:08 +0100)
----------------------------------------------------------------
arm64: dts: zynqmp: DT changes for v5.2
- Align xlnx-zynqmp-clk.h file name and separate
binding for clock driver
- Add TI quirks to zynqmp boards
----------------------------------------------------------------
Harini Katakam (1):
arm64: zynqmp: dt: Add TI PHY quirk
Jolly Shah (1):
include: dt-binding: clock: Rename zynqmp header file
Rajan Vaja (1):
dt-bindings: xilinx: Separate clock binding from firmware doc
Documentation/devicetree/bindings/clock/xlnx,zynqmp-clk.txt
| 63 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-firmware.txt | 54 +-----------------------------------------------------
arch/arm64/boot/dts/xilinx/zynqmp-zc1751-xm016-dc2.dts
| 1 +
arch/arm64/boot/dts/xilinx/zynqmp-zcu102-revA.dts
| 1 +
arch/arm64/boot/dts/xilinx/zynqmp-zcu102-revB.dts
| 1 +
arch/arm64/boot/dts/xilinx/zynqmp-zcu104-revA.dts
| 1 +
arch/arm64/boot/dts/xilinx/zynqmp-zcu106-revA.dts
| 1 +
arch/arm64/boot/dts/xilinx/zynqmp-zcu111-revA.dts
| 1 +
include/dt-bindings/clock/{xlnx,zynqmp-clk.h => xlnx-zynqmp-clk.h}
| 26 ++++++++++++++++++--------
9 files changed, 88 insertions(+), 61 deletions(-)
create mode 100644
Documentation/devicetree/bindings/clock/xlnx,zynqmp-clk.txt
rename include/dt-bindings/clock/{xlnx,zynqmp-clk.h =>
xlnx-zynqmp-clk.h} (85%)
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal SoCs
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-04-15 8:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 8:44 Michal Simek [this message]
2019-04-28 19:31 ` [GIT PULL] arm64: dts: Xilinx DT changes for v5.2 Olof Johansson
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=f7c97dc7-0aa1-ea3b-b788-7fdf686181ed@monstr.eu \
--to=monstr@monstr.eu \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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