linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Alban Bedel <albeu@free.fr>
Cc: "Linux MIPS" <linux-mips@linux-mips.org>,
	"Ralf Baechle" <ralf@linux-mips.org>,
	"Hauke Mehrtens" <hauke@hauke-m.de>,
	"Rafał Miłecki" <zajec5@gmail.com>,
	"Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>,
	"Tejun Heo" <tj@kernel.org>,
	"Alexandre Courbot" <gnurou@gmail.com>,
	"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
	"Florian Fainelli" <florian@openwrt.org>,
	"Manuel Lauss" <manuel.lauss@gmail.com>,
	"Joe Perches" <joe@perches.com>,
	"Daniel Walter" <dwalter@google.com>,
	"Sergey Ryazanov" <ryazanov.s.a@gmail.com>,
	"Huacai Chen" <chenhc@lemote.com>,
	"Andrew Bresticker" <abrestic@chromium.org>,
	"James Hartley" <james.hartley@imgtec.com>,
	"Paul Burton" <paul.burton@imgtec.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Wolfram Sang" <wsa@the-dreams.de>,
	"Simon Horman" <horms+renesas@verge.net.au>,
	"Geert Uytterhoeven" <geert@linux-m68k.org>,
	"Varka Bhadram" <varkabhadram@gmail.com>
Subject: Re: [PATCH] MIPS: Remove all the uses of custom gpio.h
Date: Mon, 3 Aug 2015 09:13:27 +0200	[thread overview]
Message-ID: <CACRpkdbUhYysC+mGuJY6Y8kd18LQLoWu+av81+ZD4UZo2nM-Yw@mail.gmail.com> (raw)
In-Reply-To: <1438277338-7246-1-git-send-email-albeu@free.fr>

On Thu, Jul 30, 2015 at 7:28 PM, Alban Bedel <albeu@free.fr> wrote:

> Currently CONFIG_ARCH_HAVE_CUSTOM_GPIO_H is defined for all MIPS
> machines, and each machine type provides its own gpio.h. However
> only a handful really implement the GPIO API, most just forward
> everythings to gpiolib.
>
> The Alchemy machine is notable as it provides a system to allow
> implementing the GPIO API at the board level. But it is not used by
> any board currently supported, so it can also be removed.
>
> For most machine types we can just remove the custom gpio.h, as well
> as the custom wrappers if some exists. Some of the code found in
> the wrappers must be moved to the respective GPIO driver.
>
> A few more fixes are need in some drivers as they rely on linux/gpio.h
> to provides some machine specific definitions, or used asm/gpio.h
> instead of linux/gpio.h for the gpio API.
>
> Signed-off-by: Alban Bedel <albeu@free.fr>
> ---
>
> This patch is based on my previous serie:
> "MIPS: ath79: Move the GPIO driver to drivers/gpio".
>
> It supercede my previous patch named:
> "MIPS: Remove most of the custom gpio.h"
>
> Compared to the previous patch:
> * Fixed gpio_to_irq on jz4740 and rb532
> * Cleaned up alchemy as well
> * Removed asm/gpio.h
>
> For testing I tried to build all mips defconfig, however my toolchain
> couldn't handle a few configs: ip28 malta_qemu_32r6 maltasmvp_eva
> sead3micro. If somebody can test these that would be more than welcome.
>
> Now a few stats about the state of CONFIG_ARCH_HAVE_CUSTOM_GPIO_H
> after appling this patch. Of the 31 supportd arch, 15 still have
> asm/gpio.h, of these 9 are just a "#warning Include linux/gpio.h
> instead of asm/gpio.h". So we have 6 arch left: arm, avr32, blackfin,
> m68k, sh and unicore32. But only m68k and unicore32 really provides
> custom wrappers, all the others only forward to gpiolib.
>
> On the drivers side we only have 13 occurences of '#include
> <asm/gpio.h>' left, mostly in drivers used on ARM SoC.
>
> So the work left to phase out the legacy GPIO is really not that much
> anymore.

Very good job being done here.
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>

I guess this better go in through the MIPS tree.
Given all the OpenWRT ports using MIPS this is excellent
progress for a large hobbyist community.

Yours,
Linus Walleij

  parent reply	other threads:[~2015-08-03  7:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-30 17:28 [PATCH] MIPS: Remove all the uses of custom gpio.h Alban Bedel
2015-07-30 20:13 ` Jonas Gorski
2015-07-31  6:04 ` Manuel Lauss
2015-08-03  7:13 ` Linus Walleij [this message]
2015-08-03  7:23   ` Ralf Baechle
2015-08-03 11:25     ` Linus Walleij

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CACRpkdbUhYysC+mGuJY6Y8kd18LQLoWu+av81+ZD4UZo2nM-Yw@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=abrestic@chromium.org \
    --cc=albeu@free.fr \
    --cc=b.zolnierkie@samsung.com \
    --cc=bhelgaas@google.com \
    --cc=chenhc@lemote.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dwalter@google.com \
    --cc=florian@openwrt.org \
    --cc=geert@linux-m68k.org \
    --cc=gnurou@gmail.com \
    --cc=hauke@hauke-m.de \
    --cc=horms+renesas@verge.net.au \
    --cc=james.hartley@imgtec.com \
    --cc=joe@perches.com \
    --cc=linux-mips@linux-mips.org \
    --cc=manuel.lauss@gmail.com \
    --cc=paul.burton@imgtec.com \
    --cc=ralf@linux-mips.org \
    --cc=ryazanov.s.a@gmail.com \
    --cc=tj@kernel.org \
    --cc=varkabhadram@gmail.com \
    --cc=wsa@the-dreams.de \
    --cc=zajec5@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).