From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] phy: driver for Conexant Digicolor internal USB PHY
Date: Sat, 28 Mar 2015 16:33:02 +0100 [thread overview]
Message-ID: <201503281633.02801.marex@denx.de> (raw)
In-Reply-To: <4a9ceb0a240d49dd6a68d50c78f85d310d4b932f.1427430989.git.baruch@tkos.co.il>
On Friday, March 27, 2015 at 05:36:29 AM, Baruch Siach wrote:
> Add a driver for the USB PHY on the Conexant CX92755 SoC, from the
> Digicolor series of SoCs. The PHY is connected to the on-chip chipidea
> usb2 host.
>
> The hardware is somewhat similar to the phy-mxs-usb.c usb_phy, but it is
> different enough to merit its own driver. Also, this driver uses the
> generic phy infrastructure.
Hi,
the register set looks very similar to MXS one indeed. How is it different
please ?
The driver looks OK.
Best regards,
Marek Vasut
WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marex@denx.de>
To: Baruch Siach <baruch@tkos.co.il>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Richard Zhao <richard.zhao@freescale.com>
Subject: Re: [PATCH 2/2] phy: driver for Conexant Digicolor internal USB PHY
Date: Sat, 28 Mar 2015 16:33:02 +0100 [thread overview]
Message-ID: <201503281633.02801.marex@denx.de> (raw)
In-Reply-To: <4a9ceb0a240d49dd6a68d50c78f85d310d4b932f.1427430989.git.baruch@tkos.co.il>
On Friday, March 27, 2015 at 05:36:29 AM, Baruch Siach wrote:
> Add a driver for the USB PHY on the Conexant CX92755 SoC, from the
> Digicolor series of SoCs. The PHY is connected to the on-chip chipidea
> usb2 host.
>
> The hardware is somewhat similar to the phy-mxs-usb.c usb_phy, but it is
> different enough to merit its own driver. Also, this driver uses the
> generic phy infrastructure.
Hi,
the register set looks very similar to MXS one indeed. How is it different
please ?
The driver looks OK.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-03-28 15:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 4:36 [PATCH 1/2] phy: dt-binding: document Conexant Digicolor USB PHY Baruch Siach
2015-03-27 4:36 ` Baruch Siach
2015-03-27 4:36 ` [PATCH 2/2] phy: driver for Conexant Digicolor internal " Baruch Siach
2015-03-27 4:36 ` Baruch Siach
2015-03-28 15:33 ` Marek Vasut [this message]
2015-03-28 15:33 ` Marek Vasut
2015-03-31 11:34 ` Baruch Siach
2015-03-31 11:34 ` Baruch Siach
2015-03-31 15:26 ` Kishon Vijay Abraham I
2015-03-31 15:26 ` Kishon Vijay Abraham I
2015-03-31 15:26 ` Kishon Vijay Abraham I
2015-03-31 15:41 ` Baruch Siach
2015-03-31 15:41 ` Baruch Siach
2015-03-31 15:41 ` Baruch Siach
2015-03-31 15:46 ` Kishon Vijay Abraham I
2015-03-31 15:46 ` Kishon Vijay Abraham I
2015-03-31 15:46 ` Kishon Vijay Abraham I
2015-03-31 18:42 ` Baruch Siach
2015-03-31 18:42 ` Baruch Siach
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=201503281633.02801.marex@denx.de \
--to=marex@denx.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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.