public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Eric Curtin <ecurtin@redhat.com>
Cc: srinivas.kandagatla@linaro.org, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org, "Arnd Bergmann" <arnd@arndb.de>,
	regressions@lists.linux.dev, "Rafał Miłecki" <rafal@milecki.pl>,
	"Chen-Yu Tsai" <wenst@chromium.org>,
	asahi@lists.linux.dev, "Sven Peter" <sven@svenpeter.dev>
Subject: Re: [PATCH] nvmem: include bit index in cell sysfs file name
Date: Tue, 13 Feb 2024 20:20:45 +0100	[thread overview]
Message-ID: <20240213202045.1e823a6c@xps-13> (raw)
In-Reply-To: <CAOgh=FwFMaYvTwmqeOQrqHq2XANxghZbTuY3+SgFx_ozpysBOg@mail.gmail.com>

Hi,

ecurtin@redhat.com wrote on Fri, 9 Feb 2024 16:49:22 +0000:

> On Fri, 9 Feb 2024 at 16:43, <srinivas.kandagatla@linaro.org> wrote:
> >
> > From: Arnd Bergmann <arnd@arndb.de>
> >
> > Creating sysfs files for all Cells caused a boot failure for linux-6.8-rc1 on
> > Apple M1, which (in downstream dts files) has multiple nvmem cells that use the
> > same byte address. This causes the device probe to fail with
> >
> > [    0.605336] sysfs: cannot create duplicate filename '/devices/platform/soc@200000000/2922bc000.efuse/apple_efuses_nvmem0/cells/efuse@a10'
> > [    0.605347] CPU: 7 PID: 1 Comm: swapper/0 Tainted: G S                 6.8.0-rc1-arnd-5+ #133
> > [    0.605355] Hardware name: Apple Mac Studio (M1 Ultra, 2022) (DT)
> > [    0.605362] Call trace:
> > [    0.605365]  show_stack+0x18/0x2c
> > [    0.605374]  dump_stack_lvl+0x60/0x80
> > [    0.605383]  dump_stack+0x18/0x24
> > [    0.605388]  sysfs_warn_dup+0x64/0x80
> > [    0.605395]  sysfs_add_bin_file_mode_ns+0xb0/0xd4
> > [    0.605402]  internal_create_group+0x268/0x404
> > [    0.605409]  sysfs_create_groups+0x38/0x94
> > [    0.605415]  devm_device_add_groups+0x50/0x94
> > [    0.605572]  nvmem_populate_sysfs_cells+0x180/0x1b0
> > [    0.605682]  nvmem_register+0x38c/0x470
> > [    0.605789]  devm_nvmem_register+0x1c/0x6c
> > [    0.605895]  apple_efuses_probe+0xe4/0x120
> > [    0.606000]  platform_probe+0xa8/0xd0
> >
> > As far as I can tell, this is a problem for any device with multiple cells on
> > different bits of the same address. Avoid the issue by changing the file name
> > to include the first bit number.
> >
> > Fixes: 0331c611949f ("nvmem: core: Expose cells through sysfs")
> > Link: https://github.com/AsahiLinux/linux/blob/bd0a1a7d4/arch/arm64/boot/dts/apple/t600x-dieX.dtsi#L156
> > Cc: regressions@lists.linux.dev
> > Cc: Miquel Raynal <miquel.raynal@bootlin.com>
> > Cc: Rafał Miłecki <rafal@milecki.pl>
> > Cc: Chen-Yu Tsai <wenst@chromium.org>
> > Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Cc: asahi@lists.linux.dev
> > Cc: Sven Peter <sven@svenpeter.dev>
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> > Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>  
> 

My R-by must have been lost, here it is again:

Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>

Thanks,
Miquèl

  reply	other threads:[~2024-02-13 19:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-09 16:34 [PATCH] nvmem: include bit index in cell sysfs file name srinivas.kandagatla
2024-02-09 16:49 ` Eric Curtin
2024-02-13 19:20   ` Miquel Raynal [this message]
2024-02-14 15:28 ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2024-01-22 15:34 Arnd Bergmann
2024-01-22 16:55 ` Srinivas Kandagatla
2024-02-09  9:09   ` Linux regression tracking (Thorsten Leemhuis)
2024-02-09 10:20     ` Arnd Bergmann
2024-01-24 17:22 ` Miquel Raynal
2024-01-24 19:49   ` Arnd Bergmann
2024-01-24 22:11     ` Miquel Raynal
2024-01-25 12:15       ` Arnd Bergmann
2024-01-25 13:06         ` Miquel Raynal

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=20240213202045.1e823a6c@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=arnd@arndb.de \
    --cc=asahi@lists.linux.dev \
    --cc=ecurtin@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafal@milecki.pl \
    --cc=regressions@lists.linux.dev \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=sven@svenpeter.dev \
    --cc=wenst@chromium.org \
    /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