From: Shawn Lin <shawn.lin@rock-chips.com>
To: Kishon Vijay Abraham I <kishon@ti.com>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: shawn.lin@rock-chips.com, Rob Herring <robh@kernel.org>,
Brian Norris <briannorris@chromium.org>,
Heiko Stuebner <heiko@sntech.de>,
linux-pci@vger.kernel.org, Jeffy Chen <jeffy.chen@rock-chips.com>,
linux-rockchip@lists.infradead.org
Subject: Re: [RFC PATCH v4 3/7] phy: rockcip-pcie: reconstruct driver to support per-lane PHYs
Date: Wed, 19 Jul 2017 15:54:29 +0800 [thread overview]
Message-ID: <3e4f8aeb-d4ea-5a80-54a9-43cc6b3488c2@rock-chips.com> (raw)
In-Reply-To: <e1afec0e-ba1b-4721-4ddb-c6ef3b85e65f@ti.com>
Hi Kishon,
On 2017/7/19 15:50, Kishon Vijay Abraham I wrote:
>
>
> On Wednesday 19 July 2017 12:52 PM, Shawn Lin wrote:
>> This patch reconstructs the whole driver to support per-lane
>> PHYs. Note that we could also support the legacy PHY if you
>> don't provide argument to our of_xlate.
>>
>> Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
>> Reviewed-by: Brian Norris <briannorris@chromium.org>
>> Tested-by: Jeffy Chen <jeffy.chen@rock-chips.com>
>
> This design looks good! I'll queue this once I start queuing 4.14.
>
Great! Thanks. :)
> Thanks
> Kishon
>
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip
>
>
>
next prev parent reply other threads:[~2017-07-19 7:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 7:22 [RFC PATCH v4 0/7] Reconstruct rockchip's PCIe and PCIe-PHY driver for per-lane PHY model Shawn Lin
2017-07-19 7:22 ` [RFC PATCH v4 1/7] PCI: rockchip: split out rockchip_pcie_get_phys Shawn Lin
[not found] ` <1500448979-93067-2-git-send-email-shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-07-19 7:47 ` Kishon Vijay Abraham I
2017-07-19 7:22 ` [RFC PATCH v4 2/7] PCI: rockchip: introduce per-lanes PHYs support Shawn Lin
[not found] ` <1500448979-93067-3-git-send-email-shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-07-19 7:48 ` Kishon Vijay Abraham I
2017-07-19 7:22 ` [RFC PATCH v4 3/7] phy: rockcip-pcie: reconstruct driver to support per-lane PHYs Shawn Lin
[not found] ` <1500448979-93067-4-git-send-email-shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-07-19 7:50 ` Kishon Vijay Abraham I
2017-07-19 7:54 ` Shawn Lin [this message]
2017-07-19 8:08 ` Kishon Vijay Abraham I
2017-07-19 9:36 ` Shawn Lin
2017-07-19 9:37 ` Kishon Vijay Abraham I
2017-07-19 7:22 ` [RFC PATCH v4 4/7] PCI: rockchip: idle the inactive PHY(s) Shawn Lin
[not found] ` <1500448979-93067-5-git-send-email-shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-07-19 7:50 ` Kishon Vijay Abraham I
2017-07-19 7:27 ` [RFC PATCH v4 5/7] arm64: dts: rockchip: convert PCIe to use per-lane PHYs for rk3339 Shawn Lin
2017-07-19 7:27 ` [RFC PATCH v4 6/7] dt-bindings: PCI: rockchip: convert to use per-lane PHY model Shawn Lin
2017-07-19 7:27 ` [RFC PATCH v4 7/7] dt-bindings: phy: convert to use per-lane Rockchip PCIe PHY Shawn Lin
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=3e4f8aeb-d4ea-5a80-54a9-43cc6b3488c2@rock-chips.com \
--to=shawn.lin@rock-chips.com \
--cc=bhelgaas@google.com \
--cc=briannorris@chromium.org \
--cc=heiko@sntech.de \
--cc=jeffy.chen@rock-chips.com \
--cc=kishon@ti.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.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