From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Chris Ruehl <chris.ruehl@gtsys.com.hk>
Cc: balbi@ti.com, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] usb: phy-generic: Add ULPI VBUS support
Date: Tue, 3 Dec 2013 10:15:56 +0200 [thread overview]
Message-ID: <20131203081556.GA26423@xps8300> (raw)
In-Reply-To: <1385967919-13258-4-git-send-email-chris.ruehl@gtsys.com.hk>
On Mon, Dec 02, 2013 at 03:05:19PM +0800, Chris Ruehl wrote:
> @@ -154,6 +164,27 @@ int usb_phy_gen_create_phy(struct device *dev, struct usb_phy_gen_xceiv *nop,
> {
> int err;
>
> + if (nop->ulpi_vbus > 0) {
> + unsigned int flags = 0;
> +
> + if (nop->ulpi_vbus & 0x1)
> + flags |= ULPI_OTG_DRVVBUS;
> + if (nop->ulpi_vbus & 0x2)
> + flags |= ULPI_OTG_DRVVBUS_EXT;
> + if (nop->ulpi_vbus & 0x4)
> + flags |= ULPI_OTG_EXTVBUSIND;
> + if (nop->ulpi_vbus & 0x8)
> + flags |= ULPI_OTG_CHRGVBUS;
> +
> + nop->ulpi = otg_ulpi_create(&ulpi_viewport_access_ops, flags);
> + if (!nop->ulpi) {
> + dev_err(dev, "Failed create ULPI Phy\n");
> + return -ENOMEM;
> + }
> + dev_dbg(dev, "Create ULPI Phy\n");
> + nop->ulpi->io_priv = nop->viewport;
> + }
This is so wrong. You are registering one kind of usb phy driver from
an other. Change drivers/usb/phy/ulpi.c to be a platform device. The
whole flag system in it is pretty horrid. While you are at it, change
that so it sets the values based on boolean flags from OF properties
or platform data.
NAK for the whole set.
--
heikki
next prev parent reply other threads:[~2013-12-03 8:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 7:05 [PATCH] usb: phy-generic, phy-ulpi patch set Chris Ruehl
[not found] ` <1385967919-13258-1-git-send-email-chris.ruehl-CR359r9tUDPXPF5Rlphj1Q@public.gmane.org>
2013-12-02 7:05 ` [PATCH 1/3] usb: phy-generic: Add GPIO based ChipSelect Chris Ruehl
[not found] ` <1385967919-13258-2-git-send-email-chris.ruehl-CR359r9tUDPXPF5Rlphj1Q@public.gmane.org>
2013-12-06 20:24 ` Felipe Balbi
[not found] ` <20131206202453.GF21086-HgARHv6XitL9zxVx7UNMDg@public.gmane.org>
2013-12-09 1:45 ` Chris Ruehl
2013-12-09 4:07 ` Felipe Balbi
[not found] ` <20131209040705.GB20608-HgARHv6XitL9zxVx7UNMDg@public.gmane.org>
2013-12-09 4:11 ` Chris Ruehl
2013-12-02 7:05 ` [PATCH 2/3] usb: phy-ulpi: Add EXTVBUSIND,CHRGVBUS flag support Chris Ruehl
2013-12-02 18:59 ` Sergei Shtylyov
2013-12-02 7:05 ` [PATCH 3/3] usb: phy-generic: Add ULPI VBUS support Chris Ruehl
[not found] ` <1385967919-13258-4-git-send-email-chris.ruehl-CR359r9tUDPXPF5Rlphj1Q@public.gmane.org>
2013-12-02 18:22 ` Mark Rutland
[not found] ` <20131202182204.GQ12952-NuALmloUBlrZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2013-12-03 2:46 ` Chris Ruehl
2013-12-03 5:24 ` Chris Ruehl
2013-12-03 8:15 ` Heikki Krogerus [this message]
2013-12-04 7:16 ` Chris Ruehl
[not found] ` <529ED6C5.3000608-CR359r9tUDPXPF5Rlphj1Q@public.gmane.org>
2013-12-04 9:49 ` Heikki Krogerus
2013-12-05 4:15 ` Chris Ruehl
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=20131203081556.GA26423@xps8300 \
--to=heikki.krogerus@linux.intel.com \
--cc=balbi@ti.com \
--cc=chris.ruehl@gtsys.com.hk \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.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).