From: Felipe Balbi <balbi@ti.com>
To: Roger Quadros <rogerq@ti.com>
Cc: devicetree@vger.kernel.org, tony@atomide.com,
bigeasy@linutronix.de, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, balbi@ti.com, kishon@ti.com,
bcousson@baylibre.com, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: omap3-beagle: Adapt USB OTG to generic PHY framework
Date: Thu, 10 Oct 2013 10:33:25 -0500 [thread overview]
Message-ID: <20131010153325.GH28375@radagast> (raw)
In-Reply-To: <1381142810-14541-1-git-send-email-rogerq@ti.com>
[-- Attachment #1.1: Type: text/plain, Size: 442 bytes --]
On Mon, Oct 07, 2013 at 01:46:50PM +0300, Roger Quadros wrote:
> The generic PHY framewrok expects different properties than the
> old USB PHY framework. Supply those properties.
>
> Fixes USB OTG port on beagle after the Generic PHY framework was
> merged in greg/usb-next. [1]
>
> [1] - https://lkml.org/lkml/2013/9/27/581
>
> Signed-off-by: Roger Quadros <rogerq@ti.com>
Acked-by: Felipe Balbi <balbi@ti.com>
--
balbi
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2013-10-10 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 10:46 [PATCH] ARM: dts: omap3-beagle: Adapt USB OTG to generic PHY framework Roger Quadros
2013-10-10 15:33 ` Felipe Balbi [this message]
[not found] ` <1381142810-14541-1-git-send-email-rogerq-l0cyMroinI0@public.gmane.org>
2013-10-18 12:00 ` Roger Quadros
[not found] ` <526122C4.4090702-l0cyMroinI0@public.gmane.org>
2013-10-18 15:59 ` Benoit Cousson
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=20131010153325.GH28375@radagast \
--to=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=rogerq@ti.com \
--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 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).