public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: Priyanka Jain <priyanka.jain@nxp.com>, Wolfgang Denk <wd@denx.de>,
	Sinan Akman <sinan@writeme.com>
Cc: u-boot@lists.denx.de
Subject: [PATCH 0/9] powerpc: dts: p2020: Linux compatibility
Date: Fri,  8 Apr 2022 14:39:49 +0200	[thread overview]
Message-ID: <20220408123958.25724-1-pali@kernel.org> (raw)

This patch series extends P2020 dtsi include files to generate board DTS
files compatible for Linux kernel. The aim is to have one DTB file
suitable for both Linux kernel and U-Boot.

Depends on:
http://patchwork.ozlabs.org/project/uboot/patch/20220402224226.20403-3-pali@kernel.org/
http://patchwork.ozlabs.org/project/uboot/patch/20220405092325.20174-1-pali@kernel.org/

Pali Rohár (9):
  powerpc: dts: p2020: Add gpio-controller@fc00 node via pq3-gpio-0.dtsi
  powerpc: dts: p2020: Make PCIe nodes compatible for Linux kernel
    driver
  powerpc: dts: p2020: Add ptp_clock@24e00 node via
    pq3-etsec1-timer-0.dtsi
  powerpc: dts: p2020: Add Linux compatible string and property for
    eSDHC
  powerpc: dts: p2020: Do not automatically disable spi@7000 node in
    p2020-post.dtsi
  powerpc: dts: p2020: Add missing interrupts property to spi@7000 node
  powerpc: dts: p2020: Make usb@22000 node compatible for Linux kernel
    driver
  powerpc: dts: p2020: Define L2 cache node
  powerpc: dts: p2020: Set dfsrr property for i2c nodes

 arch/powerpc/dts/p2020-post.dtsi         | 90 ++++++++++++++++++++++--
 arch/powerpc/dts/p2020.dtsi              |  2 +
 arch/powerpc/dts/p2020rdb-pc.dts         |  1 -
 arch/powerpc/dts/p2020rdb-pc_36b.dts     |  1 -
 arch/powerpc/dts/pq3-etsec1-timer-0.dtsi | 39 ++++++++++
 arch/powerpc/dts/pq3-gpio-0.dtsi         | 41 +++++++++++
 arch/powerpc/dts/pq3-i2c-0.dtsi          |  1 +
 arch/powerpc/dts/pq3-i2c-1.dtsi          |  1 +
 8 files changed, 168 insertions(+), 8 deletions(-)
 create mode 100644 arch/powerpc/dts/pq3-etsec1-timer-0.dtsi
 create mode 100644 arch/powerpc/dts/pq3-gpio-0.dtsi

-- 
2.20.1


             reply	other threads:[~2022-04-08 12:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 12:39 Pali Rohár [this message]
2022-04-08 12:39 ` [PATCH 1/9] powerpc: dts: p2020: Add gpio-controller@fc00 node via pq3-gpio-0.dtsi Pali Rohár
2022-04-08 12:39 ` [PATCH 2/9] powerpc: dts: p2020: Make PCIe nodes compatible for Linux kernel driver Pali Rohár
2022-04-08 12:39 ` [PATCH 3/9] powerpc: dts: p2020: Add ptp_clock@24e00 node via pq3-etsec1-timer-0.dtsi Pali Rohár
2022-04-08 12:39 ` [PATCH 4/9] powerpc: dts: p2020: Add Linux compatible string and property for eSDHC Pali Rohár
2022-04-08 12:39 ` [PATCH 5/9] powerpc: dts: p2020: Do not automatically disable spi@7000 node in p2020-post.dtsi Pali Rohár
2022-04-08 12:39 ` [PATCH 6/9] powerpc: dts: p2020: Add missing interrupts property to spi@7000 node Pali Rohár
2022-04-08 12:39 ` [PATCH 7/9] powerpc: dts: p2020: Make usb@22000 node compatible for Linux kernel driver Pali Rohár
2022-04-08 12:39 ` [PATCH 8/9] powerpc: dts: p2020: Define L2 cache node Pali Rohár
2022-04-08 12:39 ` [PATCH 9/9] powerpc: dts: p2020: Set dfsrr property for i2c nodes Pali Rohár

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=20220408123958.25724-1-pali@kernel.org \
    --to=pali@kernel.org \
    --cc=priyanka.jain@nxp.com \
    --cc=sinan@writeme.com \
    --cc=u-boot@lists.denx.de \
    --cc=wd@denx.de \
    /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