public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: balbi@ti.com
Cc: Venu Byravarasu <vbyravarasu@nvidia.com>,
	gregkh@linuxfoundation.org, stern@rowland.harvard.edu,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-tegra@vger.kernel.org
Subject: Re: [PATCH v2 4/4] usb: Add APIs to access host registers from Tegra PHY
Date: Thu, 17 Jan 2013 15:18:43 -0700	[thread overview]
Message-ID: <50F878C3.9030002@wwwdotorg.org> (raw)
In-Reply-To: <20130117090255.GD10814@arwen.pp.htv.fi>

On 01/17/2013 02:02 AM, Felipe Balbi wrote:
> Hi,
> 
> On Thu, Jan 17, 2013 at 01:58:12PM +0530, Venu Byravarasu wrote:
>> As Tegra PHY driver need to access one of the Host registers, 
>> added few APIs to ehci tegra driver.
>> 
>> Signed-off-by: Venu Byravarasu <vbyravarasu@nvidia.com>
> 
> Stephen is this another of those patches you're gonna take care of 
> yourself ?

Yes; in kernel 3.9, I believe I need to take any significant Tegra
EHCI or PHY patches through the Tegra tree due to the need to change
the Tegra device trees in lock-step with some of the code changes, and
other Tegra-related changes also changing the USB-related nodes in
device tree e.g. to add clocks properties.

Hopefully we get enough USB patches into 3.9 that the dependencies are
then removed, and we can revert back to the usual merging path in 3.10...

  parent reply	other threads:[~2013-01-17 22:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17  8:28 [PATCH v2 4/4] usb: Add APIs to access host registers from Tegra PHY Venu Byravarasu
     [not found] ` <1358411292-12288-1-git-send-email-vbyravarasu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-01-17  9:02   ` Felipe Balbi
     [not found]     ` <20130117090255.GD10814-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2013-01-17 12:37       ` Venu Byravarasu
     [not found]         ` <D958900912E20642BCBC71664EFECE3E6E1A6F0F97-QZ+emBqkIFBDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2013-01-17 13:50           ` Felipe Balbi
     [not found]             ` <20130117135043.GU18978-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2013-01-17 15:21               ` Alan Stern
     [not found]                 ` <Pine.LNX.4.44L0.1301171016550.1339-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2013-01-17 15:32                   ` Felipe Balbi
     [not found]                     ` <20130117153229.GA21904-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2013-01-17 16:03                       ` Alan Stern
     [not found]                         ` <Pine.LNX.4.44L0.1301171054220.1339-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2013-01-18  5:39                           ` Venu Byravarasu
2013-01-17 22:18     ` Stephen Warren [this message]
2013-01-17 15:15 ` Alan Stern
     [not found]   ` <Pine.LNX.4.44L0.1301171012500.1339-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2013-01-18  4:56     ` Venu Byravarasu
2013-01-18  5:42   ` 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=50F878C3.9030002@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=balbi@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@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