From: Ivan Vecera <ivecera@redhat.com>
To: netdev@vger.kernel.org
Cc: Jiri Pirko <jiri@resnulli.us>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Prathosh Satish <Prathosh.Satish@microchip.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Michal Schmidt <mschmidt@redhat.com>,
Petr Oros <poros@redhat.com>
Subject: [PATCH net-next 0/5] dpll: zl3073x: Add support for devlink flash
Date: Fri, 25 Jul 2025 17:41:31 +0200 [thread overview]
Message-ID: <20250725154136.1008132-1-ivecera@redhat.com> (raw)
Add functionality for accessing device hardware registers, loading
firmware bundles, and accessing the device's internal flash memory,
and use it to implement the devlink flash functionality.
Patch breakdown:
Patch1: helpers to access hardware registers
Patch2: low level functions to access flash memory
Patch3: support to load firmware bundles
Patch4: refactoring device initialization and helper functions
for stopping and resuming device normal operation
Patch5: devlink .flash_update callback implementation
Ivan Vecera (5):
dpll: zl3073x: Add functions to access hardware registers
dpll: zl3073x: Add low-level flash functions
dpll: zl3073x: Add firmware loading functionality
dpll: zl3073x: Refactor DPLL initialization
dpll: zl3073x: Implement devlink flash callback
Documentation/networking/devlink/zl3073x.rst | 14 +
drivers/dpll/zl3073x/Makefile | 2 +-
drivers/dpll/zl3073x/core.c | 362 +++++++---
drivers/dpll/zl3073x/core.h | 32 +
drivers/dpll/zl3073x/devlink.c | 92 ++-
drivers/dpll/zl3073x/devlink.h | 3 +
drivers/dpll/zl3073x/flash.c | 674 +++++++++++++++++++
drivers/dpll/zl3073x/flash.h | 29 +
drivers/dpll/zl3073x/fw.c | 495 ++++++++++++++
drivers/dpll/zl3073x/fw.h | 52 ++
drivers/dpll/zl3073x/regs.h | 51 ++
11 files changed, 1715 insertions(+), 91 deletions(-)
create mode 100644 drivers/dpll/zl3073x/flash.c
create mode 100644 drivers/dpll/zl3073x/flash.h
create mode 100644 drivers/dpll/zl3073x/fw.c
create mode 100644 drivers/dpll/zl3073x/fw.h
--
2.49.1
next reply other threads:[~2025-07-25 15:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 15:41 Ivan Vecera [this message]
2025-07-25 15:41 ` [PATCH net-next 1/5] dpll: zl3073x: Add functions to access hardware registers Ivan Vecera
2025-07-25 15:41 ` [PATCH net-next 2/5] dpll: zl3073x: Add low-level flash functions Ivan Vecera
2025-07-26 10:36 ` kernel test robot
2025-07-25 15:41 ` [PATCH net-next 3/5] dpll: zl3073x: Add firmware loading functionality Ivan Vecera
2025-07-26 20:33 ` Simon Horman
2025-07-29 15:20 ` Ivan Vecera
2025-07-25 15:41 ` [PATCH net-next 4/5] dpll: zl3073x: Refactor DPLL initialization Ivan Vecera
2025-07-26 10:57 ` kernel test robot
2025-07-25 15:41 ` [PATCH net-next 5/5] dpll: zl3073x: Implement devlink flash callback Ivan Vecera
2025-07-25 17:18 ` [PATCH net-next 0/5] dpll: zl3073x: Add support for devlink flash Ivan Vecera
2025-07-25 17:42 ` Jakub Kicinski
2025-07-25 17:59 ` 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=20250725154136.1008132-1-ivecera@redhat.com \
--to=ivecera@redhat.com \
--cc=Prathosh.Satish@microchip.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jiri@resnulli.us \
--cc=kuba@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=poros@redhat.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).