From: Chris Metcalf <cmetcalf@tilera.com>
To: Greg KH <greg@kroah.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-usb@vger.kernel.org>
Subject: Re: [PATCH 1/3] arch/tile: provide kernel support for the tilegx USB shim
Date: Fri, 6 Jul 2012 13:59:48 -0400 [thread overview]
Message-ID: <4FF72794.7010009@tilera.com> (raw)
In-Reply-To: <20120706173635.GB2373@kroah.com>
On 7/6/2012 1:36 PM, Greg KH wrote:
> On Wed, May 09, 2012 at 12:25:02PM -0400, Chris Metcalf wrote:
>> This change adds support for accessing the USB shim from within the
>> kernel. Note that this change by itself does not allow the kernel
>> to act as a host or as a device; it merely exposes the built-in on-chip
>> hardware to the kernel.
> What do you mean by this? This is needed for the other patches, right?
> If so, I'm guessing they are going through the tile tree? That's fine
> with me.
Correct; this piece just adds the infrastructure that lets you then layer
the standard USB host code on top. I'm assuming I'll push both the tilegx
USB infrastructure, and the drivers/usb/host stuff, through the tile tree.
Or, I can push just the low-level stuff through the tile tree and let the
USB host stuff go through the usb tree.
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
next prev parent reply other threads:[~2012-07-06 17:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 16:25 [PATCH 1/3] arch/tile: provide kernel support for the tilegx USB shim Chris Metcalf
2012-06-16 17:58 ` [PATCH 2/3] usb: add host support for the tilegx architecture Chris Metcalf
2012-06-16 20:41 ` [PATCH 3/3] bounce: allow use of bounce pool via config option Chris Metcalf
2012-07-06 17:36 ` [PATCH 1/3] arch/tile: provide kernel support for the tilegx USB shim Greg KH
2012-07-06 17:59 ` Chris Metcalf [this message]
2012-07-06 18:37 ` Greg KH
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=4FF72794.7010009@tilera.com \
--to=cmetcalf@tilera.com \
--cc=greg@kroah.com \
--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