From: chris.ruehl@gtsys.com.hk (Chris Ruehl)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] usb: chipidea: usbmisc: Add support for i.MX27/i.MX31 CPUs
Date: Tue, 14 Jan 2014 11:53:47 +0800 [thread overview]
Message-ID: <52D4B4CB.6050609@gtsys.com.hk> (raw)
In-Reply-To: <1389670245.433347746@f385.i.mail.ru>
On Tuesday, January 14, 2014 11:30 AM, Alexander Shiyan wrote:
> ???????????, 13 ?????? 2014, 22:31 +01:00 ?? Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>:
>> On Sat, Jan 11, 2014 at 06:01:48PM +0400, Alexander Shiyan wrote:
>>> ???????, 11 ?????? 2014, 13:55 +01:00 ?? Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>:
>>>> On Mon, Nov 11, 2013 at 11:09:16AM +0400, Alexander Shiyan wrote:
>>>>> Hello.
>>>>>
>>>>>>>>>> On Sunday, November 10, 2013 03:18 PM, Alexander Shiyan wrote:
>>>>>>>>>>> This adds i.MX27 and i.MX31 as the next user of the usbmisc driver.
>>>>>>>>>>>
>>>>>>>>>>> Signed-off-by: Alexander Shiyan<shc_work@mail.ru>
>>>>>>>>>>> ---
>>>>>>>>>>> drivers/usb/chipidea/usbmisc_imx.c | 42 ++++++++++++++++++++++++++++++++++++++
>>>>>>>>>>> 1 file changed, 42 insertions(+)
>>>>> ...
>>>>>> At this point might be good to patch the imx27.dtsi with the usb defines.
>>>>> ...
>>>>>
>>>>> I have a working configuration for i.MX27 USB, but I prefer to make a few more
>>>>> tests before the addition of definitions in DTS. This will be a next step.
>>>>> Thanks.
>>>> Any news here?
>>> Not ready yet.
>> Are you still working at it? Would you mind sharing more details, like
>> your current tree/patch stack and what works/doesn't work for you?
>
> Now my work on this is suspended, but will continue later.
> I'll send you a personal letter with DT configuration.
> Ports (both Host & OTG) are detected by kernel, but works Host only.
> OTG not works nor as Host, nor as Device...
>
> ---
hi,
I'm still working on my patches for imx27 and ULPI integration. But
have more urgent things in the queue.
I have a running version but it cant make it in the kernel. Rework on
platform device code needed.
Just wait until the patches already accepted appears in the linux-next
before commit new patches.
Chris
next prev parent reply other threads:[~2014-01-14 3:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-10 7:18 [PATCH 1/2] usb: chipidea: usbmisc: Add support for i.MX27/i.MX31 CPUs Alexander Shiyan
2013-11-10 7:18 ` [PATCH 2/2] usb: chipidea: usbmisc: Add support for i.MX51 CPU Alexander Shiyan
2013-11-14 11:42 ` Peter Chen
2013-11-14 18:07 ` Matt Sealey
2013-11-16 13:35 ` Peter Chen
2013-11-16 13:46 ` Alexander Shiyan
2013-11-17 4:52 ` Peter Chen
2013-11-11 2:30 ` [PATCH 1/2] usb: chipidea: usbmisc: Add support for i.MX27/i.MX31 CPUs Chris Ruehl
2013-11-11 4:45 ` Alexander Shiyan
2013-11-11 5:33 ` Chris Ruehl
2013-11-11 5:47 ` Alexander Shiyan
2013-11-11 6:10 ` Chris Ruehl
2013-11-11 7:09 ` Alexander Shiyan
2014-01-11 12:55 ` Uwe Kleine-König
2014-01-11 14:01 ` Alexander Shiyan
2014-01-13 21:31 ` Uwe Kleine-König
2014-01-14 3:30 ` Alexander Shiyan
2014-01-14 3:53 ` Chris Ruehl [this message]
2014-01-14 13:49 ` Uwe Kleine-König
2014-01-15 1:52 ` Chris Ruehl
2014-01-16 9:03 ` Uwe Kleine-König
2014-01-14 13:47 ` Uwe Kleine-König
2014-01-14 13:54 ` Uwe Kleine-König
2014-01-11 12:59 ` Uwe Kleine-König
2013-11-14 11:41 ` Peter Chen
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=52D4B4CB.6050609@gtsys.com.hk \
--to=chris.ruehl@gtsys.com.hk \
--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).