Netdev List
 help / color / mirror / Atom feed
From: <Manikandan.M@microchip.com>
To: <miquel.raynal@bootlin.com>
Cc: <pratyush@kernel.org>, <mwalle@kernel.org>,
	<takahiro.kuwano@infineon.com>, <richard@nod.at>,
	<vigneshr@ti.com>, <robh@kernel.org>, <krzk+dt@kernel.org>,
	<conor+dt@kernel.org>, <srini@kernel.org>,
	<Nicolas.Ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
	<claudiu.beznea@tuxon.dev>, <linux@armlinux.org.uk>,
	<richardcochran@gmail.com>, <linusw@kernel.org>, <arnd@arndb.de>,
	<aaro.koskinen@iki.fi>, <gregkh@linuxfoundation.org>,
	<mathieu.dubois-briand@bootlin.com>, <michael@walle.cc>,
	<linux-mtd@lists.infradead.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>, <netdev@vger.kernel.org>
Subject: Re: [PATCH v8 5/8] nvmem: layouts: add Microchip/SST SFDP EUI layout driver
Date: Thu, 15 Oct 2026 11:42:43 +0000	[thread overview]
Message-ID: <cd5cb3e9-ffda-40c9-9eb4-18d04abfd56d@microchip.com> (raw)
In-Reply-To: <87fqy8zmtd.fsf@bootlin.com>

Hi Miquel,

Thanks for the review — all valid, I will fix in v9.

On 10/14/26 2:22 PM, Miquel Raynal wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> Hi,
> 
> On 14/10/2026 at 12:10:09 +0530, Manikandan Muralidharan <manikandan.m@microchip.com> wrote:
> 
>> Add an NVMEM layout that exposes the factory-programmed EUI-48 identifier
>> from the Microchip/SST vendor SFDP parameter table (e.g. SST26VF064BEUI)
>> as a "mac-address" cell, for use as a network MAC address. The vendor
>> table is located at runtime via the SFDP NVMEM device (no offset in DT),
>> and a read_post_process callback reverses the LSB-first bytes into
>> canonical MAC order. Binds to an "nvmem-layout" node with compatible
>> "microchip,sst26vf-sfdp-eui".
>>
>> Signed-off-by: Manikandan Muralidharan <manikandan.m@microchip.com>
> 
> Mostly minor nits, see below.
> 
>> --- a/drivers/nvmem/layouts/Makefile
>> +++ b/drivers/nvmem/layouts/Makefile
>> @@ -6,4 +6,5 @@
>>   obj-$(CONFIG_NVMEM_LAYOUTS) += fixed-layout.o
>>   obj-$(CONFIG_NVMEM_LAYOUT_SL28_VPD) += sl28vpd.o
>>   obj-$(CONFIG_NVMEM_LAYOUT_ONIE_TLV) += onie-tlv.o
>> +obj-$(CONFIG_NVMEM_LAYOUT_SST26VF_SFDP_EUI) += sst26vf-sfdp-eui.o
>>   obj-$(CONFIG_NVMEM_LAYOUT_U_BOOT_ENV) += u-boot-env.o
> 
> Not sure this is ordered alphabetically, so in general add it at the end.
> 
>> +/* SFDP header and parameter header, as laid out on the flash. */
>> +struct sfdp_header {
>> +     u8 signature[4];
>> +     u8 minor;
>> +     u8 major;
>> +     u8 nph;
>> +     u8 unused;
>> +};
>> +
>> +struct sfdp_parameter_header {
>> +     u8 id_lsb;
>> +     u8 minor;
>> +     u8 major;
>> +     u8 length;
>> +     u8 parameter_table_pointer[3];
>> +     u8 id_msb;
>> +};
>> +
>> +#define SFDP_SIGNATURE                       0x50444653U
>> +
>> +#define SFDP_PARAM_HEADER_ID(h)              (((h)->id_msb << 8) | (h)->id_lsb)
>> +#define SFDP_PARAM_HEADER_PTP(h)     get_unaligned_le24((h)->parameter_table_pointer)
>> +
>> +/* Microchip (vendor) parameter table identifier: id_msb << 8 | id_lsb. */
> 
> This is not relevant, we saw it just above         ^^^^^^^^^^^^^^^^^^^^^^^
> 
>> +#define SFDP_MCHP_VENDOR_ID          0x01bf
>> +
>> +#define SFDP_MCHP_EUI48_MARKER_OFFSET        0x60
>> +#define SFDP_MCHP_EUI48_MARKER               0x30
>> +#define SFDP_MCHP_EUI48_OFFSET               0x61
>> +
>> +static int sfdp_eui_read_post_process(void *priv, const char *id, int index,
>> +                                   unsigned int offset, void *buf,
>> +                                   size_t bytes)
>> +{
>> +     u8 *data = buf;
>> +     int i;
>> +
> I believe the if against the length is wrong and should be inverted and
> placed here:
> 
>          if (bytes != ETH_ALEN)
>                  return -EINVAL;
> 
> Since lenght does not change, prefer to bail out early.
> 
>> +     /* SFDP stores the address least-significant octet first; reverse it. */
>> +     for (i = 0; i < bytes / 2; i++)
>> +             swap(data[i], data[bytes - 1 - i]);
>> +
>> +     if (bytes == ETH_ALEN && !is_valid_ether_addr(buf))
> 
> Is bytes != ETH_ALEN a valid use case?
> 
>> +             return -EINVAL;
>> +
>> +     return 0;
>> +}
>> +
>> +static int sfdp_eui_find_vendor_table(struct nvmem_device *nvmem, u32 *ptp)
>> +{
>> +     struct sfdp_parameter_header ph;
>> +     struct sfdp_header hdr;
>> +     int nph, i, ret;
>> +
>> +     ret = nvmem_device_read(nvmem, 0, sizeof(hdr), &hdr);
>> +     if (ret < 0)
>> +             return ret;
>> +
>> +     if (get_unaligned_le32(hdr.signature) != SFDP_SIGNATURE)
>> +             return -EINVAL;
>> +
>> +     /* The number of parameter headers (NPH) field is zero-based. */
>> +     nph = hdr.nph;
> 
> nph = hdr.nph + 1 ?
> 
>> +
>> +     for (i = 0; i <= nph; i++) {
> 
> and here the usual i < nph?
> 
>> +             ret = nvmem_device_read(nvmem, sizeof(hdr) + i * sizeof(ph),
>> +                                     sizeof(ph), &ph);
>> +             if (ret < 0)
>> +                     return ret;
>> +
>> +             if (SFDP_PARAM_HEADER_ID(&ph) != SFDP_MCHP_VENDOR_ID)
>> +                     continue;
>> +
>> +             *ptp = SFDP_PARAM_HEADER_PTP(&ph);
>> +             return 0;
>> +     }
>> +
>> +     return -ENOENT;
>> +}
> 
> ...
> 
>> +     info.name = "mac-address";
>> +     info.offset = base + SFDP_MCHP_EUI48_OFFSET;
>> +     info.bytes = ETH_ALEN;
>> +     info.np = of_get_child_by_name(layout_np, "mac-address");
>> +     info.read_post_process = sfdp_eui_read_post_process;
>> +
>> +     ret = nvmem_add_one_cell(nvmem, &info);
>> +     if (ret)
>> +             of_node_put(info.np);
>> +     else
>> +             dev_dbg(dev, "exposed EUI-48 at SFDP offset 0x%x\n", info.offset);
> 
> This one is not really useful anymore.
> 
>> +
>> +     of_node_put(layout_np);
>> +
>> +     return ret;
>> +}
>> +
> 
> Thanks,
> Miquèl


