From: balbi@ti•com (Felipe Balbi)
To: linux-arm-kernel@lists•infradead.org
Subject: [resend PATCH v3 4/4] usb: phy: add phy-hi6220-usb
Date: Mon, 23 Feb 2015 09:29:48 -0600 [thread overview]
Message-ID: <20150223152948.GD32701@saruman.tx.rr.com> (raw)
In-Reply-To: <BN3PR0301MB0849FB28B1DAF7BEB5F3BE7881250@BN3PR0301MB0849.namprd03.prod.outlook.com>
On Wed, Feb 11, 2015 at 01:30:53AM +0000, Peter Chen wrote:
>
> > > Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro•org>
> > > ---
> > > drivers/usb/phy/Kconfig | 9 ++
> > > drivers/usb/phy/Makefile | 1 +
> > > drivers/usb/phy/phy-hi6220-usb.c | 306
> > > +++++++++++++++++++++++++++++++++++++++
> > > 3 files changed, 316 insertions(+)
> > > create mode 100644 drivers/usb/phy/phy-hi6220-usb.c
> > >
> > > diff --git a/drivers/usb/phy/Kconfig b/drivers/usb/phy/Kconfig index
> > > c6d0c8e..405a3d0 100644
> > > --- a/drivers/usb/phy/Kconfig
> > > +++ b/drivers/usb/phy/Kconfig
> > > @@ -173,6 +173,15 @@ config USB_MXS_PHY
> > >
> > > MXS Phy is used by some of the i.MX SoCs, for example imx23/28/6x.
> > >
> > > +config USB_HI6220_PHY
> > > + tristate "hi6220 USB PHY support"
> > > + select USB_PHY
> > > + select MFD_SYSCON
> > > + help
> > > + Enable this to support the HISILICON HI6220 USB PHY.
> > > +
> > > + To compile this driver as a module, choose M here.
> > > +
> > > config USB_RCAR_PHY
> > > tristate "Renesas R-Car USB PHY support"
> > > depends on USB || USB_GADGET
> > > diff --git a/drivers/usb/phy/Makefile b/drivers/usb/phy/Makefile index
> > > 75f2bba..00172d3 100644
> > > --- a/drivers/usb/phy/Makefile
> > > +++ b/drivers/usb/phy/Makefile
> > > @@ -18,6 +18,7 @@ obj-$(CONFIG_SAMSUNG_USBPHY) += phy-
> > samsung-usb.o
> > > obj-$(CONFIG_TWL6030_USB) += phy-twl6030-usb.o
> > > obj-$(CONFIG_USB_EHCI_TEGRA) += phy-tegra-usb.o
> > > obj-$(CONFIG_USB_GPIO_VBUS) += phy-gpio-vbus-usb.o
> > > +obj-$(CONFIG_USB_HI6220_PHY) += phy-hi6220-usb.o
> >
> > new drivers only on drivers/phy/, sorry.
> >
>
> This driver has many USB dependencies, like otg, gadget. I don't know it
> can use generic phy currently.
then we improve generic phy framework. It's about time we moved
everything to that anyway.
--
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150223/1ab420a7/attachment.sig>
next prev parent reply other threads:[~2015-02-23 15:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 9:10 [resend PATCH v3 0/4] add usb support for hi6220 Zhangfei Gao
2015-02-10 9:10 ` [resend PATCH v3 1/4] Documentation: dt-bindings: add dt binding info for hi6220 dwc2 Zhangfei Gao
2015-02-10 9:10 ` [resend PATCH v3 2/4] Documentation: dt-bindings: add dt binding info for hi6220 Zhangfei Gao
2015-02-10 11:37 ` Sergei Shtylyov
2015-02-10 9:10 ` [resend PATCH v3 3/4] usb: dwc2: platform: add hi6220 support Zhangfei Gao
2015-02-10 9:10 ` [resend PATCH v3 4/4] usb: phy: add phy-hi6220-usb Zhangfei Gao
2015-02-10 14:48 ` Felipe Balbi
2015-02-10 14:53 ` zhangfei
2015-02-23 15:29 ` Felipe Balbi
2015-02-11 1:30 ` Peter Chen
2015-02-11 9:10 ` Baruch Siach
2015-02-23 15:30 ` Felipe Balbi
2015-02-23 15:29 ` Felipe Balbi [this message]
2015-02-11 15:17 ` zhangfei
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=20150223152948.GD32701@saruman.tx.rr.com \
--to=balbi@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/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