devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Murali Karicheri <m-karicheri2@ti.com>
To: WingMan Kwok <w-kwok2@ti.com>,
	robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
	kishon@ti.com, rogerq@ti.com, bhelgaas@google.com,
	ssantosh@kernel.org, linux@arm.linux.org.uk,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/2] Common SerDes driver for TI's Keystone Platforms
Date: Thu, 22 Oct 2015 11:05:26 -0400	[thread overview]
Message-ID: <5628FB36.4010303@ti.com> (raw)
In-Reply-To: <1445432201-16007-1-git-send-email-w-kwok2@ti.com>

On 10/21/2015 08:56 AM, WingMan Kwok wrote:
> On TI's Keystone platforms, several peripherals such as the
> gbe ethernet switch, 10gbe ethernet switch and PCIe controller
> require the use of a SerDes for converting SoC parallel data into
> serialized data that can be output over a high-speed electrical
> interface, and also converting high-speed serial input data
> into parallel data that can be processed by the SoC.  The
> SerDeses used by those peripherals, though they may be different,
> are largely similar in functionality and setup.
>
> This patch series provides a SerDes phy driver implementation that can be
> used by the above mentioned peripheral drivers to configure their
> respective SerDeses.
>
> As an example of the using the SerDes driver, this patch series also
> updates the Keystone PCIe host driver to enable and use its SerDes block.
>
> References:
> [1] KeyStone II Architecture Serializer/Deserializer (SerDes) User's Guide
>      (http://www.ti.com/lit/ug/spruho3a/spruho3a.pdf)
>
> v3:
> 	- addresses the following review comments
> 		1. https://lkml.org/lkml/2015/10/19/756
> 			-- included sizes.h
> 		2. https://lkml.org/lkml/2015/10/19/781
> 			-- updated base on Fengguang Wu's suggestions.
> 		3. https://lkml.org/lkml/2015/10/15/896
> 			-- clarified here https://lkml.org/lkml/2015/10/20/512
> 			-- nothing to do.
>
> v2:
> 	- addresses the following review comments on v1:
> 		1. https://lkml.org/lkml/2015/10/15/896
> 			-- this does not address the question:
> 			   "The current code does not do this when compiled,
> 			    which might be a problem for distributors.
> 			    Can you clarify the license?"
> 			-- the question is still under discussion here:
> 			   https://lkml.org/lkml/2015/10/19/471
> 		2. https://lkml.org/lkml/2015/10/15/895
>
> v1:
> 	- addresses the following review comments
> 		1. https://lkml.org/lkml/2015/10/13/803
> 		2. https://lkml.org/lkml/2015/10/14/613
> 		3. https://lkml.org/lkml/2015/10/13/818
>
> 	- An update to PCIe dts bindings to enable the PCIe SerDes is
> 	  submitted in a separate patch.
>
> WingMan Kwok (2):
>    phy: keystone: serdes driver for gbe 10gbe and pcie
>    PCI: keystone: update to use generic keystone serdes driver
>
>   Documentation/devicetree/bindings/phy/ti-phy.txt |  239 +++
>   drivers/pci/host/pci-keystone.c                  |   24 +-
>   drivers/pci/host/pci-keystone.h                  |    1 +
>   drivers/phy/Kconfig                              |    8 +
>   drivers/phy/Makefile                             |    1 +
>   drivers/phy/phy-keystone-serdes.c                | 2366 ++++++++++++++++++++++
>   6 files changed, 2629 insertions(+), 10 deletions(-)
>   create mode 100644 drivers/phy/phy-keystone-serdes.c
>
Kishon, Bjorn

Who will pick this up? Do we have time to get this in 4.4?
-- 
Murali Karicheri
Linux Kernel, Keystone

  parent reply	other threads:[~2015-10-22 15:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 12:56 [PATCH v3 0/2] Common SerDes driver for TI's Keystone Platforms WingMan Kwok
2015-10-21 12:56 ` [PATCH v3 1/2] phy: keystone: serdes driver for gbe 10gbe and pcie WingMan Kwok
2015-10-21 22:55   ` Rob Herring
2015-10-22 14:22     ` Kwok, WingMan
2015-10-21 12:56 ` [PATCH v3 2/2] PCI: keystone: update to use generic keystone serdes driver WingMan Kwok
2015-10-22 15:05 ` Murali Karicheri [this message]
     [not found]   ` <5628FB36.4010303-l0cyMroinI0@public.gmane.org>
2015-10-22 17:48     ` [PATCH v3 0/2] Common SerDes driver for TI's Keystone Platforms Russell King - ARM Linux
2015-10-22 21:56       ` Murali Karicheri
2015-10-22 22:14         ` Murali Karicheri
     [not found]         ` <56295B9E.9030201-l0cyMroinI0@public.gmane.org>
2015-10-22 22:27           ` Loc Ho
2015-10-23  9:17             ` Arnd Bergmann
2015-10-23 14:25               ` Murali Karicheri
2015-10-23 14:46               ` Russell King - ARM Linux
2015-10-23 15:41                 ` Arnd Bergmann
     [not found]                 ` <20151023144631.GZ32532-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2015-10-23 18:52                   ` Kishon Vijay Abraham I
2015-10-26 22:09                     ` Murali Karicheri

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=5628FB36.4010303@ti.com \
    --to=m-karicheri2@ti.com \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=rogerq@ti.com \
    --cc=ssantosh@kernel.org \
    --cc=w-kwok2@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).