linux-kernel - Re: Re: [PATCH V2] gpio: mmp: add GPIO driver for Marvell MMP series

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: <CACRpkdaP5gZW84WNxKvPPehx7DzW+heGy8SgG_=f4x3RSs6jNw@mail.gmail.com>
Date:	Wed, 18 Mar 2015 09:42:28 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Chao Xie <xiechao_mail@....com>
Cc:	Chao Xie <chao.xie@...vell.com>, Rob Herring <robh@...nel.org>,
	Andrew Ruder <andy@...uder.net>,
	Eric Miao <eric.y.miao@...il.com>,
	Alexandre Courbot <gnurou@...il.com>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Haojian Zhuang <haojian.zhuang@...il.com>
Subject: Re: Re: [PATCH V2] gpio: mmp: add GPIO driver for Marvell MMP series

On Wed, Mar 18, 2015 at 6:09 AM, Chao Xie <xiechao_mail@....com> wrote:
> At 2015-03-17 18:25:24, "Linus Walleij" <linus.walleij@...aro.org> wrote:

>>So this driver duplicates drivers/gpio/gpio-pxa.c in some sense but
>>is nicer and cleaner and thus an incentive for me to merge it.
>>At the same time I don't want two drivers for essentially the same
>>hardware and in that way I would prefer to clean up the PXA driver.
>>
>>But I don't know how close the PXA and MMP drivers really are.
>>
>>Will it also cover MMP2 that is currently using by the PXA driver?
>>
>>Is it really complicated to migrate gpio-pxa to GPIOLIB_IRQCHIP?
>>
>>I guess you should also delete the compatible string and
>>compatibility code in drivers/gpio/gpio-pxa.c (as a separate patch
>>in this series) and merge this along with some defconfig
>>changes that activates this by default for the MMP machines?
>
>
> I will ask Haojian to comment at it when send out V3 patch.
> pxa and mmp are two different series.
> First pxa is Intel's product, and after Intel sell its xscale to
> marvell, the SOC series become mmp. The SOC design has
> many differences.

OK I knew there was some story like this ... and before Intel
the chipset now known as PXA was StrongARM-related and was
a Digital product right?

> now mmp gpio has some registers kept in order to use the
> old pxa driver, but silicon designer warned us that it is better
> to use the new register interfaces.
>
> The major differences are:
> For all the edge detecting setting/clearing, level setting/clearing,
> direction setting/clearing, mmp has
> separated registers

So the new IP is obviously derived from the old PXA IP and
should preferably use the same driver, just with some tweaks.
It would be better if the PXA driver was evolved to cover the new
registers for the MMP.

Well I guess if *all* registers start to be at a different offset (etc)
then there is no point in having the same driver. But that seems
not to be the case.

Run-time adaptable drivers that cover a wide range of hardware
is very nice for me as a maintainer, mostly because I don't
need to fix the same bug in a myriad of places.

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/