-- 
Thanks and Regards,
Manikandan M.

  reply	other threads:[~2026-10-15 11:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14  6:40 [PATCH v8 0/8] Read MAC address from SST vendor specific SFDP region Manikandan Muralidharan
2026-10-14  6:40 ` [PATCH v8 1/8] dt-bindings: mtd: jedec,spi-nor: allow the SFDP to be exposed via NVMEM Manikandan Muralidharan
2026-10-14  6:40 ` [PATCH v8 2/8] dt-bindings: nvmem: layouts: add Microchip/SST SFDP EUI layout Manikandan Muralidharan
2026-10-14  6:40 ` [PATCH v8 3/8] nvmem: core: take a reference on dev.of_node in nvmem_register() Manikandan Muralidharan
2026-10-14  8:36   ` Miquel Raynal
2026-10-15  9:12   ` Michael Walle
2026-10-15 11:26     ` Manikandan.M
2026-10-14  6:40 ` [PATCH v8 4/8] mtd: spi-nor: sfdp: expose the SFDP as a read-only NVMEM device Manikandan Muralidharan
2026-10-14  8:38   ` Miquel Raynal
2026-10-15  9:21   ` Michael Walle
2026-10-14  6:40 ` [PATCH v8 5/8] nvmem: layouts: add Microchip/SST SFDP EUI layout driver Manikandan Muralidharan
2026-10-14  8:52   ` Miquel Raynal
2026-10-15 11:42     ` Manikandan.M [this message]
2026-10-14  6:40 ` [PATCH v8 6/8] ARM: dts: microchip: sama5d27_wlsom1: use fixed-partitions for QSPI flash Manikandan Muralidharan
2026-10-14  6:40 ` [PATCH v8 7/8] ARM: dts: microchip: sama5d27_wlsom1: read MAC address from QSPI SFDP Manikandan Muralidharan
2026-10-14  6:40 ` [PATCH v8 8/8] ARM: configs: sama5: enable Microchip/SST SFDP EUI NVMEM layout Manikandan Muralidharan

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=cd5cb3e9-ffda-40c9-9eb4-18d04abfd56d@microchip.com \
    --to=manikandan.m@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=alexandre.belloni@bootlin.com \
    --cc=arnd@arndb.de \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=krzk+dt@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=michael@walle.cc \
    --cc=miquel.raynal@bootlin.com \
    --cc=mwalle@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pratyush@kernel.org \
    --cc=richard@nod.at \
    --cc=richardcochran@gmail.com \
    --cc=robh@kernel.org \
    --cc=srini@kernel.org \
    --cc=takahiro.kuwano@infineon.com \
    --cc=vigneshr@ti.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