linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mkl@pengutronix.de (Marc Kleine-Budde)
To: linux-arm-kernel@lists.infradead.org
Subject: Want to Get Suggestion for MX28 USB Submisson
Date: Mon, 28 Nov 2011 10:44:05 +0100	[thread overview]
Message-ID: <4ED357E5.7020902@pengutronix.de> (raw)
In-Reply-To: <35AB98346D25394A9354ED89C4D76587225CFF@039-SN1MPN1-002.039d.mgd.msft.net>

On 11/28/2011 04:06 AM, Chen Peter-B29397 wrote:
> Hi lists:
> 
> Tony Lin has submitted Freescale mx28 USB Patch at August 
> (See: http://www.spinics.net/lists/linux-usb/msg50201.html), but it hasn't been accepted.
> I would like to re-submit mx28 usb patches, before that, I would like get some suggestion 
> from you. I think your suggestion will also be benefit for coming mx53, mx50 and mx6q's submission.
> 
> All Recently Freescale SoC's USB controller are the same, they are mx23, mx25, mx28, mx31, mx35,
> mx37, mx50, mx51, mx53, and mx6.
> But, the transceiver is different between them
> mx23, mx28, mx6 (Transceiver A)
> mx25 mx31, mx35,mx37, mx50, mx51, mx53 (Transceiver B)
> 
> Current upstream platform information:
> mx23 mx28 ==> mxs platfrom
> others (including mx6) ==> mxc platform
> 
> Current upstream USB information:
> mx25, mx3x, mx51: ehci-mxc.c (host), fsl_mxc_udc.c(device, main functions are at fsl_udc_core.c)
> 
> My plan of submitting mx28 (mx53,mx50, mx6 later if possible):
> 1. Replace cpu_is_mxxx() with struct platform_device_id for ehci-mxc.c and fsl_mxc_udc.c

The cpu_is_mxxx() code in the clock handling code can be removed by
introducing the missing clocks as no-op clocks on the other cores.

> 2. Using ehci-mxc.c and fsl_mxc_udc.c for mx28 upstreaming.
> For Step 2, I have concern that whether mxs platform users will be confused of their
> usb driver named xxx_mxc, not xxx_mxs?
> If mxs maintainers think it will cause confusion, I would like to change names to ehci-imx.c
> and fsl_imx_udc.c for all recent Freescale SoC's (from mx23 to mx6), is it suitable?
> 3. Create transceiver driver for mx28, and it will also be used for mx6.  

For the usb device part, I'm supporting with Robert's suggesting, first
mainline Heikki's otg patches, improve the ci13xxx driver.

cheers, Marc
-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20111128/4b215681/attachment.sig>

  parent reply	other threads:[~2011-11-28  9:44 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-28  3:06 Want to Get Suggestion for MX28 USB Submisson Chen Peter-B29397
2011-11-28  4:57 ` Greg KH
2011-11-28  5:24   ` Chen Peter-B29397
2011-11-28  5:32     ` Greg KH
2011-11-30  3:04   ` Shawn Guo
2011-11-30  3:08     ` Chen Peter-B29397
2011-11-28  7:08 ` Robert Schwebel
2011-11-28  8:10   ` Chen Peter-B29397
2011-11-28  8:17     ` Robert Schwebel
2011-11-28  9:02       ` Chen Peter-B29397
2011-11-28  9:44 ` Marc Kleine-Budde [this message]
2011-11-28 12:11   ` Chen Peter-B29397
2012-02-03 21:21 ` Marek Vasut
2012-02-04  1:24   ` Chen Peter-B29397
2012-02-04 10:17     ` Marek Vasut
2012-02-10  3:31       ` Chen Peter-B29397
2012-02-10  3:47         ` Marek Vasut
2012-03-14  3:24           ` Fabio Estevam
2012-03-14  3:30             ` Chen Peter-B29397
2012-03-14 19:24               ` Sascha Hauer
2012-03-16 23:13               ` Fabio Estevam
2012-03-18 12:06                 ` Chen Peter-B29397
2012-04-03  7:23                   ` Marek Vasut
2012-04-07  1:34                     ` Marek Vasut
2012-04-09 16:11                       ` Subodh Nijsure
2012-04-09 18:56                         ` Marek Vasut

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=4ED357E5.7020902@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).