From: Roger Quadros <rogerq@ti.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>, kishon@ti.com
Cc: bcousson@baylibre.com, pavel@ucw.cz, aaro.koskinen@iki.fi,
marek@goldelico.com, balbi@ti.com, tony@atomide.com,
linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] ARM: dts: omap3: Adapt USB OTG to generic PHY framework
Date: Mon, 7 Oct 2013 16:49:41 +0300 [thread overview]
Message-ID: <5252BBF5.1060406@ti.com> (raw)
In-Reply-To: <5252B9C7.5040109@linutronix.de>
On 10/07/2013 04:40 PM, Sebastian Andrzej Siewior wrote:
> On 10/07/2013 03:28 PM, Roger Quadros wrote:
>> The generic PHY framewrok expects different properties than the
>> old USB PHY framework. Supply those properties.
>>
>> Fixes USB OTG port on GAT04 and N900 after the Generic PHY framework was
>> merged in greg/usb-next. [1]
>
> Would it be much pain (and do we want this at all) to add a fallback
> into the kernel or at least a printk pointing out to update the .dts
> for two releases or so? So the user does not need to spent hours to
> figure out why it suddenly stopped working.
>
I agree with you.
Also, figuring out which kernel configs to enable for
USB OTG to work on OMAP is a pain in itself to the user.
cheers,
-roger
WARNING: multiple messages have this Message-ID (diff)
From: rogerq@ti.com (Roger Quadros)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: dts: omap3: Adapt USB OTG to generic PHY framework
Date: Mon, 7 Oct 2013 16:49:41 +0300 [thread overview]
Message-ID: <5252BBF5.1060406@ti.com> (raw)
In-Reply-To: <5252B9C7.5040109@linutronix.de>
On 10/07/2013 04:40 PM, Sebastian Andrzej Siewior wrote:
> On 10/07/2013 03:28 PM, Roger Quadros wrote:
>> The generic PHY framewrok expects different properties than the
>> old USB PHY framework. Supply those properties.
>>
>> Fixes USB OTG port on GAT04 and N900 after the Generic PHY framework was
>> merged in greg/usb-next. [1]
>
> Would it be much pain (and do we want this at all) to add a fallback
> into the kernel or at least a printk pointing out to update the .dts
> for two releases or so? So the user does not need to spent hours to
> figure out why it suddenly stopped working.
>
I agree with you.
Also, figuring out which kernel configs to enable for
USB OTG to work on OMAP is a pain in itself to the user.
cheers,
-roger
WARNING: multiple messages have this Message-ID (diff)
From: Roger Quadros <rogerq@ti.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>, <kishon@ti.com>
Cc: <bcousson@baylibre.com>, <pavel@ucw.cz>, <aaro.koskinen@iki.fi>,
<marek@goldelico.com>, <balbi@ti.com>, <tony@atomide.com>,
<linux-usb@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] ARM: dts: omap3: Adapt USB OTG to generic PHY framework
Date: Mon, 7 Oct 2013 16:49:41 +0300 [thread overview]
Message-ID: <5252BBF5.1060406@ti.com> (raw)
In-Reply-To: <5252B9C7.5040109@linutronix.de>
On 10/07/2013 04:40 PM, Sebastian Andrzej Siewior wrote:
> On 10/07/2013 03:28 PM, Roger Quadros wrote:
>> The generic PHY framewrok expects different properties than the
>> old USB PHY framework. Supply those properties.
>>
>> Fixes USB OTG port on GAT04 and N900 after the Generic PHY framework was
>> merged in greg/usb-next. [1]
>
> Would it be much pain (and do we want this at all) to add a fallback
> into the kernel or at least a printk pointing out to update the .dts
> for two releases or so? So the user does not need to spent hours to
> figure out why it suddenly stopped working.
>
I agree with you.
Also, figuring out which kernel configs to enable for
USB OTG to work on OMAP is a pain in itself to the user.
cheers,
-roger
next prev parent reply other threads:[~2013-10-07 13:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 13:28 [PATCH 0/1] Possibly fix USB OTG on GTA04 and N900 Roger Quadros
2013-10-07 13:28 ` Roger Quadros
2013-10-07 13:28 ` Roger Quadros
[not found] ` <1381152493-28055-1-git-send-email-rogerq-l0cyMroinI0@public.gmane.org>
2013-10-07 13:28 ` [PATCH 1/1] ARM: dts: omap3: Adapt USB OTG to generic PHY framework Roger Quadros
2013-10-07 13:28 ` Roger Quadros
2013-10-07 13:28 ` Roger Quadros
2013-10-07 13:40 ` Sebastian Andrzej Siewior
2013-10-07 13:40 ` Sebastian Andrzej Siewior
2013-10-07 13:49 ` Roger Quadros [this message]
2013-10-07 13:49 ` Roger Quadros
2013-10-07 13:49 ` Roger Quadros
2013-10-10 15:34 ` Felipe Balbi
2013-10-10 15:34 ` Felipe Balbi
2013-10-10 15:34 ` Felipe Balbi
2013-10-14 9:20 ` Roger Quadros
2013-10-14 9:20 ` Roger Quadros
2013-10-14 9:20 ` Roger Quadros
2013-10-15 6:53 ` Benoit Cousson
2013-10-15 6:53 ` Benoit Cousson
2013-10-08 16:04 ` [PATCH 0/1] Possibly fix USB OTG on GTA04 and N900 Sebastian Reichel
2013-10-08 16:04 ` Sebastian Reichel
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=5252BBF5.1060406@ti.com \
--to=rogerq@ti.com \
--cc=aaro.koskinen@iki.fi \
--cc=balbi@ti.com \
--cc=bcousson@baylibre.com \
--cc=bigeasy@linutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marek@goldelico.com \
--cc=pavel@ucw.cz \
--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.