cip-dev.lists.cip-project.org archive mirror
 help / color / mirror / Atom feed
From: Biju Das <biju.das.jz@bp.renesas.com>
To: cip-dev@lists.cip-project.org,
	Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>,
	Pavel Machek <pavel@denx.de>
Cc: Chris Paterson <chris.paterson2@renesas.com>,
	Biju Das <biju.das.jz@bp.renesas.com>,
	Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: [cip-dev] [PATCH 4.4.y-cip 0/5] Add RZ/G1H MMC/SDHI support
Date: Wed,  2 Sep 2020 08:50:30 +0100	[thread overview]
Message-ID: <20200902075035.4445-1-biju.das.jz@bp.renesas.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 935 bytes --]

This patch series add support MMC/SDHI for iWave RZ/G1H board based on
r8a7742 SoC to 4.4.y-cip kernel. All patches in this series
are cherry-picked from mainline.

Lad Prabhakar (4):
  dt-bindings: mmc: renesas,sdhi: Document r8a7742 support
  ARM: dts: r8a7742: Add SDHI nodes
  ARM: dts: r8a7742: Add MMC0 node
  ARM: dts: r8a7742-iwg21d-q7: Enable SDHI2 controller

Yoshihiro Shimoda (1):
  ARM: dts: renesas: Fix SD Card/eMMC interface device node names

 .../devicetree/bindings/mmc/tmio_mmc.txt      |  1 +
 arch/arm/boot/dts/r8a7742-iwg21d-q7.dts       | 39 ++++++++++
 arch/arm/boot/dts/r8a7742.dtsi                | 71 +++++++++++++++++++
 arch/arm/boot/dts/r8a7743.dtsi                |  6 +-
 arch/arm/boot/dts/r8a7744.dtsi                |  6 +-
 arch/arm/boot/dts/r8a7745.dtsi                |  6 +-
 arch/arm/boot/dts/r8a77470.dtsi               |  6 +-
 7 files changed, 123 insertions(+), 12 deletions(-)

-- 
2.17.1


[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5363): https://lists.cip-project.org/g/cip-dev/message/5363
Mute This Topic: https://lists.cip-project.org/mt/76578438/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

             reply	other threads:[~2020-09-02 12:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02  7:50 Biju Das [this message]
2020-09-02  7:50 ` [cip-dev] [PATCH 4.4.y-cip 1/5] dt-bindings: mmc: renesas,sdhi: Document r8a7742 support Biju Das
2020-09-02  7:50 ` [cip-dev] [PATCH 4.4.y-cip 2/5] ARM: dts: r8a7742: Add SDHI nodes Biju Das
2020-09-02  7:50 ` [cip-dev] [PATCH 4.4.y-cip 3/5] ARM: dts: r8a7742: Add MMC0 node Biju Das
2020-09-02  7:50 ` [cip-dev] [PATCH 4.4.y-cip 4/5] ARM: dts: r8a7742-iwg21d-q7: Enable SDHI2 controller Biju Das
2020-09-02  7:50 ` [cip-dev] [PATCH 4.4.y-cip 5/5] ARM: dts: renesas: Fix SD Card/eMMC interface device node names Biju Das
2020-09-02  9:02 ` [cip-dev] [PATCH 4.4.y-cip 0/5] Add RZ/G1H MMC/SDHI support Nobuhiro Iwamatsu
2020-09-02 13:33   ` Pavel Machek
2020-09-03  6:20     ` Nobuhiro Iwamatsu

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=20200902075035.4445-1-biju.das.jz@bp.renesas.com \
    --to=biju.das.jz@bp.renesas.com \
    --cc=chris.paterson2@renesas.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    --cc=pavel@denx.de \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    /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).