Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: John Crispin <john@phrozen.org>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH 3/3] owrt: MIPS: ralink: add usb platform support
Date: Mon, 15 Apr 2013 15:23:28 +0400	[thread overview]
Message-ID: <516BE330.2000502@cogentembedded.com> (raw)
In-Reply-To: <516BD656.6090709@phrozen.org>

Hello.

On 15-04-2013 14:28, John Crispin wrote:

>> From: John Crispin<blogic@openwrt.org>

>> Add code to load the platform ehci/ohci driver on Ralink SoC. For the usb core
>> to work we need to populate the platform_data during boot, prior to the usb
>> driver being loaded.

>> Signed-off-by: John Crispin<blogic@openwrt.org>
>> [matthijs@stdin.nl: Extracted non-ohci/ehci 3052 code into separate patch]
>> Signed-off-by: Matthijs Kooijman<matthijs@stdin.nl>

> this patch sits ontop of a patch from openwrt that adds a OF binding for
> ohci/ehci so it wont go upstream until the usb people decided how to expose
> ohci-platform and ehci-platform in OF

    Note that there's already a patch exposing ehci-platform to DT in Greg's 
'usb-next' branch:

https://git.kernel.org/cgit/linux/kernel/git/gregkh/usb.git/commit/?h=usb-next&id=f3bc64d6d1f21c1b92d75f233a37b75d77af6963

>      John

WBR, Sergei

      reply	other threads:[~2013-04-15 11:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15 10:27 [PATCH 1/3] MIPS: ralink: use the dwc2 driver for the rt305x USB controller Matthijs Kooijman
2013-04-15 10:27 ` [PATCH 2/3] MIPS: ralink: setup dma_mask for the rt305x dwc2 usb controller Matthijs Kooijman
2013-04-15 11:04   ` John Crispin
2013-04-15 10:27 ` [PATCH 3/3] owrt: MIPS: ralink: add usb platform support Matthijs Kooijman
2013-04-15 10:28   ` John Crispin
2013-04-15 11:23     ` Sergei Shtylyov [this message]

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=516BE330.2000502@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=john@phrozen.org \
    --cc=linux-mips@linux-mips.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