From: Alexander Fomichev <fomichev.ru@gmail.com>
To: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: "Jérôme Glisse" <jglisse@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
"Diego Santa Cruz" <Diego.SantaCruz@spinetix.com>,
"Jon Hunter" <jonathanh@nvidia.com>,
"Stable # 4 . 20+" <stable@vger.kernel.org>,
linux-i2c <linux-i2c@vger.kernel.org>,
linux@yadro.com
Subject: Re: [PATCH] misc: eeprom: at24: Always append device id even if label property is set.
Date: Mon, 5 Jul 2021 19:50:49 +0300 [thread overview]
Message-ID: <CAEKnZG5TmoR44dOmK9KmHnWogHvd7MGVXjdXWgew+9smuGEOCg@mail.gmail.com> (raw)
In-Reply-To: <CAMpxmJX_3eu+8Oxg2UgiifwD=qwJYM3-qCqwxseM1mnLbn5fJA@mail.gmail.com>
The proposed patch has been tested and it solves the problem.
Thanks.
Tested-by: Alexander Fomichev <fomichev.ru@gmail.com>
чт, 1 июл. 2021 г. в 19:47, Bartosz Golaszewski <bgolaszewski@baylibre.com>:
>
> On Thu, Jul 1, 2021 at 5:28 PM <jglisse@redhat.com> wrote:
> >
> > From: Jérôme Glisse <jglisse@redhat.com>
> >
> > We need to append device id even if eeprom have a label property set as some
> > platform can have multiple eeproms with same label and we can not register
> > each of those with same label. Failing to register those eeproms trigger
> > cascade failures on such platform (system is no longer working).
> >
> > This fix regression on such platform introduced with 4e302c3b568e
> >
> > Signed-off-by: Jérôme Glisse <jglisse@redhat.com>
> > Cc: Diego Santa Cruz <Diego.SantaCruz@spinetix.com>
> > Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> > Cc: Jon Hunter <jonathanh@nvidia.com>
> > Cc: stable@vger.kernel.org
> > Cc: linux-i2c@vger.kernel.org
> > ---
> > drivers/misc/eeprom/at24.c | 17 +++++++----------
> > 1 file changed, 7 insertions(+), 10 deletions(-)
> >
> > diff --git a/drivers/misc/eeprom/at24.c b/drivers/misc/eeprom/at24.c
> > index 7a6f01ace78a..305ffad131a2 100644
> > --- a/drivers/misc/eeprom/at24.c
> > +++ b/drivers/misc/eeprom/at24.c
> > @@ -714,23 +714,20 @@ static int at24_probe(struct i2c_client *client)
> > }
> >
> > /*
> > - * If the 'label' property is not present for the AT24 EEPROM,
> > - * then nvmem_config.id is initialised to NVMEM_DEVID_AUTO,
> > - * and this will append the 'devid' to the name of the NVMEM
> > - * device. This is purely legacy and the AT24 driver has always
> > - * defaulted to this. However, if the 'label' property is
> > - * present then this means that the name is specified by the
> > - * firmware and this name should be used verbatim and so it is
> > - * not necessary to append the 'devid'.
> > + * We initialize nvmem_config.id to NVMEM_DEVID_AUTO even if the
> > + * label property is set as some platform can have multiple eeproms
> > + * with same label and we can not register each of those with same
> > + * label. Failing to register those eeproms trigger cascade failure
> > + * on such platform.
> > */
> > + nvmem_config.id = NVMEM_DEVID_AUTO;
> > +
> > if (device_property_present(dev, "label")) {
> > - nvmem_config.id = NVMEM_DEVID_NONE;
> > err = device_property_read_string(dev, "label",
> > &nvmem_config.name);
> > if (err)
> > return err;
> > } else {
> > - nvmem_config.id = NVMEM_DEVID_AUTO;
> > nvmem_config.name = dev_name(dev);
> > }
> >
> > --
> > 2.31.1
> >
>
> Cc'ing Alexander Fomichev who reported this issue first.
>
> This is the second time someone raises this problem so it seems that
> this change really broke many existing systems. I will apply this
> patch and send it for stable.
>
> Bart
--
С уважением,
Александр Фомичёв.
prev parent reply other threads:[~2021-07-05 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 15:28 [PATCH] misc: eeprom: at24: Always append device id even if label property is set jglisse
2021-07-01 16:47 ` Bartosz Golaszewski
2021-07-05 16:50 ` Alexander Fomichev [this message]
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=CAEKnZG5TmoR44dOmK9KmHnWogHvd7MGVXjdXWgew+9smuGEOCg@mail.gmail.com \
--to=fomichev.ru@gmail.com \
--cc=Diego.SantaCruz@spinetix.com \
--cc=bgolaszewski@baylibre.com \
--cc=jglisse@redhat.com \
--cc=jonathanh@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@yadro.com \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).