linux-kernel - Re: [PATCH 1/2] gpio: Add support for IDT 79RC3243x GPIO controller

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: <CAHp75Vf921iQUR=VgMXTD-M_Ah+8UeAmKXXqgvB8WFz58pQ5Qg@mail.gmail.com>
Date:   Wed, 21 Apr 2021 12:54:53 +0300
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Thomas Bogendoerfer <tsbogend@...ha.franken.de>
Cc:     Linus Walleij <linus.walleij@...aro.org>,
        Bartosz Golaszewski <bgolaszewski@...libre.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>
Subject: Re: [PATCH 1/2] gpio: Add support for IDT 79RC3243x GPIO controller

On Wed, Apr 21, 2021 at 12:19 PM Thomas Bogendoerfer
<tsbogend@...ha.franken.de> wrote:
> On Wed, Apr 21, 2021 at 11:48:59AM +0300, Andy Shevchenko wrote:
> > On Wed, Apr 21, 2021 at 11:32 AM Thomas Bogendoerfer
> > <tsbogend@...ha.franken.de> wrote:
> > > On Wed, Apr 21, 2021 at 11:09:51AM +0300, Andy Shevchenko wrote:
> > > > On Tuesday, April 20, 2021, Thomas Bogendoerfer <tsbogend@...ha.franken.de>
> > > > wrote:
> > > >
> > > > > IDT 79RC3243x SoCs integrated a gpio controller, which handles up
> > > > > to 32 gpios. All gpios could be used as interrupt source.
> > > >
> > > >
> > > >
> > > > I would recommend looking for latest new drivers in GPIO subsystem to see
> > > > how you may improve yours.
> > >
> > > Could give me a better pointer to it ? I looked at a lot of gpio driver
> > > and took what fitted best.
> > >
> > > > Here just one question, why it can not be a module
> > >
> > > that's probably doable...
> > >
> > > > why arch_initcall() is used
> > >
> > > without that interrupts weren't avaiable early enough.
> > >
> > > > and why you put a dead code into it (see the first part of the
> > > > question)?
> > >
> > > hmm, pointer please ?
> >
> > It's already in the question above, do your homework :-)
>
> is this some sort of joke I'm not getting ?

Maybe, but no, it's not a joke. You asked where the dead code is. I
answered that you as the author of the code should have a better
understanding of what you are doing. I can admit that it's hard to
cover all aspects of the kernel programming in one go, but at least
this part is a low hanging fruit.

As I promised you, I will do a deep review later on, I'm giving you
time to find issues yourself. That's how you may actually learn the
things. It's solely your choice to follow or not, my promise will be
kept and you will get an answer anyway.

> git log --oneline drivers/gpio/Makefile
>
> 2ad74f40dacc gpio: visconti: Add Toshiba Visconti GPIO support
>
> that's the latest driver added in v5.12-rc8. Is that a good one ?

Briefly looking, I haven't found any problems with that code. It looks neat.

-- 
With Best Regards,
Andy Shevchenko