linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: quentin.schulz@bootlin.com
Cc: alexandre.belloni@bootlin.com, ralf@linux-mips.org,
	paul.burton@mips.com, jhogan@kernel.org, robh+dt@kernel.org,
	mark.rutland@arm.com, kishon@ti.com, andrew@lunn.ch,
	f.fainelli@gmail.com, allan.nielsen@microchip.com,
	linux-mips@linux-mips.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	thomas.petazzoni@bootlin.com
Subject: Re: [PATCH net-next v4 00/11] mscc: ocelot: add support for SerDes muxing configuration
Date: Fri, 05 Oct 2018 14:39:24 -0700 (PDT)	[thread overview]
Message-ID: <20181005.143924.1849227852256176976.davem@davemloft.net> (raw)
In-Reply-To: <20181004122208.32272-1-quentin.schulz@bootlin.com>

From: Quentin Schulz <quentin.schulz@bootlin.com>
Date: Thu,  4 Oct 2018 14:21:57 +0200

> The Ocelot switch has currently an hardcoded SerDes muxing that suits only
> a particular use case. Any other board setup will fail to work.
> 
> To prepare for upcoming boards' support that do not have the same muxing,
> create a PHY driver that will handle all possible cases.
> 
> A SerDes can work in SGMII, QSGMII or PCIe and is also muxed to use a
> given port depending on the selected mode or board design.
> 
> The SerDes configuration is in the middle of an address space (HSIO) that
> is used to configure some parts in the MAC controller driver, that is why
> we need to use a syscon so that we can write to the same address space from
> different drivers safely using regmap.
> 
> This breaks backward compatibility but it's fine because there's only one
> board at the moment that is using what's modified in this patch series.
> This will break git bisect.
> 
> Even though this patch series is about SerDes __muxing__ configuration, the
> DT node is named serdes for the simple reason that I couldn't find any
> mention to SerDes anywhere else from the address space handled by this
> driver.

Series applied to net-next, thanks.

      parent reply	other threads:[~2018-10-05 21:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-04 12:21 [PATCH net-next v4 00/11] mscc: ocelot: add support for SerDes muxing configuration Quentin Schulz
2018-10-04 12:21 ` [PATCH net-next v4 01/11] MIPS: mscc: ocelot: make HSIO registers address range a syscon Quentin Schulz
2018-10-04 12:21 ` [PATCH net-next v4 02/11] dt-bindings: net: ocelot: remove hsio from the list of register address spaces Quentin Schulz
2018-10-04 12:22 ` [PATCH net-next v4 03/11] net: mscc: ocelot: get HSIO regmap from syscon Quentin Schulz
2018-10-04 12:22 ` [PATCH net-next v4 04/11] net: mscc: ocelot: move the HSIO header to include/soc Quentin Schulz
2018-10-04 12:22 ` [PATCH net-next v4 05/11] net: mscc: ocelot: simplify register access for PLL5 configuration Quentin Schulz
2018-10-04 12:22 ` [PATCH net-next v4 06/11] phy: add QSGMII and PCIE modes Quentin Schulz
2018-10-04 12:22 ` [PATCH net-next v4 07/11] dt-bindings: phy: add DT binding for Microsemi Ocelot SerDes muxing Quentin Schulz
2018-10-04 12:22 ` [PATCH net-next v4 08/11] MIPS: mscc: ocelot: add SerDes mux DT node Quentin Schulz
2018-10-04 12:22 ` [PATCH net-next v4 09/11] dt-bindings: add constants for Microsemi Ocelot SerDes driver Quentin Schulz
2018-10-04 20:15   ` Florian Fainelli
2018-10-04 12:22 ` [PATCH net-next v4 10/11] phy: add driver for Microsemi Ocelot SerDes muxing Quentin Schulz
2018-10-04 12:22 ` [PATCH net-next v4 11/11] net: mscc: ocelot: make use of SerDes PHYs for handling their configuration Quentin Schulz
2018-10-04 20:16   ` Florian Fainelli
2018-10-05 21:39 ` David Miller [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=20181005.143924.1849227852256176976.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=alexandre.belloni@bootlin.com \
    --cc=allan.nielsen@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=jhogan@kernel.org \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mark.rutland@arm.com \
    --cc=netdev@vger.kernel.org \
    --cc=paul.burton@mips.com \
    --cc=quentin.schulz@bootlin.com \
    --cc=ralf@linux-mips.org \
    --cc=robh+dt@kernel.org \
    --cc=thomas.petazzoni@bootlin.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).