From: Mark Brown <broonie@kernel.org>
To: Ivan Vecera <ivecera@redhat.com>
Cc: netdev@vger.kernel.org,
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>,
Lee Jones <lee@kernel.org>, Kees Cook <kees@kernel.org>,
Andy Shevchenko <andy@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Schmidt <mschmidt@redhat.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH v3 net-next 3/8] mfd: Add Microchip ZL3073x support
Date: Thu, 17 Apr 2025 16:57:57 +0100 [thread overview]
Message-ID: <4324af33-4be7-45bc-b7d2-b400a7865319@sirena.org.uk> (raw)
In-Reply-To: <20250416162144.670760-4-ivecera@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 494 bytes --]
On Wed, Apr 16, 2025 at 06:21:39PM +0200, Ivan Vecera wrote:
> +static const struct regmap_config zl3073x_regmap_config = {
> + .reg_bits = 8,
> + .val_bits = 8,
> + .max_register = ZL_RANGE_OFF + ZL_NUM_REGS - 1,
> + .ranges = &zl3073x_regmap_range,
> + .num_ranges = 1,
> + .cache_type = REGCACHE_RBTREE,
Unless you have a specific reason to use something else you should
probably use _MAPLE these days, it's a more modern data structure and
makes choices more suited to current hardware.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-04-17 15:58 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 16:21 [PATCH v3 net-next 00/10] Add Microchip ZL3073x support (part 1) Ivan Vecera
2025-04-16 16:21 ` [PATCH v3 net-next 1/8] dt-bindings: dpll: Add device tree bindings for DPLL device and pin Ivan Vecera
2025-04-21 22:20 ` Rob Herring
2025-04-21 22:29 ` Rob Herring
2025-04-16 16:21 ` [PATCH v3 net-next 2/8] dt-bindings: dpll: Add support for Microchip Azurite chip family Ivan Vecera
2025-04-16 17:42 ` Rob Herring (Arm)
2025-04-16 18:29 ` Ivan Vecera
2025-04-17 5:54 ` Krzysztof Kozlowski
2025-04-16 16:21 ` [PATCH v3 net-next 3/8] mfd: Add Microchip ZL3073x support Ivan Vecera
2025-04-16 17:11 ` Andrew Lunn
[not found] ` <CAAVpwAsw4-7n_iV=8aXp7=X82Mj7M-vGAc3f-fVbxxg0qgAQQA@mail.gmail.com>
2025-04-17 13:13 ` Andrew Lunn
2025-04-17 14:50 ` Ivan Vecera
2025-04-17 15:12 ` Ivan Vecera
2025-04-17 15:42 ` Andy Shevchenko
2025-04-17 16:29 ` Ivan Vecera
2025-04-17 16:35 ` Andy Shevchenko
2025-04-18 20:18 ` Andrew Lunn
2025-04-17 15:51 ` Andy Shevchenko
2025-04-17 15:57 ` Mark Brown [this message]
2025-04-16 16:21 ` [PATCH v3 net-next 4/8] mfd: zl3073x: Add support for devlink device info Ivan Vecera
2025-04-17 15:53 ` Andy Shevchenko
2025-04-16 16:21 ` [PATCH v3 net-next 5/8] mfd: zl3073x: Add functions to work with register mailboxes Ivan Vecera
2025-04-16 17:32 ` Andrew Lunn
2025-04-16 18:27 ` Ivan Vecera
2025-04-17 10:02 ` Ivan Vecera
2025-04-17 13:27 ` Andrew Lunn
2025-04-17 14:15 ` Ivan Vecera
2025-04-24 15:49 ` Lee Jones
2025-04-17 13:22 ` Andrew Lunn
2025-04-17 14:18 ` Ivan Vecera
2025-04-17 16:13 ` Lee Jones
2025-04-17 16:35 ` Ivan Vecera
2025-04-16 16:21 ` [PATCH v3 net-next 6/8] mfd: zl3073x: Add clock_id field Ivan Vecera
2025-04-16 16:21 ` [PATCH v3 net-next 7/8] mfd: zl3073x: Fetch invariants during probe Ivan Vecera
2025-04-16 16:21 ` [PATCH v3 net-next 8/8] mfd: zl3073x: Register DPLL sub-device during init Ivan Vecera
2025-04-17 16:20 ` Lee Jones
2025-04-17 16:40 ` Ivan Vecera
2025-04-24 15:34 ` Lee Jones
2025-04-24 15:36 ` Lee Jones
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=4324af33-4be7-45bc-b7d2-b400a7865319@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Prathosh.Satish@microchip.com \
--cc=akpm@linux-foundation.org \
--cc=andy@kernel.org \
--cc=arkadiusz.kubalewski@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=kees@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--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
all inboxes | Powered by JetHome®