From: Kishon Vijay Abraham I <kishon@ti.com>
To: Roger Quadros <rogerq@ti.com>
Cc: robh+dt@kernel.org, nsekhar@ti.com, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/4] phy: ti: Add AM654 USB2 support
Date: Wed, 16 Jan 2019 14:02:15 +0530 [thread overview]
Message-ID: <d842caba-191c-b10e-14b4-60a749d8dc81@ti.com> (raw)
In-Reply-To: <5C35BB6D.2030509@ti.com>
On 09/01/19 2:44 PM, Roger Quadros wrote:
> Hi Kishon,
>
> On 05/12/18 17:03, Roger Quadros wrote:
>> Hi Kishon,
>>
>> This series extends omap-usb2 PHY driver to be used
>> for AM654 USB2 PHY.
>
> Any comments on this series? If it looks fine, could you please
> queue this for -next. Thanks.
Sorry for the delay. Merged now to -next.
Thanks
Kishon
>
> cheers,
> -roger
>
>>
>> cheers,
>> -roger
>>
>> Roger Quadros (4):
>> phy: ti: usb2: Fix logic on -EPROBE_DEFER
>> phy: ti: Don't depend on OMAP_OCP2SCP
>> dt-bindings: phy: ti: Add support for AM654x USB2 PHY
>> phy: ti: usb2: Add support for AM654 USB2 PHY
>>
>> Documentation/devicetree/bindings/phy/ti-phy.txt | 1 +
>> drivers/phy/ti/Kconfig | 6 +-
>> drivers/phy/ti/phy-omap-usb2.c | 105 ++++++++++++++---------
>> 3 files changed, 67 insertions(+), 45 deletions(-)
>>
>
prev parent reply other threads:[~2019-01-16 8:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 15:03 [PATCH 0/4] phy: ti: Add AM654 USB2 support Roger Quadros
2018-12-05 15:03 ` [PATCH 1/4] phy: ti: usb2: Fix logic on -EPROBE_DEFER Roger Quadros
2018-12-14 9:41 ` Roger Quadros
2018-12-14 17:23 ` Tony Lindgren
2018-12-05 15:03 ` [PATCH 2/4] phy: ti: Don't depend on OMAP_OCP2SCP Roger Quadros
2018-12-05 15:03 ` [PATCH 3/4] dt-bindings: phy: ti: Add support for AM654x USB2 PHY Roger Quadros
2018-12-19 20:37 ` Rob Herring
2018-12-05 15:03 ` [PATCH 4/4] phy: ti: usb2: Add support for AM654 " Roger Quadros
2019-01-09 9:14 ` [PATCH 0/4] phy: ti: Add AM654 USB2 support Roger Quadros
2019-01-16 8:32 ` Kishon Vijay Abraham I [this message]
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=d842caba-191c-b10e-14b4-60a749d8dc81@ti.com \
--to=kishon@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=rogerq@ti.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).