From: Ivan Vecera <ivecera@redhat.com>
To: netdev@vger.kernel.org
Cc: Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
Jiri Pirko <jiri@resnulli.us>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Prathosh Satish <Prathosh.Satish@microchip.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, Lee Jones <lee@kernel.org>,
Andy Shevchenko <andy@kernel.org>,
Michal Schmidt <mschmidt@redhat.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: [PATCH net-next v7 0/8] Add Microchip ZL3073x support (part 1)
Date: Wed, 7 May 2025 14:43:50 +0200 [thread overview]
Message-ID: <20250507124358.48776-1-ivecera@redhat.com> (raw)
Add support for Microchip Azurite DPLL/PTP/SyncE chip family that
provides DPLL and PTP functionality. This series bring first part
that adds the common MFD driver that provides an access to the bus
that can be either I2C or SPI.
The next part of the series is bringing the DPLL driver that will
covers DPLL functionality. Another series will bring PTP driver and
flashing capability via devlink in the MFD driver will follow soon.
Testing was done by myself and by Prathosh Satish on Microchip EDS2
development board with ZL30732 DPLL chip connected over I2C bus.
Patch breakdown
===============
Patch 1 - Common DT schema for DPLL device and pin
Patch 2 - DT bindings for microchip,zl3073* devices
Patch 3 - Basic support for I2C, SPI and regmap configuration
Patch 4 - Devlink device registration and info
Patch 5 - Helpers for reading and writing register mailboxes
Patch 6 - Fetch invariant register values used by DPLL/PTP sub-drivers
Patch 7 - Clock ID generation for DPLL driver
Patch 8 - Register/create DPLL device cells
---
v6->v7:
* pass channel number using platform data instead of mfd_cell->id
v5->v6:
* fixed devlink info firmware version to be running instead of fixed
* added documentation for devlink info versions
v4->v5:
* fixed DT patches description
* dropped mailbox API
* added type-safe register access functions
* added an ability to protect multi-op accesses
v3->v4:
* fixed shortcomings in DT patches
* completely reworked register access
* removed a need to manage locking during mailbox accesses by callers
* regcache switched to maple
* dev_err_probe() in probe path
* static mfd cells during sub-devices registration
v1->v3:
* dropped macros for generating register access functions
* register access functions are provided in <linux/mfd/zl3073x_regs.h>
* fixed DT descriptions and compatible wildcard usage
* reworked regmap locking
- regmap uses implicit locking
- mailbox registers are additionally protected by extra mutex
* fixed regmap virtual address range
* added regmap rbtree cache (only for page selector now)
* dropped patches for exporting strnchrnul and for supporting mfg file
this will be maybe added later
Ivan Vecera (8):
dt-bindings: dpll: Add DPLL device and pin
dt-bindings: dpll: Add support for Microchip Azurite chip family
mfd: Add Microchip ZL3073x support
mfd: zl3073x: Add support for devlink device info
mfd: zl3073x: Protect operations requiring multiple register accesses
mfd: zl3073x: Fetch invariants during probe
mfd: zl3073x: Add clock_id field
mfd: zl3073x: Register DPLL sub-device during init
.../devicetree/bindings/dpll/dpll-device.yaml | 76 ++
.../devicetree/bindings/dpll/dpll-pin.yaml | 45 +
.../bindings/dpll/microchip,zl30731.yaml | 115 +++
Documentation/networking/devlink/index.rst | 1 +
Documentation/networking/devlink/zl3073x.rst | 37 +
MAINTAINERS | 11 +
drivers/mfd/Kconfig | 32 +
drivers/mfd/Makefile | 5 +
drivers/mfd/zl3073x-core.c | 875 ++++++++++++++++++
drivers/mfd/zl3073x-i2c.c | 68 ++
drivers/mfd/zl3073x-regs.h | 54 ++
drivers/mfd/zl3073x-spi.c | 68 ++
drivers/mfd/zl3073x.h | 31 +
include/linux/mfd/zl3073x-regs.h | 88 ++
include/linux/mfd/zl3073x.h | 202 ++++
15 files changed, 1708 insertions(+)
create mode 100644 Documentation/devicetree/bindings/dpll/dpll-device.yaml
create mode 100644 Documentation/devicetree/bindings/dpll/dpll-pin.yaml
create mode 100644 Documentation/devicetree/bindings/dpll/microchip,zl30731.yaml
create mode 100644 Documentation/networking/devlink/zl3073x.rst
create mode 100644 drivers/mfd/zl3073x-core.c
create mode 100644 drivers/mfd/zl3073x-i2c.c
create mode 100644 drivers/mfd/zl3073x-regs.h
create mode 100644 drivers/mfd/zl3073x-spi.c
create mode 100644 drivers/mfd/zl3073x.h
create mode 100644 include/linux/mfd/zl3073x-regs.h
create mode 100644 include/linux/mfd/zl3073x.h
--
2.49.0
next reply other threads:[~2025-05-07 12:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 12:43 Ivan Vecera [this message]
2025-05-07 12:43 ` [PATCH net-next v7 1/8] dt-bindings: dpll: Add DPLL device and pin Ivan Vecera
2025-05-07 12:43 ` [PATCH net-next v7 2/8] dt-bindings: dpll: Add support for Microchip Azurite chip family Ivan Vecera
2025-05-07 12:43 ` [PATCH net-next v7 3/8] mfd: Add Microchip ZL3073x support Ivan Vecera
2025-05-07 12:43 ` [PATCH net-next v7 4/8] mfd: zl3073x: Add support for devlink device info Ivan Vecera
2025-05-07 12:43 ` [PATCH net-next v7 5/8] mfd: zl3073x: Protect operations requiring multiple register accesses Ivan Vecera
2025-05-07 12:43 ` [PATCH net-next v7 6/8] mfd: zl3073x: Fetch invariants during probe Ivan Vecera
2025-05-07 12:43 ` [PATCH net-next v7 7/8] mfd: zl3073x: Add clock_id field Ivan Vecera
2025-05-07 12:43 ` [PATCH net-next v7 8/8] mfd: zl3073x: Register DPLL sub-device during init Ivan Vecera
2025-05-07 13:30 ` Andy Shevchenko
2025-05-07 13:41 ` Andy Shevchenko
2025-05-07 13:56 ` Ivan Vecera
2025-05-07 14:59 ` Andy Shevchenko
2025-05-07 15:26 ` Lee Jones
2025-05-12 11:55 ` Ivan Vecera
2025-05-13 9:41 ` Lee Jones
2025-05-13 10:47 ` Ivan Vecera
2025-05-19 16:59 ` Ivan Vecera
2025-05-22 7:39 ` Lee Jones
2025-05-22 8:54 ` Ivan Vecera
2025-05-22 10:45 ` Lee Jones
2025-05-22 11:23 ` Ivan Vecera
2025-06-12 10:26 ` Lee Jones
2025-05-07 14:19 ` Ivan Vecera
2025-05-07 15:00 ` Andy Shevchenko
2025-05-07 15:23 ` Ivan Vecera
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=20250507124358.48776-1-ivecera@redhat.com \
--to=ivecera@redhat.com \
--cc=Prathosh.Satish@microchip.com \
--cc=andy@kernel.org \
--cc=arkadiusz.kubalewski@intel.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=horms@kernel.org \
--cc=jiri@resnulli.us \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=lee@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=vadim.fedorenko@linux.dev \
/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).