linux-kernel - Re: [PATCH] rtc: rtc-isl12022: add isl12020 device support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20210923183934.09cfb251@monster.powergraphx.local>
Date:   Thu, 23 Sep 2021 16:39:34 +0000
From:   Wilken Gottwalt <wilken.gottwalt@...teo.net>
To:     Alexandre Belloni <alexandre.belloni@...tlin.com>
Cc:     linux-kernel@...r.kernel.org,
        Alessandro Zummo <a.zummo@...ertech.it>,
        Joerg Reiling <joerg.reiling@...optik.com>,
        linux-rtc@...r.kernel.org
Subject: Re: [PATCH] rtc: rtc-isl12022: add isl12020 device support

On Thu, 23 Sep 2021 17:36:55 +0200
Alexandre Belloni <alexandre.belloni@...tlin.com> wrote:

> Hi,
> 
> On 23/09/2021 12:53:49+0000, Wilken Gottwalt wrote:
> > Adds the isl12020 device, which is fully compatible to isl12022.
> > 
> 
> Do you know what is differing between both parts? If there is nothing
> relevant to linux, maybe we could just avoid adding a new compatible
> string.

Hmm no, there are no changes relevant for a driver. So yeah, you are
right, that only would add the possibility to use isl12020 in the device
tree instead of isl12022. Oh boy, this is kind of embarrassing, just
didn't think about it. ;-) But there will be more patches, the chip
also have temp sensor exposable by hwmon.

> > Signed-off-by: Wilken Gottwalt <wilken.gottwalt@...teo.net>
> > Signed-off-by: Joerg Reiling <joerg.reiling@...optik.com>
> > ---
> >  drivers/rtc/rtc-isl12022.c | 3 +++
> >  1 file changed, 3 insertions(+)
> > 
> > diff --git a/drivers/rtc/rtc-isl12022.c b/drivers/rtc/rtc-isl12022.c
> > index 961bd5d1d109..c62770ec99c9 100644
> > --- a/drivers/rtc/rtc-isl12022.c
> > +++ b/drivers/rtc/rtc-isl12022.c
> > @@ -257,6 +257,8 @@ static int isl12022_probe(struct i2c_client *client,
> >  static const struct of_device_id isl12022_dt_match[] = {
> >  	{ .compatible = "isl,isl12022" }, /* for backward compat., don't use */
> >  	{ .compatible = "isil,isl12022" },
> > +	{ .compatible = "isl,isl12020" }, /* for backward compat., don't use */
> 
> Please, do not add this compatible string.
> 
> > +	{ .compatible = "isil,isl12020" },
> 
> You also need to document this string in Documentation/devicetree/bindings/rtc/trivial-rtc.yaml

I only checked the isl* bindings. Why is there no specific isl12022 yaml
file like the other isl* chips have?

> >  	{ },
> >  };
> >  MODULE_DEVICE_TABLE(of, isl12022_dt_match);
> > @@ -264,6 +266,7 @@ MODULE_DEVICE_TABLE(of, isl12022_dt_match);
> >  
> >  static const struct i2c_device_id isl12022_id[] = {
> >  	{ "isl12022", 0 },
> > +	{ "isl12020", 0 },
> >  	{ }
> >  };
> >  MODULE_DEVICE_TABLE(i2c, isl12022_id);
> > -- 
> > 2.33.0
> > 
>