public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Venu Byravarasu <vbyravarasu@nvidia.com>
Cc: "balbi@ti.com" <balbi@ti.com>,
	"stern@rowland.harvard.edu" <stern@rowland.harvard.edu>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 resend] USB: PHY: Re-organize Tegra USB PHY driver
Date: Tue, 23 Oct 2012 13:53:39 +0300	[thread overview]
Message-ID: <20121023105339.GD24820@arwen.pp.htv.fi> (raw)
In-Reply-To: <D958900912E20642BCBC71664EFECE3E6DE0B97217@BGMAIL02.nvidia.com>

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

Hi,

On Tue, Oct 23, 2012 at 04:23:19PM +0530, Venu Byravarasu wrote:
> > -----Original Message-----
> > From: Venu Byravarasu
> > Sent: Monday, October 22, 2012 4:04 PM
> > To: 'balbi@ti.com'
> > Cc: stern@rowland.harvard.edu; gregkh@linuxfoundation.org; linux-
> > usb@vger.kernel.org; linux-kernel@vger.kernel.org
> > Subject: RE: [PATCH v3 resend] USB: PHY: Re-organize Tegra USB PHY driver
> > 
> > >
> > > what is this SOC dependent PHY driver ?
> > 
> > SOC dependent PHY driver actually deals with the PHY interface
> > programming.
> > e.g. please see code present in tegra2_usb_driver.c.
> > 
> > > What sort of dependencies are
> > > there ? Those differences should be handled with runtime checks.
> > 
> > As PHY related bugs got fixed across different set of SOCs apart from
> > adding few features, wanted to separate this out from common PHY
> > functionality. This will help us in adding support for different SOCs with
> > minimum set of changes.
> 
> Felipe,
> 
> Please let me know if you have any more questions on this patch.
> If not, can you please merge this?

Like I said before, those differences should be handled by runtime
checks, you shouldn't need separate files for that. What you need to do
is implement a single PHY driver which can handle all tegras known to
date, later you can add support for new tegras by patching a few things
here and there.

-- 
balbi

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

  reply	other threads:[~2012-10-23 10:59 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
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 [this message]
  -- 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=20121023105339.GD24820@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox