Re: [PATCH v3 3/3] nvmem: uniphier-efuse: Add ti,am62p-efuse compatible

[Judith Mendez]

Hi,

On 9/13/26 3:57 AM, Krzysztof Kozlowski wrote:
> On Thu, Sep 10, 2026 at 10:55:09AM -0500, Judith Mendez wrote:
> > Add ti,am62p-efuse compatible to uniphier-efuse. Leverage the
> > nvmem provider to supply silicon revision information from GP_SW
> > efuse registers on AM62p device.
> >
> > Signed-off-by: Judith Mendez <jm@xxxxxx>
> > Reviewed-by: Kunihiko Hayashi <hayashi.kunihiko@xxxxxxxxxxxxx>
> > ---
> > Changes since v2:
> > - Add Kunihiko's review tag
> > ---
> >   drivers/nvmem/uniphier-efuse.c | 1 +
> >   1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/nvmem/uniphier-efuse.c b/drivers/nvmem/uniphier-efuse.c
> > index 85f9372fb97ca..d0953b99d7e18 100644
> > --- a/drivers/nvmem/uniphier-efuse.c
> > +++ b/drivers/nvmem/uniphier-efuse.c
> > @@ -59,6 +59,7 @@ static int uniphier_efuse_probe(struct platform_device *pdev)
> >   
> >   static const struct of_device_id uniphier_efuse_of_match[] = {
> >   	{ .compatible = "socionext,uniphier-efuse",},
> > +	{ .compatible = "ti,am62p-efuse",},
>
> Why do you need this change?

I think series has been merged already, but I guess ti,am62p-efuse
is not really required anymore due to fallback compatible logic we
added, but it helps provide a bit of clarity and ease of use. Which
helps in this case since the driver name might confuse the reader
since it is not generic driver name.

If you truly have a problem with current setup, LMK, thanks for
your review though.

~ Judith