linux-kernel - Re: [PATCH net-next v2 2/2] misc: Add Renesas Synchronization Management Unit (SMU) 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <YG6gdRiEkiYxKKm9@kroah.com>
Date:   Thu, 8 Apr 2021 08:19:33 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Min Li <min.li.xe@...esas.com>
Cc:     "derek.kiernan@...inx.com" <derek.kiernan@...inx.com>,
        "dragan.cvetic@...inx.com" <dragan.cvetic@...inx.com>,
        "arnd@...db.de" <arnd@...db.de>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next v2 2/2] misc: Add Renesas Synchronization
 Management Unit (SMU) support

On Wed, Apr 07, 2021 at 07:43:44PM +0000, Min Li wrote:
> > 
> > Why do you need 4 files here?  Can't you do this all in one?  There's no need
> > for such a small driver to be split up, that just causes added complexity and
> > makes things harder to review and understand.
> > 
> 
> We will add more functions and boards down the road. So the abstraction here is for future consideration  

Do not add additional complexity today for stuff that you do not need
today.  Add it when you need it.

> > >  include/uapi/linux/rsmu.h |  64 +++++++++++
> > 
> > Where are you documenting these new custom ioctls?  And why do you even
> > need them?
> > 
> 
> Other than comments in the header itself, no additional documenting. Do you know if Linux has specific place to document custom ioctls? 
> Renesas software needs to access these ioctls to provide GNSS assisted partial timing support. More specifically, RSMU_GET_STATE would tell us if a specific DPLL
> is locked to GNSS and RSMU_GET_FFO would tell us how much of frequency offset for the DPLL to lock to the GNSS.

Please provide some sort of documentation and at the least, a pointer to
the software that uses this so that we can see how it all ties together.

thanks,

greg k-h