From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Masami Hiramatsu <masami.hiramatsu@linaro.org>,
Jassi Brar <jaswinder.singh@linaro.org>,
linux-kernel@vger.kernel.org,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/6] phy: socionext: Add some improvements and legacy SoC support
Date: Wed, 15 Jan 2020 11:13:35 +0900 [thread overview]
Message-ID: <20200115111334.FD2E.4A936039@socionext.com> (raw)
In-Reply-To: <1573035979-32200-1-git-send-email-hayashi.kunihiko@socionext.com>
Hi,
Gentle ping.
Is there any comments about this series?
Thank you,
On Wed, 6 Nov 2019 19:26:13 +0900 <hayashi.kunihiko@socionext.com> wrote:
> This series adds some improvements to PHY interface drivers, and adds legacy SoC
> support that needs to manage gio clock and reset.
>
> Kunihiko Hayashi (6):
> phy: socionext: Use devm_platform_ioremap_resource()
> dt-bindings: phy: socionext: Add Pro5 support and remove Pro4 from
> usb3-hsphy
> phy: uniphier-usb3ss: Add Pro5 support
> phy: uniphier-usb3hs: Add legacy SoC support for Pro5
> phy: uniphier-usb3hs: Change Rx sync mode to avoid communication
> failure
> phy: uniphier-pcie: Add legacy SoC support for Pro5
>
> .../devicetree/bindings/phy/uniphier-pcie-phy.txt | 13 ++-
> .../bindings/phy/uniphier-usb3-hsphy.txt | 6 +-
> .../bindings/phy/uniphier-usb3-ssphy.txt | 5 +-
> drivers/phy/socionext/phy-uniphier-pcie.c | 87 ++++++++++++++++----
> drivers/phy/socionext/phy-uniphier-usb3hs.c | 92 ++++++++++++++++------
> drivers/phy/socionext/phy-uniphier-usb3ss.c | 8 +-
> 6 files changed, 163 insertions(+), 48 deletions(-)
>
> --
> 2.7.4
---
Best Regards,
Kunihiko Hayashi
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-01-15 2:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 10:26 [PATCH 0/6] phy: socionext: Add some improvements and legacy SoC support Kunihiko Hayashi
2019-11-06 10:26 ` [PATCH 1/6] phy: socionext: Use devm_platform_ioremap_resource() Kunihiko Hayashi
2019-11-06 10:26 ` [PATCH 2/6] dt-bindings: phy: socionext: Add Pro5 support and remove Pro4 from usb3-hsphy Kunihiko Hayashi
2019-11-07 0:52 ` Rob Herring
2019-11-06 10:26 ` [PATCH 3/6] phy: uniphier-usb3ss: Add Pro5 support Kunihiko Hayashi
2019-11-06 10:26 ` [PATCH 4/6] phy: uniphier-usb3hs: Add legacy SoC support for Pro5 Kunihiko Hayashi
2019-11-06 10:26 ` [PATCH 5/6] phy: uniphier-usb3hs: Change Rx sync mode to avoid communication failure Kunihiko Hayashi
2019-11-06 10:26 ` [PATCH 6/6] phy: uniphier-pcie: Add legacy SoC support for Pro5 Kunihiko Hayashi
2019-12-20 12:00 ` [PATCH 0/6] phy: socionext: Add some improvements and legacy SoC support Kunihiko Hayashi
2020-01-15 2:13 ` Kunihiko Hayashi [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=20200115111334.FD2E.4A936039@socionext.com \
--to=hayashi.kunihiko@socionext.com \
--cc=devicetree@vger.kernel.org \
--cc=jaswinder.singh@linaro.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=masami.hiramatsu@linaro.org \
--cc=robh+dt@kernel.org \
--cc=yamada.masahiro@socionext.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).