public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: David Hewitt <davidmhewitt@gmail.com>
To: u-boot@lists.denx.de
Cc: David Hewitt <davidmhewitt@gmail.com>,
	Simon Glass <sjg@chromium.org>,
	Philipp Tomsich <philipp.tomsich@vrull.eu>,
	Kever Yang <kever.yang@rock-chips.com>,
	Peng Fan <peng.fan@nxp.com>,
	Jaehoon Chung <jh80.chung@samsung.com>
Subject: [PATCH 0/2] Add initial support for PINE64 PineTab2
Date: Mon, 10 Jul 2023 12:05:56 +0100	[thread overview]
Message-ID: <20230710110558.61852-1-davidmhewitt@gmail.com> (raw)

This is my first contribution to U-Boot and my first attempt at an
email-patch submission workflow. So please go easy on me!

This series of patches adds the basics required to get the PINE64
PineTab2 booting with U-Boot. This has only been tested thus far with 
eMMC and SD card booting, but I intend to do further work to get the 
display and USB tested and working in the future too.

Some minor modifications were required to the mmc tree due to a bug in 
the implementation of the Designware MMC controller where pulling PWREN
high causes it not to work.

David Hewitt (2):
  rockchip: Add initial support for the PineTab2 from PINE64
  mmc: Add quirk to disable PWREN for dw_mmc

 arch/arm/dts/Makefile                         |   1 +
 arch/arm/dts/rk3566-pinetab2.dts              | 422 ++++++++++++++++++
 arch/arm/mach-rockchip/rk3568/Kconfig         |   9 +
 board/pine64/pinetab2-rk3566/Kconfig          |  15 +
 board/pine64/pinetab2-rk3566/MAINTAINERS      |   7 +
 board/pine64/pinetab2-rk3566/Makefile         |   5 +
 .../pine64/pinetab2-rk3566/pinetab2-rk3566.c  |   1 +
 configs/pinetab2_defconfig                    |  83 ++++
 drivers/mmc/dw_mmc.c                          |   3 +-
 drivers/mmc/rockchip_dw_mmc.c                 |   3 +
 include/configs/pinetab2-rk3566.h             |  13 +
 include/configs/rk3568_common.h               |   4 +-
 include/dwmmc.h                               |   1 +
 13 files changed, 564 insertions(+), 3 deletions(-)
 create mode 100644 arch/arm/dts/rk3566-pinetab2.dts
 create mode 100644 board/pine64/pinetab2-rk3566/Kconfig
 create mode 100644 board/pine64/pinetab2-rk3566/MAINTAINERS
 create mode 100644 board/pine64/pinetab2-rk3566/Makefile
 create mode 100644 board/pine64/pinetab2-rk3566/pinetab2-rk3566.c
 create mode 100644 configs/pinetab2_defconfig
 create mode 100644 include/configs/pinetab2-rk3566.h

Signed-off-by: David Hewitt <davidmhewitt@gmail.com>
Cc: Simon Glass <sjg@chromium.org>
Cc: Philipp Tomsich <philipp.tomsich@vrull.eu>
Cc: Kever Yang <kever.yang@rock-chips.com>
Cc: Peng Fan <peng.fan@nxp.com>
Cc: Jaehoon Chung <jh80.chung@samsung.com>
-- 
2.34.1


             reply	other threads:[~2023-07-10 12:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10 11:05 David Hewitt [this message]
2023-07-10 11:05 ` [PATCH 1/2] rockchip: Add initial support for the PineTab2 from PINE64 David Hewitt
2023-07-10 17:18   ` Jonas Karlman
2023-07-10 11:05 ` [PATCH 2/2] mmc: Add quirk to disable PWREN for dw_mmc David Hewitt
2023-07-10 13:08   ` [PATCH v2 " David Hewitt
2023-07-10 16:51     ` Jonas Karlman

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=20230710110558.61852-1-davidmhewitt@gmail.com \
    --to=davidmhewitt@gmail.com \
    --cc=jh80.chung@samsung.com \
    --cc=kever.yang@rock-chips.com \
    --cc=peng.fan@nxp.com \
    --cc=philipp.tomsich@vrull.eu \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.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