From: Ivan Vecera <ivecera@redhat.com>
To: Andy Shevchenko <andy@kernel.org>
Cc: netdev@vger.kernel.org, Michal Schmidt <mschmidt@redhat.com>,
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>,
Andrew Morton <akpm@linux-foundation.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH 01/28] mfd: Add Microchip ZL3073x support
Date: Wed, 9 Apr 2025 08:40:22 +0200 [thread overview]
Message-ID: <eeddcda2-efe4-4563-bb2c-70009b374486@redhat.com> (raw)
In-Reply-To: <Z_QTzwXvxcSh53Cq@smile.fi.intel.com>
On 07. 04. 25 8:05 odp., Andy Shevchenko wrote:
> On Mon, Apr 07, 2025 at 07:28:28PM +0200, Ivan Vecera wrote:
>> This adds base MFD driver for Microchip Azurite ZL3073x chip family.
>> These chips provide DPLL and PHC (PTP) functionality and they can
>> be connected over I2C or SPI bus.
>>
>> The MFD driver provide basic communication and synchronization
>> over the bus and common functionality that are used by the DPLL
>> driver (later in this series) and by the PTP driver (will be
>> added later).
>>
>> The chip family is characterized by following properties:
>> * 2 separate DPLL units (channels)
>> * 5 synthesizers
>> * 10 input pins (references)
>> * 10 outputs
>> * 20 output pins (output pin pair shares one output)
>> * Each reference and output can act in differential or single-ended
>> mode (reference or output in differential mode consumes 2 pins)
>> * Each output is connected to one of the synthesizers
>> * Each synthesizer is driven by one of the DPLL unit
> .
> The comments below are applicable to entire series, take your time and fix
> *all* stylic and header issues before sending v2.
>
> ...
>
> + array_size.h
> + bits.h
>
> + device/devres.h
>
>> +#include <linux/module.h>
>
> This file uses *much* amore than that.
>
> + regmap.h
>
>
>> +#include "zl3073x.h"
>
> ...
>
Will fix in the next series.
>> +/*
>> + * Regmap ranges
>> + */
>> +#define ZL3073x_PAGE_SIZE 128
>> +#define ZL3073x_NUM_PAGES 16
>> +#define ZL3073x_PAGE_SEL 0x7F
>> +
>> +static const struct regmap_range_cfg zl3073x_regmap_ranges[] = {
>> + {
>> + .range_min = 0,
>
> Are you sure you get the idea of virtual address pages here?
What is wrong here?
I have a device that uses 7-bit addresses and have 16 register pages.
Each pages is from 0x00-0x7f and register 0x7f is used as page selector
where bits 0-3 select the page.
>> + .range_max = ZL3073x_NUM_PAGES * ZL3073x_PAGE_SIZE,
>> + .selector_reg = ZL3073x_PAGE_SEL,
>> + .selector_mask = GENMASK(3, 0),
>> + .selector_shift = 0,
>> + .window_start = 0,
>> + .window_len = ZL3073x_PAGE_SIZE,
>> + },
>> +};
>
> ...
>
>> +struct zl3073x_dev *zl3073x_dev_alloc(struct device *dev)
>> +{
>> + struct zl3073x_dev *zldev;
>> +
>> + return devm_kzalloc(dev, sizeof(*zldev), GFP_KERNEL);
>> +}
>> +EXPORT_SYMBOL_NS_GPL(zl3073x_dev_alloc, "ZL3073X");
>> +
>> +int zl3073x_dev_init(struct zl3073x_dev *zldev)
>> +{
>> + devm_mutex_init(zldev->dev, &zldev->lock);
>
> Missing check.
Will fix.
>> + return 0;
>> +}
>> +EXPORT_SYMBOL_NS_GPL(zl3073x_dev_init, "ZL3073X");
>> +
>> +void zl3073x_dev_exit(struct zl3073x_dev *zldev)
>> +{
>> +}
>> +EXPORT_SYMBOL_NS_GPL(zl3073x_dev_exit, "ZL3073X");
>
> What's the point in these stubs?
This function is used and filled later. I will drop it here and
introduce when it will be necessary.
>> +#include <linux/i2c.h>
>
>> +#include <linux/kernel.h>
>
> No usual driver should include kernel.h, please follow IWYU principle.
Will follow IWYU in v2.
>> +#include <linux/module.h>
>
> Again, this is just a random list of headers, see above and follow the IWYU
> principle.
Ditto.
>> +#include "zl3073x.h"
>
> ...
>
>> +static const struct i2c_device_id zl3073x_i2c_id[] = {
>> + { "zl3073x-i2c", },
>
> Redundant inner comma.
Ack
>> + { /* sentinel */ },
>
> No comma for the sentinel.
>
>> +};
Ack
>> +static const struct of_device_id zl3073x_i2c_of_match[] = {
>> + { .compatible = "microchip,zl3073x-i2c" },
>> + { /* sentinel */ },
Ack
>> +};
>
>> +static int zl3073x_i2c_probe(struct i2c_client *client)
>> +{
>> + struct device *dev = &client->dev;
>> + const struct i2c_device_id *id;
>> + struct zl3073x_dev *zldev;
>
>> + int rc = 0;
>
> Useless assignment.
Sorry for that, it was originally necessary.
Will drop.
>> + zldev = zl3073x_dev_alloc(dev);
>> + if (!zldev)
>> + return -ENOMEM;
>> +
>> + id = i2c_client_get_device_id(client);
>> + zldev->dev = dev;
>> +
>> + zldev->regmap = devm_regmap_init_i2c(client,
>> + zl3073x_get_regmap_config());
>
> It's perfectly a single line.
I tried to follow strictly 80 chars/line. Will fix.
>> + if (IS_ERR(zldev->regmap)) {
>> + rc = PTR_ERR(zldev->regmap);
>> + dev_err(dev, "Failed to allocate register map: %d\n", rc);
>> + return rc;
>
> return dev_err_probe(...);
Will change.
>> + }
>> +
>> + i2c_set_clientdata(client, zldev);
>> +
>> + return zl3073x_dev_init(zldev);
>> +}
>
> ...
>
>> +static void zl3073x_i2c_remove(struct i2c_client *client)
>> +{
>
>> + struct zl3073x_dev *zldev;
>> +
>> + zldev = i2c_get_clientdata(client);
>
> Just make it one line definition + assignment.
Ack
>> + zl3073x_dev_exit(zldev);
>
> This is a red flag and because you haven't properly named the calls (i.e. devm
> to show that they are only for probe stage and use managed resources) this is
> not easy to catch.
Will rename zl3073x_dev_alloc() to zl3073x_devm_alloc() to indicate that
devres is used... Probably will drop zl3073x_dev_exit() entirely and
take care of devlink unregistration by devres way.
>> +}
>> +
>> +static struct i2c_driver zl3073x_i2c_driver = {
>> + .driver = {
>> + .name = "zl3073x-i2c",
>> + .of_match_table = of_match_ptr(zl3073x_i2c_of_match),
>
> Please, never use of_match_ptr() or ACPI_PTR() in a new code.
Ack
>> + },
>> + .probe = zl3073x_i2c_probe,
>> + .remove = zl3073x_i2c_remove,
>> + .id_table = zl3073x_i2c_id,
>> +};
>
>> +
>
> Redundant blank line.
>
>> +module_i2c_driver(zl3073x_i2c_driver);
>
> ...
>
>> +#include <linux/kernel.h>
>
> Just no. You should know what you are doing in the driver.
Will fix.
>> +#include <linux/module.h>
>
>> +#include <linux/of.h>
Ack
>> +#include <linux/spi/spi.h>
>> +#include "zl3073x.h"
>
> ...
>
>> +static const struct spi_device_id zl3073x_spi_id[] = {
>> + { "zl3073x-spi", },
>> + { /* sentinel */ },
>> +};
>> +MODULE_DEVICE_TABLE(spi, zl3073x_spi_id);
>> +
>> +static const struct of_device_id zl3073x_spi_of_match[] = {
>> + { .compatible = "microchip,zl3073x-spi" },
>> + { /* sentinel */ },
>> +};
>> +MODULE_DEVICE_TABLE(of, zl3073x_spi_of_match);
>
> Move the above closer to its user.
Ack
>> +static int zl3073x_spi_probe(struct spi_device *spidev)
>
> Usual name is spi for the above, it's shorter and allows to tidy up the code.
>
> And below same comments as for i2c part of the driver.
OK, will fix.
>> +#ifndef __ZL3073X_CORE_H
>> +#define __ZL3073X_CORE_H
>
>> +#include <linux/mfd/zl3073x.h>
>
> How is it used here, please?
Will change to forward declaration.
>> +struct zl3073x_dev *zl3073x_dev_alloc(struct device *dev);
>> +int zl3073x_dev_init(struct zl3073x_dev *zldev);
>> +void zl3073x_dev_exit(struct zl3073x_dev *zldev);
>> +const struct regmap_config *zl3073x_get_regmap_config(void);
>> +
>> +#endif /* __ZL3073X_CORE_H */
>
> ...
>
>> +#ifndef __LINUX_MFD_ZL3073X_H
>> +#define __LINUX_MFD_ZL3073X_H
>
>> +#include <linux/device.h>
>> +#include <linux/regmap.h>
>
> Ditto. Two unused headers and one which must be included is missed.
The same, forward declaration and inclusion of <linux/mutex.h>
>> +struct zl3073x_dev {
>> + struct device *dev;
>> + struct regmap *regmap;
>> + struct mutex lock;
>> +};
Thank you Andy for the review.
I.
next prev parent reply other threads:[~2025-04-09 6:40 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 17:28 [PATCH 00/28] Add Microchip ZL3073x support Ivan Vecera
2025-04-07 17:28 ` [PATCH 01/28] mfd: " Ivan Vecera
2025-04-07 17:53 ` Krzysztof Kozlowski
2025-04-09 6:31 ` Ivan Vecera
2025-04-07 18:05 ` Andy Shevchenko
2025-04-09 6:40 ` Ivan Vecera [this message]
2025-04-14 6:36 ` Andy Shevchenko
2025-04-14 11:39 ` Ivan Vecera
2025-04-14 11:52 ` Ivan Vecera
2025-04-14 13:55 ` Andy Shevchenko
2025-04-14 14:08 ` Ivan Vecera
2025-04-14 14:07 ` Ivan Vecera
2025-04-14 14:10 ` Andy Shevchenko
2025-04-14 14:13 ` Andy Shevchenko
2025-04-14 14:16 ` Andy Shevchenko
2025-04-14 14:53 ` Ivan Vecera
2025-04-14 17:09 ` Andy Shevchenko
2025-04-14 17:42 ` Ivan Vecera
2025-04-14 13:58 ` Andy Shevchenko
2025-04-07 17:28 ` [PATCH 02/28] mfd: zl3073x: Register itself as devlink device Ivan Vecera
2025-04-07 20:57 ` Andrew Lunn
2025-04-09 6:41 ` Ivan Vecera
2025-04-07 17:28 ` [PATCH 03/28] mfd: zl3073x: Add register access helpers Ivan Vecera
2025-04-07 21:03 ` Andrew Lunn
2025-04-09 6:42 ` Ivan Vecera
2025-04-07 17:28 ` [PATCH 04/28] mfd: zl3073x: Add macros for device registers access Ivan Vecera
2025-04-07 17:28 ` [PATCH 05/28] mfd: zl3073x: Add components versions register defs Ivan Vecera
2025-04-07 21:09 ` Andrew Lunn
2025-04-09 6:44 ` Ivan Vecera
2025-04-10 7:11 ` Krzysztof Kozlowski
2025-04-10 10:23 ` Ivan Vecera
2025-04-10 10:42 ` Krzysztof Kozlowski
2025-04-10 12:01 ` Ivan Vecera
2025-04-07 17:28 ` [PATCH 06/28] mfd: zl3073x: Implement devlink device info Ivan Vecera
2025-04-07 17:28 ` [PATCH 07/28] mfd: zl3073x: Add macro to wait for register value bits to be cleared Ivan Vecera
2025-04-07 17:28 ` [PATCH 08/28] mfd: zl3073x: Add functions to work with register mailboxes Ivan Vecera
2025-04-07 17:28 ` [PATCH 09/28] mfd: zl3073x: Add clock_id field Ivan Vecera
2025-04-07 17:31 ` [PATCH 10/28] lib: Allow modules to use strnchrnul Ivan Vecera
2025-04-07 17:50 ` Kees Cook
2025-04-07 17:31 ` [PATCH 11/28] mfd: zl3073x: Load mfg file into HW if it is present Ivan Vecera
2025-04-07 17:31 ` [PATCH 12/28] mfd: zl3073x: Fetch invariants during probe Ivan Vecera
2025-04-07 17:31 ` [PATCH 13/28] dpll: Add Microchip ZL3073x DPLL driver Ivan Vecera
2025-04-07 17:31 ` [PATCH 14/28] mfd: zl3073x: Register DPLL sub-device during init Ivan Vecera
2025-04-07 17:31 ` [PATCH 15/28] dt-bindings: dpll: Add device tree bindings for DPLL device and pin Ivan Vecera
2025-04-07 18:01 ` Krzysztof Kozlowski
2025-04-07 18:10 ` Krzysztof Kozlowski
2025-04-08 5:19 ` Michal Schmidt
2025-04-09 7:09 ` Ivan Vecera
2025-04-07 17:31 ` [PATCH 16/28] dt-bindings: dpll: Add support for Microchip Azurite chip family Ivan Vecera
2025-04-07 18:04 ` Krzysztof Kozlowski
2025-04-09 7:19 ` Ivan Vecera
2025-04-10 7:01 ` Krzysztof Kozlowski
2025-04-10 10:28 ` Ivan Vecera
2025-04-10 12:19 ` Krzysztof Kozlowski
2025-04-10 12:38 ` Ivan Vecera
2025-04-07 17:31 ` [PATCH 17/28] dpll: zl3073x: Read DPLL types from firmware Ivan Vecera
2025-04-07 17:31 ` [PATCH 18/28] dpll: zl3073x: Read optional pin properties " Ivan Vecera
2025-04-07 18:06 ` Krzysztof Kozlowski
2025-04-09 7:22 ` Ivan Vecera
2025-04-07 17:31 ` [PATCH 19/28] dpll: zl3073x: Implement input pin selection in manual mode Ivan Vecera
2025-04-07 17:32 ` [PATCH 20/28] dpll: zl3073x: Add support to get/set priority on input pins Ivan Vecera
2025-04-07 17:32 ` [PATCH 21/28] dpll: zl3073x: Implement input pin state setting in automatic mode Ivan Vecera
2025-04-07 17:32 ` [PATCH 22/28] dpll: zl3073x: Add support to get/set frequency on input pins Ivan Vecera
2025-04-07 17:32 ` [PATCH 23/28] dpll: zl3073x: Add support to get/set frequency on output pins Ivan Vecera
2025-04-07 17:32 ` [PATCH 24/28] dpll: zl3073x: Read pin supported frequencies from firmware Ivan Vecera
2025-04-07 17:32 ` [PATCH 25/28] dpll: zl3073x: Add support to get phase offset on input pins Ivan Vecera
2025-04-07 17:32 ` [PATCH 26/28] dpll: zl3073x: Add support to get/set phase adjust on pins Ivan Vecera
2025-04-07 17:33 ` [PATCH 27/28] dpll: zl3073x: Add support to get/set esync " Ivan Vecera
2025-04-07 17:33 ` [PATCH 28/28] dpll: zl3073x: Add support to get fractional frequency offset on input pins Ivan Vecera
2025-04-07 18:06 ` [PATCH 00/28] Add Microchip ZL3073x support Andy Shevchenko
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=eeddcda2-efe4-4563-bb2c-70009b374486@redhat.com \
--to=ivecera@redhat.com \
--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=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