linux-kernel - RE: [RFC 02/11] soc: Add Realtek chip info driver for RTD1195 and RTD1295

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <0cd79474f707499d8c5d58b4f3250a68@realtek.com>
Date:   Fri, 3 Jan 2020 05:07:12 +0000
From:   Stanley Chang[昌育德] 
        <stanley_chang@...ltek.com>
To:     James Tai <james.tai@...ltek.com>,
        Andreas Färber <afaerber@...e.de>,
        "linux-realtek-soc@...ts.infradead.org" 
        <linux-realtek-soc@...ts.infradead.org>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>
Subject: RE: [RFC 02/11] soc: Add Realtek chip info driver for RTD1195 and RTD1295

Hi Andreas,

I have tested this patch in my local platform.
And this patch is fine and it can work.

> 
> Add Stanley Chang for review.
> 
> > Add a soc bus driver to print chip model and revision details.
> >
> > Revisions from downstream drivers/soc/realtek/rtd{119x,129x}/rtk_chip.c.
> >
> > Signed-off-by: Andreas Färber <afaerber@...e.de>
> > ---
> >  Naming: What to call the family vs. soc_id?
> >
> >  drivers/soc/Kconfig          |   1 +
> >  drivers/soc/Makefile         |   1 +
> >  drivers/soc/realtek/Kconfig  |  13 ++++
> >  drivers/soc/realtek/Makefile |   2 +
> >  drivers/soc/realtek/chip.c   | 164
> > +++++++++++++++++++++++++++++++++++++++++++
> >  5 files changed, 181 insertions(+)
> >  create mode 100644 drivers/soc/realtek/Kconfig  create mode 100644
> > drivers/soc/realtek/Makefile  create mode 100644
> > drivers/soc/realtek/chip.c

Tested-by: Stanley Chang <stanley_chang@...ltek.com>
Reviewed-by: Stanley Chang <stanley_chang@...ltek.com>

Thanks,
Stanley