From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v2 0/2] pinctrl: meson: prepare for new SoC
Date: Wed, 11 Oct 2017 17:15:29 -0700 [thread overview]
Message-ID: <7hshepfcgu.fsf@baylibre.com> (raw)
In-Reply-To: <20171011120230.30483-1-jbrunet@baylibre.com> (Jerome Brunet's message of "Wed, 11 Oct 2017 14:02:28 +0200")
Jerome Brunet <jbrunet@baylibre.com> writes:
> The goal of this patchset is to prepare meson pinctrl driver to
> add a new meson SoC support. This new SoC will share the same pinconf/gpio
> registers but the pinmux part will be slightly different.
>
> First patch allows to compile and ship only the necessary pinctrl drivers,
> depending on the architecture and configuration needs. This should save
> a bit of memory.
>
> Second patch provide a way to deal with a different pinmux scheme, while
> reusing most of the meson pinctrl driver.
>
> Linus, FYI, this series depends on the meson changes you have already
> merged in this cycle.
>
> Change since v1: [0]
> * Use of_device_get_match_data() in patch
> * Change pmx naming scheme for the SoC parts
>
> [0]: https://lkml.kernel.org/r/20171009101747.16940-1-jbrunet at baylibre.com
>
> Jerome Brunet (2):
> pinctrl: meson: separate soc drivers
> pinctrl: meson: rework pinmux ops
Reviewed-by: Kevin Hilman <khilman@baylibre.com>
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Carlo Caione <carlo@caione.org>,
linux-gpio@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] pinctrl: meson: prepare for new SoC
Date: Wed, 11 Oct 2017 17:15:29 -0700 [thread overview]
Message-ID: <7hshepfcgu.fsf@baylibre.com> (raw)
In-Reply-To: <20171011120230.30483-1-jbrunet@baylibre.com> (Jerome Brunet's message of "Wed, 11 Oct 2017 14:02:28 +0200")
Jerome Brunet <jbrunet@baylibre.com> writes:
> The goal of this patchset is to prepare meson pinctrl driver to
> add a new meson SoC support. This new SoC will share the same pinconf/gpio
> registers but the pinmux part will be slightly different.
>
> First patch allows to compile and ship only the necessary pinctrl drivers,
> depending on the architecture and configuration needs. This should save
> a bit of memory.
>
> Second patch provide a way to deal with a different pinmux scheme, while
> reusing most of the meson pinctrl driver.
>
> Linus, FYI, this series depends on the meson changes you have already
> merged in this cycle.
>
> Change since v1: [0]
> * Use of_device_get_match_data() in patch
> * Change pmx naming scheme for the SoC parts
>
> [0]: https://lkml.kernel.org/r/20171009101747.16940-1-jbrunet@baylibre.com
>
> Jerome Brunet (2):
> pinctrl: meson: separate soc drivers
> pinctrl: meson: rework pinmux ops
Reviewed-by: Kevin Hilman <khilman@baylibre.com>
next prev parent reply other threads:[~2017-10-12 0:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 12:02 [PATCH v2 0/2] pinctrl: meson: prepare for new SoC Jerome Brunet
2017-10-11 12:02 ` Jerome Brunet
2017-10-11 12:02 ` [PATCH v2 1/2] pinctrl: meson: separate soc drivers Jerome Brunet
2017-10-11 12:02 ` Jerome Brunet
2017-10-11 12:02 ` [PATCH v2 2/2] pinctrl: meson: rework pinmux ops Jerome Brunet
2017-10-11 12:02 ` Jerome Brunet
2017-10-12 0:15 ` Kevin Hilman [this message]
2017-10-12 0:15 ` [PATCH v2 0/2] pinctrl: meson: prepare for new SoC Kevin Hilman
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=7hshepfcgu.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linus-amlogic@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.