From: Pavan Kondeti <pkondeti@codeaurora.org>
To: balbi@ti.com
Cc: Sergei Shtylyov <sshtylyov@mvista.com>,
linux-usb@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [RFC v2 4/4] USB: Eliminate delays involved in root hub initialization during HNP
Date: Thu, 16 Dec 2010 18:43:16 +0530 [thread overview]
Message-ID: <4D0A106C.3030608@codeaurora.org> (raw)
In-Reply-To: <20101216130756.GE6652@legolas.emea.dhcp.ti.com>
On 12/16/2010 6:37 PM, Felipe Balbi wrote:
> On Thu, Dec 16, 2010 at 03:39:35PM +0300, Sergei Shtylyov wrote:
>> Hello.
>>
>> On 16-12-2010 14:09, Pavankumar Kondeti wrote:
>>
>>> Some USB controllers have common resources (IRQ, register address
>>> space) for Host, Peripheral and OTG. So HCD is added only before
>>> entering into Host mode. Root hub initialization is done in
>>> different steps to decrease boot up time. But this makes B-device
>>> difficult to meet HNP timings. Hence eliminate delays involved in
>>> root hub initialization for B-host.
>>
>>> This patch also marks hnp_supported flag TRUE for B-host while
>>> registering the bus.
>>
>>> Change-Id: I821775e8c90bd71a7abbe17176f189664a1841e1
>>> Signed-off-by: Pavankumar Kondeti<pkondeti@codeaurora.org>
>> [...]
>>
>>> index ac79fd5..2df61ba 100644
>>> --- a/drivers/usb/core/hub.c
>>> +++ b/drivers/usb/core/hub.c
>>> @@ -680,6 +680,7 @@ static void hub_activate(struct usb_hub *hub, enum hub_activation_type type)
>>> int status;
>>> bool need_debounce_delay = false;
>>> unsigned delay;
>>> + bool hnp_in_progress = hdev->bus->is_b_host&& (type == HUB_INIT);
>>
>> Parens here are not necessary.
>
> there's also a missing space before &&
>
There is one. Please see my original patch. I am not sure why it is
missing in Sergei's reply.
Thanks,
Pavan
--
Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2010-12-16 13:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 11:08 [RFC v2 0/4] USB core changes for supporting OTG on MSM SoC Pavankumar Kondeti
2010-12-16 11:08 ` [RFC v2 1/4] USB: core: OTG Supplement Revision 2.0 updates Pavankumar Kondeti
2010-12-16 15:34 ` Alan Stern
2010-12-16 15:53 ` Pavan Kondeti
2010-12-16 11:09 ` [RFC v2 2/4] USB: gadget: OTG supplement revision " Pavankumar Kondeti
2010-12-16 11:09 ` [RFC v2 3/4] USB: EHCI: Notify HCD about HNP enabled port suspend Pavankumar Kondeti
2010-12-16 11:09 ` [RFC v2 4/4] USB: Eliminate delays involved in root hub initialization during HNP Pavankumar Kondeti
2010-12-16 12:39 ` Sergei Shtylyov
2010-12-16 13:07 ` Felipe Balbi
2010-12-16 13:13 ` Pavan Kondeti [this message]
2010-12-16 13:17 ` Sergei Shtylyov
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=4D0A106C.3030608@codeaurora.org \
--to=pkondeti@codeaurora.org \
--cc=balbi@ti.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sshtylyov@mvista.com \
/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).