From: Colin Foster <colin.foster@in-advantage.com> Date: 2022-09-05 16:22:09
The patch set in general is to add support for the VSC7512, and
eventually the VSC7511, VSC7513 and VSC7514 devices controlled over
SPI. Specifically this patch set enables pinctrl, serial gpio expander
access, and control of an internal and an external MDIO bus.
I have mentioned previously:
The hardware setup I'm using for development is a beaglebone black, with
jumpers from SPI0 to the microchip VSC7512 dev board. The microchip dev
board has been modified to not boot from flash, but wait for SPI. An
ethernet cable is connected from the beaglebone ethernet to port 0 of
the dev board. Network functionality will be included in a future patch set.
The device tree I'm using is included in the documentation, so I'll not
include that in this cover letter. I have exported the serial GPIOs to the
LEDs, and verified functionality via
"echo heartbeat > sys/class/leds/port0led/trigger"
/ {
vscleds {
compatible = "gpio-leds";
vscled@0 {
label = "port0led";
gpios = <&sgpio_out1 0 0 GPIO_ACTIVE_LOW>;
default-state = "off";
};
vscled@1 {
label = "port0led1";
gpios = <&sgpio_out1 0 1 GPIO_ACTIVE_LOW>;
default-state = "off";
};
[ ... ]
};
};
I verified module functionality with modprobe ocelot-soc;
modprobe pinctrl-ocelot;
modprobe pinctrl-microchip-sgpio;
I only have hardware to test the last patch, so any testers are welcome.
I've been extra cautious about the ocelot_regmap_from_resource helper
function, both before and after the last patch. I accidentally broke it
in the past and would like to avoid doing so again.
RFC history:
v16
* Add reviewed-by tags (patches 1-6)
* Utilize resource_size() (patch 8/8)
* One more round of missed includes (patch 8/8)
* Remove pinctrl-ocelot module patch, which was applied in v6.0-rc1
v15
* Add missed includes
* Fix punctuation and function convention inside comments
* Utilize spi_message_init_with_transfers() instead of
spi_message_add_tail()
* Remove unnecessary "< 0" comparisons
* Utilize HZ_PER_MHZ instead of magic numbers
v14
* Add header guards to include/linux/mfd/ocelot.h and
drivers/mfd/ocelot.h
* Lines extended to 100 chars (patch 9/9)
* Remove unnecessary "dev" and "spi" elements from ocelot_ddata
structure
* Add doc comments for ocelot_ddata
* Add Reviewed and Acked tags
* Submit to MFD instead of net-next
v13
* Suggestions from Andy for code cleanup, missed includes, forward
declarations, module names.
* Fix x86 allmodconfig build
* MFD module name is now ocelot-soc
* Add module names to Kconfig for pinctrl changes
v12
* Suggestions from Vladimir, Andy, Randy, and Rob. Thanks as always!
* Utilize dev_get_regmap to clean up interfaces
* MFD_OCELOT can be a module
v11
* Suggestions from Rob and Andy. Thanks!
* Add pinctrl module functionality back and fixing those features
* Fix aarch64 compiler error
v10
* Fix warning by removing unused function
v9
* Submitting as a PATCH instead of an RFC
* Remove switch functionality - will be a separate patch set
* Remove Kconfig tristate module options
* Another round of suggestions from Lee, Vladimir, and Andy. Many
thanks!
* Add documentation
* Update maintainers
v8
* Applied another round of suggestions from Lee and Vladimir
* Utilize regmap bus reads, which speeds bulk transfers up by an
order of magnitude
* Add two additional patches to utilize phylink_generic_validate
* Changed GPL V2 to GPL in licenses where applicable (checkpatch)
* Remove initial hsio/serdes changes from the RFC
v7
* Applied as much as I could from Lee and Vladimir's suggestions. As
always, the feedback is greatly appreciated!
* Remove "ocelot_spi" container complication
* Move internal MDIO bus from ocelot_ext to MFD, with a devicetree
change to match
* Add initial HSIO support
* Switch to IORESOURCE_REG for resource definitions
v6
* Applied several suggestions from the last RFC from Lee Jones. I
hope I didn't miss anything.
* Clean up MFD core - SPI interaction. They no longer use callbacks.
* regmaps get registered to the child device, and don't attempt to
get shared. It seems if a regmap is to be shared, that should be
solved with syscon, not dev or mfd.
v5
* Restructured to MFD
* Several commits were split out, submitted, and accepted
* pinctrl-ocelot believed to be fully functional (requires commits
from the linux-pinctrl tree)
* External MDIO bus believed to be fully functional
v4
* Functional
* Device tree fixes
* Add hooks for pinctrl-ocelot - some functionality by way of sysfs
* Add hooks for pinctrl-microsemi-sgpio - not yet fully functional
* Remove lynx_pcs interface for a generic phylink_pcs. The goal here
is to have an ocelot_pcs that will work for each configuration of
every port.
v3
* Functional
* Shared MDIO transactions routed through mdio-mscc-miim
* CPU / NPI port enabled by way of vsc7512_enable_npi_port /
felix->info->enable_npi_port
* NPI port tagging functional - Requires a CPU port driver that supports
frames of 1520 bytes. Verified with a patch to the cpsw driver
v2
* Near functional. No CPU port communication, but control over all
external ports
* Cleaned up regmap implementation from v1
v1 (accidentally named vN)
* Initial architecture. Not functional
* General concepts laid out
Colin Foster (8):
mfd: ocelot: add helper to get regmap from a resource
net: mdio: mscc-miim: add ability to be used in a non-mmio
configuration
pinctrl: ocelot: add ability to be used in a non-mmio configuration
pinctrl: microchip-sgpio: allow sgpio driver to be used as a module
pinctrl: microchip-sgpio: add ability to be used in a non-mmio
configuration
resource: add define macro for register address resources
dt-bindings: mfd: ocelot: add bindings for VSC7512
mfd: ocelot: add support for the vsc7512 chip via spi
.../devicetree/bindings/mfd/mscc,ocelot.yaml | 160 ++++++++++
MAINTAINERS | 7 +
drivers/mfd/Kconfig | 21 ++
drivers/mfd/Makefile | 3 +
drivers/mfd/ocelot-core.c | 161 ++++++++++
drivers/mfd/ocelot-spi.c | 299 ++++++++++++++++++
drivers/mfd/ocelot.h | 49 +++
drivers/net/mdio/mdio-mscc-miim.c | 42 +--
drivers/pinctrl/Kconfig | 5 +-
drivers/pinctrl/pinctrl-microchip-sgpio.c | 14 +-
drivers/pinctrl/pinctrl-ocelot.c | 16 +-
include/linux/ioport.h | 5 +
include/linux/mfd/ocelot.h | 62 ++++
13 files changed, 795 insertions(+), 49 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mfd/mscc,ocelot.yaml
create mode 100644 drivers/mfd/ocelot-core.c
create mode 100644 drivers/mfd/ocelot-spi.c
create mode 100644 drivers/mfd/ocelot.h
create mode 100644 include/linux/mfd/ocelot.h
--
2.25.1
From: Colin Foster <colin.foster@in-advantage.com> Date: 2022-09-05 16:22:03
Several ocelot-related modules are designed for MMIO / regmaps. As such,
they often use a combination of devm_platform_get_and_ioremap_resource()
and devm_regmap_init_mmio().
Operating in an MFD might be different, in that it could be memory mapped,
or it could be SPI, I2C... In these cases a fallback to use IORESOURCE_REG
instead of IORESOURCE_MEM becomes necessary.
When this happens, there's redundant logic that needs to be implemented in
every driver. In order to avoid this redundancy, utilize a single function
that, if the MFD scenario is enabled, will perform this fallback logic.
Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Reviewed-by: Andy Shevchenko <redacted>
---
v16
* Add Andy Reviewed-by tag
v15
* Add missed errno.h and ioport.h includes
* Add () to function references in both the commit log and comments
v14
* Add header guard
* Change regs type from u32* to void*
* Add Reviewed-by tag
---
MAINTAINERS | 5 +++
include/linux/mfd/ocelot.h | 62 ++++++++++++++++++++++++++++++++++++++
2 files changed, 67 insertions(+)
create mode 100644 include/linux/mfd/ocelot.h
From: Colin Foster <colin.foster@in-advantage.com> Date: 2022-09-05 16:22:16
There are a few Ocelot chips that contain pinctrl logic, but can be
controlled externally. Specifically the VSC7511, 7512, 7513 and 7514. In
the externally controlled configurations these registers are not
memory-mapped.
Add support for these non-memory-mapped configurations.
Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Reviewed-by: Andy Shevchenko <redacted>
Acked-by: Linus Walleij <redacted>
---
v16
* Add Andy Reviewed-by tag
v15
* No changes
v14
* Add Reviewed and Acked tags
---
drivers/pinctrl/pinctrl-ocelot.c | 16 +++++-----------
1 file changed, 5 insertions(+), 11 deletions(-)
@@ -1975,7 +1976,6 @@ static int ocelot_pinctrl_probe(struct platform_device *pdev)structocelot_pinctrl*info;structreset_control*reset;structregmap*pincfg;-void__iomem*base;intret;structregmap_configregmap_config={.reg_bits=32,
@@ -2004,20 +2004,14 @@ static int ocelot_pinctrl_probe(struct platform_device *pdev)"Failed to get reset\n");reset_control_reset(reset);-base=devm_ioremap_resource(dev,-platform_get_resource(pdev,IORESOURCE_MEM,0));-if(IS_ERR(base))-returnPTR_ERR(base);-info->stride=1+(info->desc->npins-1)/32;regmap_config.max_register=OCELOT_GPIO_SD_MAP*info->stride+15*4;-info->map=devm_regmap_init_mmio(dev,base,®map_config);-if(IS_ERR(info->map)){-dev_err(dev,"Failed to create regmap\n");-returnPTR_ERR(info->map);-}+info->map=ocelot_regmap_from_resource(pdev,0,®map_config);+if(IS_ERR(info->map))+returndev_err_probe(dev,PTR_ERR(info->map),+"Failed to create regmap\n");dev_set_drvdata(dev,info->map);info->dev=dev;
From: Colin Foster <colin.foster@in-advantage.com> Date: 2022-09-05 16:22:23
There are a few Ocelot chips that contain the logic for this bus, but are
controlled externally. Specifically the VSC7511, 7512, 7513, and 7514. In
the externally controlled configurations these registers are not
memory-mapped.
Add support for these non-memory-mapped configurations.
Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Reviewed-by: Andy Shevchenko <redacted>
Acked-by: Jakub Kicinski <kuba@kernel.org>
---
v16
* Add Andy Reviewed-by tag
v15
* No changes
v14
* Add Reviewed and Acked tags
---
drivers/net/mdio/mdio-mscc-miim.c | 42 +++++++++----------------------
1 file changed, 12 insertions(+), 30 deletions(-)
@@ -270,44 +271,25 @@ static int mscc_miim_clk_set(struct mii_bus *bus)staticintmscc_miim_probe(structplatform_device*pdev){-structregmap*mii_regmap,*phy_regmap=NULL;structdevice_node*np=pdev->dev.of_node;+structregmap*mii_regmap,*phy_regmap;structdevice*dev=&pdev->dev;-void__iomem*regs,*phy_regs;structmscc_miim_dev*miim;-structresource*res;structmii_bus*bus;intret;-regs=devm_platform_get_and_ioremap_resource(pdev,0,NULL);-if(IS_ERR(regs)){-dev_err(dev,"Unable to map MIIM registers\n");-returnPTR_ERR(regs);-}--mii_regmap=devm_regmap_init_mmio(dev,regs,&mscc_miim_regmap_config);--if(IS_ERR(mii_regmap)){-dev_err(dev,"Unable to create MIIM regmap\n");-returnPTR_ERR(mii_regmap);-}+mii_regmap=ocelot_regmap_from_resource(pdev,0,+&mscc_miim_regmap_config);+if(IS_ERR(mii_regmap))+returndev_err_probe(dev,PTR_ERR(mii_regmap),+"Unable to create MIIM regmap\n");/* This resource is optional */-res=platform_get_resource(pdev,IORESOURCE_MEM,1);-if(res){-phy_regs=devm_ioremap_resource(dev,res);-if(IS_ERR(phy_regs)){-dev_err(dev,"Unable to map internal phy registers\n");-returnPTR_ERR(phy_regs);-}--phy_regmap=devm_regmap_init_mmio(dev,phy_regs,-&mscc_miim_phy_regmap_config);-if(IS_ERR(phy_regmap)){-dev_err(dev,"Unable to create phy register regmap\n");-returnPTR_ERR(phy_regmap);-}-}+phy_regmap=ocelot_regmap_from_resource_optional(pdev,1,+&mscc_miim_phy_regmap_config);+if(IS_ERR(phy_regmap))+returndev_err_probe(dev,PTR_ERR(phy_regmap),+"Unable to create phy register regmap\n");ret=mscc_miim_setup(dev,&bus,"mscc_miim",mii_regmap,0);if(ret<0){
From: Colin Foster <colin.foster@in-advantage.com> Date: 2022-09-05 16:22:32
DEFINE_RES_ macros have been created for the commonly used resource types,
but not IORESOURCE_REG. Add the macro so it can be used in a similar manner
to all other resource types.
Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Reviewed-by: Andy Shevchenko <redacted>
---
v16
* Add Andy Reviewed-by tag
v15
* No changes
v14
* Add Reviewed tag
---
include/linux/ioport.h | 5 +++++
1 file changed, 5 insertions(+)
From: Colin Foster <colin.foster@in-advantage.com> Date: 2022-09-05 16:22:37
As the commit message suggests, this simply adds the ability to select
SGPIO pinctrl as a module. This becomes more practical when the SGPIO
hardware exists on an external chip, controlled indirectly by I2C or SPI.
This commit enables that level of control.
Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
Reviewed-by: Linus Walleij <redacted>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Reviewed-by: Andy Shevchenko <redacted>
---
v16
* Add Andy Reviewed-by tag
v14,15
* No changes
---
drivers/pinctrl/Kconfig | 5 ++++-
drivers/pinctrl/pinctrl-microchip-sgpio.c | 6 +++++-
2 files changed, 9 insertions(+), 2 deletions(-)
@@ -292,7 +292,7 @@ config PINCTRL_MCP23S08correspondinginterrupt-controller.configPINCTRL_MICROCHIP_SGPIO-bool"Pinctrl driver for Microsemi/Microchip Serial GPIO"+tristate"Pinctrl driver for Microsemi/Microchip Serial GPIO"depends onOFdepends onHAS_IOMEMselectGPIOLIB
@@ -310,6 +310,9 @@ config PINCTRL_MICROCHIP_SGPIOconnectcontrolsignalsfromSFPmodulesandtoactasanLEDcontroller.+Ifcompiledasamodule,themodulenamewillbe+pinctrl-microchip-sgpio.+configPINCTRL_OCELOTtristate"Pinctrl driver for the Microsemi Ocelot and Jaguar2 SoCs"depends onOF
From: Colin Foster <colin.foster@in-advantage.com> Date: 2022-09-05 16:22:44
There are a few Ocelot chips that can contain SGPIO logic, but can be
controlled externally. Specifically the VSC7511, 7512, 7513, and 7514. In
the externally controlled configurations these registers are not
memory-mapped.
Add support for these non-memory-mapped configurations.
Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Acked-by: Linus Walleij <redacted>
Reviewed-by: Andy Shevchenko <redacted>
---
v16
* Add Andy Reviewed-by tag
v15
* No changes
v14
* Add Reviewed and Acked tags
---
drivers/pinctrl/pinctrl-microchip-sgpio.c | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
From: Colin Foster <colin.foster@in-advantage.com> Date: 2022-09-05 16:22:50
The VSC7512 is a networking chip that contains several peripherals. Many of
these peripherals are currently supported by the VSC7513 and VSC7514 chips,
but those run on an internal CPU. The VSC7512 lacks this CPU, and must be
controlled externally.
Utilize the existing drivers by referencing the chip as an MFD. Add support
for the two MDIO buses, the internal phys, pinctrl, and serial GPIO.
Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
---
v16
* Includes fixups:
* ocelot-core.c add includes device.h, export.h, iopoll.h, ioport,h
* ocelot-spi.c add includes device.h, err.h, errno.h, export.h,
mod_devicetable.h, types.h
* Move kconfig.h from ocelot-spi.c to ocelot.h
* Remove unnecessary byteorder.h
* Utilize resource_size() function
v15
* Add missed include bits.h
* Clean _SIZE macros to make them all the same width (e.g. 0x004)
* Remove unnecessary ret = ...; return ret; calls
* Utilize spi_message_init_with_transfers() instead of
spi_message_add_tail() calls in the bus_read routine
* Utilize HZ_PER_MHZ from units.h instead of a magic number
* Remove unnecessary err < 0 checks
* Fix typos in comments
v14
* Add Reviewed tag
* Copyright ranges are now "2021-2022"
* 100-char width applied instead of 80
* Remove invalid dev_err_probe return
* Remove "spi" and "dev" elements from ocelot_ddata struct.
Since "dev" is available throughout, determine "ddata" and "spi" from
there instead of keeping separate references.
* Add header guard in drivers/mfd/ocelot.h
* Document ocelot_ddata struct
---
MAINTAINERS | 1 +
drivers/mfd/Kconfig | 21 +++
drivers/mfd/Makefile | 3 +
drivers/mfd/ocelot-core.c | 161 ++++++++++++++++++++
drivers/mfd/ocelot-spi.c | 299 ++++++++++++++++++++++++++++++++++++++
drivers/mfd/ocelot.h | 49 +++++++
6 files changed, 534 insertions(+)
create mode 100644 drivers/mfd/ocelot-core.c
create mode 100644 drivers/mfd/ocelot-spi.c
create mode 100644 drivers/mfd/ocelot.h
From: Lee Jones <lee@kernel.org> Date: 2022-09-08 09:41:06
On Mon, 05 Sep 2022, Colin Foster wrote:
Several ocelot-related modules are designed for MMIO / regmaps. As such,
they often use a combination of devm_platform_get_and_ioremap_resource()
and devm_regmap_init_mmio().
Operating in an MFD might be different, in that it could be memory mapped,
or it could be SPI, I2C... In these cases a fallback to use IORESOURCE_REG
instead of IORESOURCE_MEM becomes necessary.
When this happens, there's redundant logic that needs to be implemented in
every driver. In order to avoid this redundancy, utilize a single function
that, if the MFD scenario is enabled, will perform this fallback logic.
Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Reviewed-by: Andy Shevchenko <redacted>
---
v16
* Add Andy Reviewed-by tag
v15
* Add missed errno.h and ioport.h includes
* Add () to function references in both the commit log and comments
v14
* Add header guard
* Change regs type from u32* to void*
* Add Reviewed-by tag
---
MAINTAINERS | 5 +++
include/linux/mfd/ocelot.h | 62 ++++++++++++++++++++++++++++++++++++++
2 files changed, 67 insertions(+)
create mode 100644 include/linux/mfd/ocelot.h
From: Lee Jones <lee@kernel.org> Date: 2022-09-08 09:41:49
On Mon, 05 Sep 2022, Colin Foster wrote:
There are a few Ocelot chips that contain the logic for this bus, but are
controlled externally. Specifically the VSC7511, 7512, 7513, and 7514. In
the externally controlled configurations these registers are not
memory-mapped.
Add support for these non-memory-mapped configurations.
Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Reviewed-by: Andy Shevchenko <redacted>
Acked-by: Jakub Kicinski <kuba@kernel.org>
---
v16
* Add Andy Reviewed-by tag
v15
* No changes
v14
* Add Reviewed and Acked tags
---
drivers/net/mdio/mdio-mscc-miim.c | 42 +++++++++----------------------
1 file changed, 12 insertions(+), 30 deletions(-)
From: Lee Jones <lee@kernel.org> Date: 2022-09-08 09:42:12
On Mon, 05 Sep 2022, Colin Foster wrote:
There are a few Ocelot chips that contain pinctrl logic, but can be
controlled externally. Specifically the VSC7511, 7512, 7513 and 7514. In
the externally controlled configurations these registers are not
memory-mapped.
Add support for these non-memory-mapped configurations.
Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Reviewed-by: Andy Shevchenko <redacted>
Acked-by: Linus Walleij <redacted>
---
v16
* Add Andy Reviewed-by tag
v15
* No changes
v14
* Add Reviewed and Acked tags
---
drivers/pinctrl/pinctrl-ocelot.c | 16 +++++-----------
1 file changed, 5 insertions(+), 11 deletions(-)
From: Lee Jones <lee@kernel.org> Date: 2022-09-08 09:42:47
On Mon, 05 Sep 2022, Colin Foster wrote:
As the commit message suggests, this simply adds the ability to select
SGPIO pinctrl as a module. This becomes more practical when the SGPIO
hardware exists on an external chip, controlled indirectly by I2C or SPI.
This commit enables that level of control.
Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
Reviewed-by: Linus Walleij <redacted>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Reviewed-by: Andy Shevchenko <redacted>
---
v16
* Add Andy Reviewed-by tag
v14,15
* No changes
---
drivers/pinctrl/Kconfig | 5 ++++-
drivers/pinctrl/pinctrl-microchip-sgpio.c | 6 +++++-
2 files changed, 9 insertions(+), 2 deletions(-)
From: Lee Jones <lee@kernel.org> Date: 2022-09-08 09:43:15
On Mon, 05 Sep 2022, Colin Foster wrote:
There are a few Ocelot chips that can contain SGPIO logic, but can be
controlled externally. Specifically the VSC7511, 7512, 7513, and 7514. In
the externally controlled configurations these registers are not
memory-mapped.
Add support for these non-memory-mapped configurations.
Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Acked-by: Linus Walleij <redacted>
Reviewed-by: Andy Shevchenko <redacted>
---
v16
* Add Andy Reviewed-by tag
v15
* No changes
v14
* Add Reviewed and Acked tags
---
drivers/pinctrl/pinctrl-microchip-sgpio.c | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
From: Lee Jones <lee@kernel.org> Date: 2022-09-08 09:43:51
On Mon, 05 Sep 2022, Colin Foster wrote:
DEFINE_RES_ macros have been created for the commonly used resource types,
but not IORESOURCE_REG. Add the macro so it can be used in a similar manner
to all other resource types.
Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Reviewed-by: Andy Shevchenko <redacted>
---
v16
* Add Andy Reviewed-by tag
v15
* No changes
v14
* Add Reviewed tag
---
include/linux/ioport.h | 5 +++++
1 file changed, 5 insertions(+)
From: Lee Jones <lee@kernel.org> Date: 2022-09-08 09:44:46
On Mon, 05 Sep 2022, Colin Foster wrote:
The VSC7512 is a networking chip that contains several peripherals. Many of
these peripherals are currently supported by the VSC7513 and VSC7514 chips,
but those run on an internal CPU. The VSC7512 lacks this CPU, and must be
controlled externally.
Utilize the existing drivers by referencing the chip as an MFD. Add support
for the two MDIO buses, the internal phys, pinctrl, and serial GPIO.
Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
---
v16
* Includes fixups:
* ocelot-core.c add includes device.h, export.h, iopoll.h, ioport,h
* ocelot-spi.c add includes device.h, err.h, errno.h, export.h,
mod_devicetable.h, types.h
* Move kconfig.h from ocelot-spi.c to ocelot.h
* Remove unnecessary byteorder.h
* Utilize resource_size() function
v15
* Add missed include bits.h
* Clean _SIZE macros to make them all the same width (e.g. 0x004)
* Remove unnecessary ret = ...; return ret; calls
* Utilize spi_message_init_with_transfers() instead of
spi_message_add_tail() calls in the bus_read routine
* Utilize HZ_PER_MHZ from units.h instead of a magic number
* Remove unnecessary err < 0 checks
* Fix typos in comments
v14
* Add Reviewed tag
* Copyright ranges are now "2021-2022"
* 100-char width applied instead of 80
* Remove invalid dev_err_probe return
* Remove "spi" and "dev" elements from ocelot_ddata struct.
Since "dev" is available throughout, determine "ddata" and "spi" from
there instead of keeping separate references.
* Add header guard in drivers/mfd/ocelot.h
* Document ocelot_ddata struct
---
MAINTAINERS | 1 +
drivers/mfd/Kconfig | 21 +++
drivers/mfd/Makefile | 3 +
drivers/mfd/ocelot-core.c | 161 ++++++++++++++++++++
drivers/mfd/ocelot-spi.c | 299 ++++++++++++++++++++++++++++++++++++++
drivers/mfd/ocelot.h | 49 +++++++
6 files changed, 534 insertions(+)
create mode 100644 drivers/mfd/ocelot-core.c
create mode 100644 drivers/mfd/ocelot-spi.c
create mode 100644 drivers/mfd/ocelot.h
From: Vladimir Oltean <vladimir.oltean@nxp.com> Date: 2022-09-08 14:23:06
On Thu, Sep 08, 2022 at 10:40:48AM +0100, Lee Jones wrote:
Applied, thanks.
Hurray!
Colin, what plans do you have for the rest of VSC7512 upstreaming?
Do you need Lee to provide a stable branch for networking to pull, so
you can continue development in this kernel release cycle, or do you
expect that there won't be dependencies and you can therefore just test
on linux-next?
From: Colin Foster <colin.foster@in-advantage.com> Date: 2022-09-08 15:04:35
On Thu, Sep 08, 2022 at 02:22:56PM +0000, Vladimir Oltean wrote:
On Thu, Sep 08, 2022 at 10:40:48AM +0100, Lee Jones wrote:
quoted
Applied, thanks.
Hurray!
Colin, what plans do you have for the rest of VSC7512 upstreaming?
Do you need Lee to provide a stable branch for networking to pull, so
you can continue development in this kernel release cycle, or do you
expect that there won't be dependencies and you can therefore just test
on linux-next?
Yay!
My plan was to start sending RFCs on the internal copper phys and get
some feedback there. I assume there'll be a couple rounds and I don't
expect to hit this next release (if I'm being honest).
So I'll turn this question around to the net people: would a round or
two of RFCs that don't cleanly apply to net-next be acceptable? Then I
could submit a patch right after the next merge window? I've been
dragging these patches around for quite some time, I can do it for
another month :-)
From: Lee Jones <lee@kernel.org> Date: 2022-09-09 06:57:27
Enjoy!
[ Well done Colin !! ]
The following changes since commit 568035b01cfb107af8d2e4bd2fb9aea22cf5b868:
Linux 6.0-rc1 (2022-08-14 15:50:18 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git ib-mfd-net-pinctrl-v6.0
for you to fetch changes up to f3e893626abeac3cdd9ba41d3395dc6c1b7d5ad6:
mfd: ocelot: Add support for the vsc7512 chip via spi (2022-09-09 07:54:47 +0100)
----------------------------------------------------------------
Immutable branch between MFD Net and Pinctrl due for the v6.0 merge window
----------------------------------------------------------------
Colin Foster (8):
mfd: ocelot: Add helper to get regmap from a resource
net: mdio: mscc-miim: add ability to be used in a non-mmio configuration
pinctrl: ocelot: add ability to be used in a non-mmio configuration
pinctrl: microchip-sgpio: allow sgpio driver to be used as a module
pinctrl: microchip-sgpio: add ability to be used in a non-mmio configuration
resource: add define macro for register address resources
dt-bindings: mfd: ocelot: Add bindings for VSC7512
mfd: ocelot: Add support for the vsc7512 chip via spi
.../devicetree/bindings/mfd/mscc,ocelot.yaml | 160 +++++++++++
MAINTAINERS | 7 +
drivers/mfd/Kconfig | 21 ++
drivers/mfd/Makefile | 3 +
drivers/mfd/ocelot-core.c | 161 +++++++++++
drivers/mfd/ocelot-spi.c | 299 +++++++++++++++++++++
drivers/mfd/ocelot.h | 49 ++++
drivers/net/mdio/mdio-mscc-miim.c | 42 +--
drivers/pinctrl/Kconfig | 5 +-
drivers/pinctrl/pinctrl-microchip-sgpio.c | 14 +-
drivers/pinctrl/pinctrl-ocelot.c | 16 +-
include/linux/ioport.h | 5 +
include/linux/mfd/ocelot.h | 62 +++++
13 files changed, 795 insertions(+), 49 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mfd/mscc,ocelot.yaml
create mode 100644 drivers/mfd/ocelot-core.c
create mode 100644 drivers/mfd/ocelot-spi.c
create mode 100644 drivers/mfd/ocelot.h
create mode 100644 include/linux/mfd/ocelot.h
--
Lee Jones [李琼斯]
From: Lee Jones <lee@kernel.org> Date: 2022-09-09 07:21:38
On Thu, 08 Sep 2022, Colin Foster wrote:
On Thu, Sep 08, 2022 at 02:22:56PM +0000, Vladimir Oltean wrote:
quoted
On Thu, Sep 08, 2022 at 10:40:48AM +0100, Lee Jones wrote:
quoted
Applied, thanks.
Hurray!
Colin, what plans do you have for the rest of VSC7512 upstreaming?
Do you need Lee to provide a stable branch for networking to pull, so
you can continue development in this kernel release cycle, or do you
expect that there won't be dependencies and you can therefore just test
on linux-next?
Yay!
My plan was to start sending RFCs on the internal copper phys and get
some feedback there. I assume there'll be a couple rounds and I don't
expect to hit this next release (if I'm being honest).
So I'll turn this question around to the net people: would a round or
two of RFCs that don't cleanly apply to net-next be acceptable? Then I
could submit a patch right after the next merge window? I've been
dragging these patches around for quite some time, I can do it for
another month :-)
Immutable branch now tested and pushed.
See reply to cover-letter.
--
Lee Jones [李琼斯]
From: Jakub Kicinski <kuba@kernel.org> Date: 2022-09-19 17:15:07
On Thu, 8 Sep 2022 08:04:13 -0700 Colin Foster wrote:
My plan was to start sending RFCs on the internal copper phys and get
some feedback there. I assume there'll be a couple rounds and I don't
expect to hit this next release (if I'm being honest).
So I'll turn this question around to the net people: would a round or
two of RFCs that don't cleanly apply to net-next be acceptable? Then I
could submit a patch right after the next merge window? I've been
dragging these patches around for quite some time, I can do it for
another month :-)
FWIW RFC patches which don't apply cleanly seem perfectly fine to me.
Perhaps note the base in the cover letter for those who may want to
test them.
We can pull Lee's branch (thanks!) if it turns out the code is ready
long before the MW.
From: Colin Foster <colin.foster@in-advantage.com> Date: 2022-09-19 19:05:38
Hi Jakub,
On Mon, Sep 19, 2022 at 10:14:53AM -0700, Jakub Kicinski wrote:
On Thu, 8 Sep 2022 08:04:13 -0700 Colin Foster wrote:
quoted
My plan was to start sending RFCs on the internal copper phys and get
some feedback there. I assume there'll be a couple rounds and I don't
expect to hit this next release (if I'm being honest).
So I'll turn this question around to the net people: would a round or
two of RFCs that don't cleanly apply to net-next be acceptable? Then I
could submit a patch right after the next merge window? I've been
dragging these patches around for quite some time, I can do it for
another month :-)
FWIW RFC patches which don't apply cleanly seem perfectly fine to me.
Perhaps note the base in the cover letter for those who may want to
test them.
We can pull Lee's branch (thanks!) if it turns out the code is ready
long before the MW.
I'll quote Vladimir Oltean: "It mostly looks ok to me"
https://lore.kernel.org/netdev/20220912155234.ds73xpn5ijjq3iif@skbuf/
If you pull in Lee's branch I would certainly make use of it in the next
2-3 weeks. I would probably send out the patch set for review in a day
or two.
@@ -0,0 +1,160 @@+# SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause */+%YAML1.2+---+$id:http://devicetree.org/schemas/mfd/mscc,ocelot.yaml#+$schema:http://devicetree.org/meta-schemas/core.yaml#++title:Ocelot Externally-Controlled Ethernet Switch++maintainers:+-Colin Foster <colin.foster@in-advantage.com>++description:|+The Ocelot ethernet switch family contains chips that have an internal CPU+(VSC7513, VSC7514) and chips that don't (VSC7511, VSC7512). All switches have+the option to be controlled externally, which is the purpose of this driver.
"Driver" as in Linux driver? If so, drop it.
Best regards,
Krzysztof