From: kishon@ti.com (Kishon Vijay Abraham I)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 0/5] phy: bcm-ns-usb3: add MDIO driver
Date: Fri, 16 Jun 2017 12:06:21 +0530 [thread overview]
Message-ID: <a28bd799-abc2-8f4e-c3db-b9f82f35295a@ti.com> (raw)
In-Reply-To: <20170608200428.9187-1-zajec5@gmail.com>
On Friday 09 June 2017 01:34 AM, Rafa? Mi?ecki wrote:
> From: Rafa? Mi?ecki <rafal@milecki.pl>
>
> As explained in the commit 9200c6f177638 ("Revert "phy: Add USB3 PHY support
> for Broadcom NSP SoC"") this module should be modified to use MDIO bus as
> this is how PHY is really attached.
>
> This should allow reusing this driver on NSP and any other platform with
> MDIO bus and this particular PHY.
can you run checkpatch and fix all warnings in this series?
Thanks
Kishon
>
> V2: Rebase and update 4/5 and 5/5.
>
> Rafa? Mi?ecki (5):
> phy: bcm-ns-usb3: always wait for idle after writing to the PHY reg
> phy: bcm-ns-usb3: use pointer for PHY writing function
> phy: bcm-ns-usb3: enable MDIO in the platform specific code
> dt-bindings: phy: Modify Broadcom NS USB 3.0 PHY binding to use MDIO
> phy: bcm-ns-usb3: add MDIO driver using proper bus layer
>
> .../devicetree/bindings/phy/bcm-ns-usb3-phy.txt | 27 ++-
> drivers/phy/broadcom/Kconfig | 1 +
> drivers/phy/broadcom/phy-bcm-ns-usb3.c | 230 +++++++++++++++------
> 3 files changed, 186 insertions(+), 72 deletions(-)
>
next prev parent reply other threads:[~2017-06-16 6:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 13:29 [PATCH for 4.13 0/5] phy: bcm-ns-usb3: add MDIO driver Rafał Miłecki
2017-05-11 13:29 ` [PATCH 1/5] phy: bcm-ns-usb3: always wait for idle after writing to the PHY reg Rafał Miłecki
2017-05-11 13:29 ` [PATCH 2/5] phy: bcm-ns-usb3: use pointer for PHY writing function Rafał Miłecki
2017-05-11 13:29 ` [PATCH 3/5] phy: bcm-ns-usb3: enable MDIO in the platform specific code Rafał Miłecki
2017-05-11 13:29 ` [PATCH 4/5] dt-bindings: phy: Modify Broadcom NS USB 3.0 PHY binding to use MDIO Rafał Miłecki
2017-05-13 0:19 ` Rob Herring
2017-05-11 13:29 ` [PATCH 5/5] phy: bcm-ns-usb3: add MDIO driver using proper bus layer Rafał Miłecki
2017-05-11 16:29 ` Florian Fainelli
2017-06-16 6:04 ` Kishon Vijay Abraham I
2017-06-16 6:11 ` Rafał Miłecki
2017-06-16 6:31 ` Kishon Vijay Abraham I
2017-06-08 20:04 ` [PATCH V2 0/5] phy: bcm-ns-usb3: add MDIO driver Rafał Miłecki
2017-06-08 20:04 ` [PATCH V2 1/5] phy: bcm-ns-usb3: always wait for idle after writing to the PHY reg Rafał Miłecki
2017-06-08 20:04 ` [PATCH V2 2/5] phy: bcm-ns-usb3: use pointer for PHY writing function Rafał Miłecki
2017-06-08 20:04 ` [PATCH V2 3/5] phy: bcm-ns-usb3: enable MDIO in the platform specific code Rafał Miłecki
2017-06-08 20:04 ` [PATCH V2 4/5] dt-bindings: phy: Modify Broadcom NS USB 3.0 PHY binding to use MDIO Rafał Miłecki
2017-06-14 15:26 ` Rob Herring
2017-06-08 20:04 ` [PATCH V2 5/5] phy: bcm-ns-usb3: add MDIO driver using proper bus layer Rafał Miłecki
2017-06-16 6:36 ` Kishon Vijay Abraham I [this message]
2017-06-16 7:14 ` [PATCH V2 0/5] phy: bcm-ns-usb3: add MDIO driver Rafał Miłecki
2017-06-16 7:52 ` Kishon Vijay Abraham I
2017-06-16 7:53 ` Kishon Vijay Abraham I
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=a28bd799-abc2-8f4e-c3db-b9f82f35295a@ti.com \
--to=kishon@ti.com \
--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 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).