linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alban <albeu@free.fr>
To: Sergey Ryazanov <ryazanov.s.a@gmail.com>
Cc: Aban Bedel <albeu@free.fr>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	Ralf Baechle <ralf@linux-mips.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	Gabor Juhos <juhosg@openwrt.org>,
	Linux MIPS <linux-mips@linux-mips.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] MIPS: ath79: Remove the unused GPIO function API
Date: Wed, 8 Jul 2015 10:55:14 +0200	[thread overview]
Message-ID: <20150708105514.1156aba3@tock> (raw)
In-Reply-To: <CAHNKnsSgyzQu5uxZHu80X9MRQ5sJ+WEBatv9599QYxBsty66pg@mail.gmail.com>

On Sat, 4 Jul 2015 19:58:32 +0300
Sergey Ryazanov <ryazanov.s.a@gmail.com> wrote:

> 2015-07-03 12:11 GMT+03:00 Alban Bedel <albeu@free.fr>:
> > To prepare moving the GPIO driver to drivers/gpio remove the
> > platform specific pinmux API. As it is not used by any board,
> > and such functionality should better be implemented using the
> > pinmux subsystem just removing it seems to be the best option.
> >
> For reference: OpenWRT uses this functions to activate UART.

The pinctrl-single driver should be usable for all SoC where this code
was used. I haven't tried it yet, but it should only be a matter of
writing the DTS down.

Alban

  reply	other threads:[~2015-07-08  8:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03  9:11 [PATCH 0/2] MIPS: ath79: Move the GPIO driver to drivers/gpio Alban Bedel
2015-07-03  9:11 ` [PATCH 1/2] MIPS: ath79: Remove the unused GPIO function API Alban Bedel
2015-07-04 16:58   ` Sergey Ryazanov
2015-07-08  8:55     ` Alban [this message]
2015-07-16 12:44     ` Linus Walleij
2015-07-16 12:43   ` Linus Walleij
2015-07-03  9:11 ` [PATCH 2/2] MIPS: ath79: Move the GPIO driver to drivers/gpio Alban Bedel
2015-07-06 20:52   ` Linus Walleij
2015-07-06 10:36 ` [PATCH 0/2] " 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=20150708105514.1156aba3@tock \
    --to=albeu@free.fr \
    --cc=gnurou@gmail.com \
    --cc=juhosg@openwrt.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=ryazanov.s.a@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).