From: Igor Grinberg <grinberg@compulab.co.il>
To: balbi@ti.com
Cc: Tony Lindgren <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 3/5] omap3: cm-t3517: add support for usb host.
Date: Mon, 20 Sep 2010 16:46:34 +0200 [thread overview]
Message-ID: <4C9773CA.4010102@compulab.co.il> (raw)
In-Reply-To: <20100920063913.GB32493@legolas.emea.dhcp.ti.com>
On 09/20/10 08:39, Felipe Balbi wrote:
> On Thu, Sep 16, 2010 at 04:12:06AM -0500, Igor Grinberg wrote:
>> Yes it will, but even if the hub reset gpio is for some reason unavailable,
>> we don't want to disable ehci completely...
>
> then you should set the gpio to an invalid number, otherwise you might
> cause lots of WARN() to appear due to fiddling with unrequested gpio.
What gpio should be set to invalid number?
It is a reset gpio for usb _hub_ and it has nothing to do with ehci.
Can you please, explain the case when I might cause those WARN()'s?
--
Regards,
Igor.
WARNING: multiple messages have this Message-ID (diff)
From: grinberg@compulab.co.il (Igor Grinberg)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] omap3: cm-t3517: add support for usb host.
Date: Mon, 20 Sep 2010 16:46:34 +0200 [thread overview]
Message-ID: <4C9773CA.4010102@compulab.co.il> (raw)
In-Reply-To: <20100920063913.GB32493@legolas.emea.dhcp.ti.com>
On 09/20/10 08:39, Felipe Balbi wrote:
> On Thu, Sep 16, 2010 at 04:12:06AM -0500, Igor Grinberg wrote:
>> Yes it will, but even if the hub reset gpio is for some reason unavailable,
>> we don't want to disable ehci completely...
>
> then you should set the gpio to an invalid number, otherwise you might
> cause lots of WARN() to appear due to fiddling with unrequested gpio.
What gpio should be set to invalid number?
It is a reset gpio for usb _hub_ and it has nothing to do with ehci.
Can you please, explain the case when I might cause those WARN()'s?
--
Regards,
Igor.
next prev parent reply other threads:[~2010-09-20 14:46 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 8:54 [PATCH 0/5] Support for CompuLab CM-T3517 modules Igor Grinberg
2010-09-16 8:54 ` Igor Grinberg
2010-09-16 8:54 ` [PATCH 1/5] omap3: Introduce CompuLab CM-T3517 module Igor Grinberg
2010-09-16 8:54 ` Igor Grinberg
2010-09-16 17:53 ` Tony Lindgren
2010-09-16 17:53 ` Tony Lindgren
2010-09-19 8:58 ` Igor Grinberg
2010-09-19 8:58 ` Igor Grinberg
2010-09-16 8:54 ` [PATCH 2/5] omap3: cm-t3517: add support for v3020 rtc Igor Grinberg
2010-09-16 8:54 ` Igor Grinberg
2010-09-16 8:54 ` [PATCH 3/5] omap3: cm-t3517: add support for usb host Igor Grinberg
2010-09-16 8:54 ` Igor Grinberg
2010-09-16 9:00 ` Felipe Balbi
2010-09-16 9:00 ` Felipe Balbi
2010-09-16 9:12 ` Igor Grinberg
2010-09-16 9:12 ` Igor Grinberg
2010-09-16 17:48 ` Tony Lindgren
2010-09-16 17:48 ` Tony Lindgren
2010-09-19 9:00 ` Igor Grinberg
2010-09-19 9:00 ` Igor Grinberg
2010-09-20 6:39 ` Felipe Balbi
2010-09-20 6:39 ` Felipe Balbi
2010-09-20 14:46 ` Igor Grinberg [this message]
2010-09-20 14:46 ` Igor Grinberg
2010-09-21 7:07 ` Felipe Balbi
2010-09-21 7:07 ` Felipe Balbi
2010-09-16 8:54 ` [PATCH 4/5] omap3: cm-t3517: add support for NAND flash Igor Grinberg
2010-09-16 8:54 ` Igor Grinberg
2010-09-16 8:54 ` [PATCH 5/5] omap3: cm-t3517: add support for TI HECC Igor Grinberg
2010-09-16 8:54 ` Igor Grinberg
-- strict thread matches above, loose matches on Subject: below --
2010-09-21 16:03 [PATCH 0/5] Support for CompuLab CM-T3517 modules Igor Grinberg
2010-09-21 16:03 ` [PATCH 3/5] omap3: cm-t3517: add support for usb host Igor Grinberg
2010-09-21 16:03 ` Igor Grinberg
2010-09-21 16:26 ` Gadiyar, Anand
2010-09-21 16:26 ` Gadiyar, Anand
2010-09-22 8:24 ` Igor Grinberg
2010-09-22 8:24 ` Igor Grinberg
2010-09-27 22:28 ` Tony Lindgren
2010-09-27 22:28 ` Tony Lindgren
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=4C9773CA.4010102@compulab.co.il \
--to=grinberg@compulab.co.il \
--cc=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.