All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Venu Byravarasu <vbyravarasu@nvidia.com>
Cc: <stern@rowland.harvard.edu>, <gregkh@linuxfoundation.org>,
	<balbi@ti.com>, <linux-usb@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 resend] USB: PHY: Re-organize Tegra USB PHY driver
Date: Fri, 19 Oct 2012 18:35:56 +0300	[thread overview]
Message-ID: <20121019153555.GC440@arwen.pp.htv.fi> (raw)
In-Reply-To: <1350643085-27294-1-git-send-email-vbyravarasu@nvidia.com>

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

Hi,

On Fri, Oct 19, 2012 at 04:08:05PM +0530, Venu Byravarasu wrote:
> NVIDIA produces several Tegra SoCs viz Tegra20, Tegra30 etc.
> In order to support USB PHY drivers on these SoCs, existing
> PHY driver is split into SoC agnostic common USB PHY driver
> and Tegra20-specific USB phy driver. This will facilitate
> easy addition and deletion of phy drivers for Tegra SoCs.
> 
> Signed-off-by: Venu Byravarasu <vbyravarasu@nvidia.com>

I was reading this "driver" more closely and I have a bunch of questions
about it, but the most important of all of them is: "why isn't that a
real PHY driver ?". It doesn't have a probe() function, it doesn't use
struct usb_phy to represent the PHY, it has a bunch of tegra-specific
APIs and we can't let those continue.

Please, take a look at drivers/usb/phy/omap_usb2.c (misnamed actually,
should be phy-omap-usb2.c so we have a common prefix) to see how your
PHY driver should look like and which sort of functionality if should
expose to the rest of the kernel.

Please comment on the above.

cheers

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2012-10-19 15:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-19 10:38 [PATCH v3 resend] USB: PHY: Re-organize Tegra USB PHY driver Venu Byravarasu
2012-10-19 14:46 ` Alan Stern
2012-10-19 15:35 ` Felipe Balbi [this message]
2012-10-19 16:29   ` Stephen Warren
2012-10-22  7:56     ` Felipe Balbi
2012-10-22 14:21       ` Alan Stern
2012-10-22  8:30   ` Venu Byravarasu
2012-10-22 10:02     ` Felipe Balbi
2012-10-22 10:17       ` Venu Byravarasu
2012-10-22 10:16         ` Felipe Balbi
2012-10-22 10:33           ` Venu Byravarasu
2012-10-23 10:53           ` Venu Byravarasu
2012-10-23 10:53             ` Felipe Balbi
  -- strict thread matches above, loose matches on Subject: below --
2012-10-19 10:33 Venu Byravarasu
2012-10-19 10:32 ` Felipe Balbi
2012-10-19 10:43   ` Venu Byravarasu

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=20121019153555.GC440@arwen.pp.htv.fi \
    --to=balbi@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=vbyravarasu@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.