From: Ivan Vecera <ivecera@redhat.com>
To: netdev@vger.kernel.org
Cc: Prathosh Satish <Prathosh.Satish@microchip.com>,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
Jiri Pirko <jiri@resnulli.us>, Petr Oros <poros@redhat.com>,
Michal Schmidt <mschmidt@redhat.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH net-next 0/2] dpll: zl3073x: consolidate chip info and add temperature reporting
Date: Fri, 27 Feb 2026 11:52:58 +0100 [thread overview]
Message-ID: <20260227105300.710272-1-ivecera@redhat.com> (raw)
This series refactors the ZL3073x chip variant handling and adds die
temperature reporting for chips that support it.
Patch 1 replaces the five per-variant chip_info structures and their
exported symbols with a single consolidated lookup table. The chip
variant is now detected at runtime from the chip ID register rather
than being selected at compile time via bus driver match data. This
simplifies the I2C/SPI drivers and makes adding new variants a
single-line table addition. A flags field replaces the hardcoded
chip_id switch in zl3073x_dev_is_ref_phase_comp_32bit().
Patch 2 uses the new flags infrastructure to add die temperature
reporting for chip variants that provide a temperature status register.
The temp_get callback is conditionally set during device registration
based on the ZL3073X_FLAG_DIE_TEMP chip flag.
Ivan Vecera (2):
dpll: zl3073x: detect DPLL channel count from chip ID at runtime
dpll: zl3073x: add die temperature reporting for supported chips
drivers/dpll/zl3073x/core.c | 118 ++++++++++--------------------------
drivers/dpll/zl3073x/core.h | 59 +++++++++---------
drivers/dpll/zl3073x/dpll.c | 28 ++++++++-
drivers/dpll/zl3073x/dpll.h | 2 +
drivers/dpll/zl3073x/i2c.c | 37 ++++-------
drivers/dpll/zl3073x/regs.h | 2 +
drivers/dpll/zl3073x/spi.c | 37 ++++-------
7 files changed, 113 insertions(+), 170 deletions(-)
--
2.52.0
next reply other threads:[~2026-02-27 10:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 10:52 Ivan Vecera [this message]
2026-02-27 10:52 ` [PATCH net-next 1/2] dpll: zl3073x: detect DPLL channel count from chip ID at runtime Ivan Vecera
2026-02-27 10:53 ` [PATCH net-next 2/2] dpll: zl3073x: add die temperature reporting for supported chips Ivan Vecera
2026-03-02 14:01 ` [PATCH net-next 0/2] dpll: zl3073x: consolidate chip info and add temperature reporting Simon Horman
2026-03-03 11:20 ` patchwork-bot+netdevbpf
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=20260227105300.710272-1-ivecera@redhat.com \
--to=ivecera@redhat.com \
--cc=Prathosh.Satish@microchip.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=poros@redhat.com \
--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