public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Akash Gajjar <akash@openedev•com>
To: heiko@sntech•de
Cc: Mark Rutland <mark.rutland@arm•com>,
	devicetree@vger•kernel.org, tom@radxa•com,
	linux-kernel@vger•kernel.org, kever.yang@rock-chips•com,
	Kishon Vijay Abraham I <kishon@ti•com>,
	linux-rockchip@lists•infradead.org,
	Rob Herring <robh+dt@kernel•org>,
	Akash Gajjar <akash@openedev•com>,
	Andy Yan <andy.yan@rock-chips•com>,
	jagan@openedev•com, linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/2] add usb2-phy support for RK3308 SoC
Date: Tue, 17 Dec 2019 13:27:13 +0530	[thread overview]
Message-ID: <20191217075722.11646-1-akash@openedev.com> (raw)

Add usb2-phy support in RK3308 SoC dtsi
Add usb2-phy support for RK3308 SoC in Rockchip USB driver

- Tested USB2.0 with these patches on RockPiS board and Mainline Linux kernel

Akash Gajjar (2):
  arch: arm64: rockchip: add usb node for RK3308
  phy: phy-rockchip-inno-usb2: add usb2-phy support for RK3308 SoC

 .../bindings/phy/phy-rockchip-inno-usb2.txt   |  1 +
 arch/arm64/boot/dts/rockchip/rk3308.dtsi      | 49 +++++++++++++++++++
 drivers/phy/rockchip/phy-rockchip-inno-usb2.c | 44 +++++++++++++++++
 3 files changed, 94 insertions(+)

-- 
2.17.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2019-12-17  9:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-17  7:57 Akash Gajjar [this message]
2019-12-17  7:57 ` [PATCH 1/2] arch: arm64: rockchip: add usb node for RK3308 Akash Gajjar
2019-12-17  7:57 ` [PATCH 2/2] phy: phy-rockchip-inno-usb2: add usb2-phy support for RK3308 SoC Akash Gajjar
2019-12-26 21:07   ` Rob Herring

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=20191217075722.11646-1-akash@openedev.com \
    --to=akash@openedev$(echo .)com \
    --cc=andy.yan@rock-chips$(echo .)com \
    --cc=devicetree@vger$(echo .)kernel.org \
    --cc=heiko@sntech$(echo .)de \
    --cc=jagan@openedev$(echo .)com \
    --cc=kever.yang@rock-chips$(echo .)com \
    --cc=kishon@ti$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-rockchip@lists$(echo .)infradead.org \
    --cc=mark.rutland@arm$(echo .)com \
    --cc=robh+dt@kernel$(echo .)org \
    --cc=tom@radxa$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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