From: arnaud.patard@rtp-net.org (Arnaud Patard (Rtp))
To: linux-arm-kernel@lists.infradead.org
Subject: [patch 2/5] ulpi: handle ULPI_OTG_CTRL_CHRGVBUS
Date: Thu, 23 Dec 2010 21:11:03 +0100 [thread overview]
Message-ID: <8762ukb67c.fsf@lechat.rtp-net.org> (raw)
In-Reply-To: <4D109C47.6020704@compulab.co.il> (Igor Grinberg's message of "Tue, 21 Dec 2010 14:23:35 +0200")
Igor Grinberg <grinberg@compulab.co.il> writes:
> Hi Arnaud,
>
> On 12/20/10 17:48, Arnaud Patard (Rtp) wrote:
>> Current code doesn't handle setting CHRGVBUS when enabling vbus.
>> Add support for it
>>
>>
>>
>> Signed-off-by: Arnaud Patard <arnaud.patard@rtp-net.org>
>> Index: tst-usb/drivers/usb/otg/ulpi.c
>> ===================================================================
>> --- tst-usb.orig/drivers/usb/otg/ulpi.c 2010-12-20 15:38:41.000000000 +0100
>> +++ tst-usb/drivers/usb/otg/ulpi.c 2010-12-20 15:38:57.000000000 +0100
>> @@ -234,7 +234,8 @@
>> {
>> unsigned int flags = otg_io_read(otg, ULPI_OTG_CTRL);
>>
>> - flags &= ~(ULPI_OTG_CTRL_DRVVBUS | ULPI_OTG_CTRL_DRVVBUS_EXT);
>> + flags &= ~(ULPI_OTG_CTRL_DRVVBUS | ULPI_OTG_CTRL_DRVVBUS_EXT |
>> + ULPI_OTG_CTRL_CHRGVBUS);
>>
>> if (on) {
>> if (otg->flags & ULPI_OTG_DRVVBUS)
>> @@ -242,6 +243,9 @@
>>
>> if (otg->flags & ULPI_OTG_DRVVBUS_EXT)
>> flags |= ULPI_OTG_CTRL_DRVVBUS_EXT;
>> +
>> + if (otg->flags & ULPI_OTG_CHRGVBUS)
>> + flags |= ULPI_OTG_CTRL_CHRGVBUS;
>> }
>>
>> return otg_io_write(otg, flags, ULPI_OTG_CTRL);
>
> I think this is a wrong place to set the ChrgVbus bit.
> As for ULPI spec. 1.1:
> "3.8.7.1 Session Request Protocol (SRP)
> ULPI provides full SRP support. The Link uses the ChrgVbus and DischrgVbus bits
> in the OTG Control register to begin and end a session."
>
> So it is used for SRP.
> May be it is better to implement
> int (*start_srp)(struct otg_transceiver *otg);
> method for setting this bit?
>
I was not sure on where to put this so I took the same approach as the
fsl bsp which was to set it in this function and to call this function
_after_ usb_add_hcd() [ see my previous patch ]. Indeed, it fixed my
issue so I believe it not so bad given that there has already been some
troubles on the ehci-mxc init.
Arnaud
next prev parent reply other threads:[~2010-12-23 20:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 15:48 [patch 0/5] iMX51 usb fixes Arnaud Patard (Rtp)
2010-12-20 15:48 ` [patch 1/5] ehci-mxc: Enable vbus later Arnaud Patard (Rtp)
2010-12-21 9:31 ` Sascha Hauer
2010-12-23 20:15 ` Arnaud Patard (Rtp)
2011-01-03 14:38 ` Sascha Hauer
2010-12-20 15:48 ` [patch 2/5] ulpi: handle ULPI_OTG_CTRL_CHRGVBUS Arnaud Patard (Rtp)
2010-12-21 12:23 ` Igor Grinberg
2010-12-23 20:11 ` Arnaud Patard (Rtp) [this message]
2010-12-24 15:05 ` Igor Grinberg
2011-01-03 11:41 ` Arnaud Patard (Rtp)
2011-01-03 13:33 ` Igor Grinberg
2011-01-03 14:04 ` Arnaud Patard (Rtp)
2011-01-04 7:55 ` Igor Grinberg
2011-01-04 20:00 ` Arnaud Patard (Rtp)
2011-01-04 20:03 ` Matt Sealey
2011-01-06 7:54 ` Igor Grinberg
2011-01-07 9:02 ` Arnaud Patard (Rtp)
2011-01-10 13:45 ` Igor Grinberg
2011-01-10 14:22 ` Arnaud Patard (Rtp)
2011-01-11 7:41 ` Igor Grinberg
2010-12-20 15:48 ` [patch 3/5] arch/arm/plat-mxc/ehci.c: fix errors/typos Arnaud Patard (Rtp)
2010-12-20 15:48 ` [patch 4/5] MX51: Add support for usb host 2 Arnaud Patard (Rtp)
2010-12-20 15:48 ` [patch 5/5] mx51: fix usb clock support Arnaud Patard (Rtp)
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=8762ukb67c.fsf@lechat.rtp-net.org \
--to=arnaud.patard@rtp-net.org \
--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).