linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: George Hilliard <thirtythreeforty@gmail.com>
To: Chen-Yu Tsai <wens@csie.org>, Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>
Cc: George Hilliard <thirtythreeforty@gmail.com>,
	Icenowy Zheng <icenowy@aosc.io>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RESEND PATCH 2/5] phy: sun4i-usb: add support for the USB PHY on suniv SoC
Date: Mon,  9 Mar 2020 15:43:23 -0500	[thread overview]
Message-ID: <20200309204326.27403-3-thirtythreeforty@gmail.com> (raw)
In-Reply-To: <20200309204326.27403-1-thirtythreeforty@gmail.com>

The suniv SoC has one USB OTG port connected to a MUSB controller.

Add support for its USB PHY.

Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
Signed-off-by: George Hilliard <thirtythreeforty@gmail.com>
---
 drivers/phy/allwinner/phy-sun4i-usb.c | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/drivers/phy/allwinner/phy-sun4i-usb.c b/drivers/phy/allwinner/phy-sun4i-usb.c
index 856927382248..5fb0c42fe8fd 100644
--- a/drivers/phy/allwinner/phy-sun4i-usb.c
+++ b/drivers/phy/allwinner/phy-sun4i-usb.c
@@ -98,6 +98,7 @@
 #define POLL_TIME			msecs_to_jiffies(250)
 
 enum sun4i_usb_phy_type {
+	suniv_f1c100s_phy,
 	sun4i_a10_phy,
 	sun6i_a31_phy,
 	sun8i_a33_phy,
@@ -859,6 +860,14 @@ static int sun4i_usb_phy_probe(struct platform_device *pdev)
 	return 0;
 }
 
+static const struct sun4i_usb_phy_cfg suniv_f1c100s_cfg = {
+	.num_phys = 1,
+	.type = suniv_f1c100s_phy,
+	.disc_thresh = 3,
+	.phyctl_offset = REG_PHYCTL_A10,
+	.dedicated_clocks = true,
+};
+
 static const struct sun4i_usb_phy_cfg sun4i_a10_cfg = {
 	.num_phys = 3,
 	.type = sun4i_a10_phy,
@@ -973,6 +982,8 @@ static const struct sun4i_usb_phy_cfg sun50i_h6_cfg = {
 };
 
 static const struct of_device_id sun4i_usb_phy_of_match[] = {
+	{ .compatible = "allwinner,suniv-f1c100s-usb-phy",
+	  .data = &suniv_f1c100s_cfg },
 	{ .compatible = "allwinner,sun4i-a10-usb-phy", .data = &sun4i_a10_cfg },
 	{ .compatible = "allwinner,sun5i-a13-usb-phy", .data = &sun5i_a13_cfg },
 	{ .compatible = "allwinner,sun6i-a31-usb-phy", .data = &sun6i_a31_cfg },
-- 
2.25.0


  parent reply	other threads:[~2020-03-09 20:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-09 20:43 [RESEND PATCH 0/5] Support the Allwinner F1C100s USB stack George Hilliard
2020-03-09 20:43 ` [RESEND PATCH 1/5] dt-bindings: Add new F1C100s compatible strings for USB George Hilliard
2020-03-12  6:53   ` Chen-Yu Tsai
2020-03-09 20:43 ` George Hilliard [this message]
2020-03-12  6:51   ` [RESEND PATCH 2/5] phy: sun4i-usb: add support for the USB PHY on suniv SoC Chen-Yu Tsai
2020-03-12  6:54     ` Chen-Yu Tsai
2020-03-12 12:06     ` George Hilliard
2020-03-13  4:07       ` Chen-Yu Tsai
2020-03-13 14:03         ` George Hilliard
2020-03-09 20:43 ` [RESEND PATCH 3/5] musb: sunxi: add support for the suniv MUSB controller George Hilliard
2020-03-12  6:55   ` Chen-Yu Tsai
2020-03-09 20:43 ` [RESEND PATCH 4/5] ARM: suniv: add USB-related device nodes George Hilliard
2020-03-09 20:43 ` [RESEND PATCH 5/5] ARM: suniv: f1c100s: enable USB on Lichee Pi Nano George Hilliard

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=20200309204326.27403-3-thirtythreeforty@gmail.com \
    --to=thirtythreeforty@gmail.com \
    --cc=icenowy@aosc.io \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).