public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: quentin.schulz@free-electrons.com (Quentin Schulz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 00/11] add pinmuxing support for pins in AXP209 and AXP813 PMICs
Date: Tue, 5 Dec 2017 15:51:08 +0100	[thread overview]
Message-ID: <8ff99511-eccb-9d9f-ddc0-35b875cce92d@free-electrons.com> (raw)
In-Reply-To: <20171205144647.17594-1-quentin.schulz@free-electrons.com>

Hi all,

Copy pasting of the cover letter done wrong, there are only 9 patches in
this patch series unlike what's specified in the title of the cover
letter for this patch series.

Sorry for the noise.

Quentin

On 05/12/2017 15:46, Quentin Schulz wrote:
> The AXP209 and AXP813 PMICs have several pins (respectively 3 and 2) that can
> be used either as GPIOs or for other purposes (ADC or LDO here).
> 
> We already have a GPIO driver for the GPIO use of those pins on the AXP209.
> Let's "upgrade" this driver to support all the functions these pins can have.
> 
> Then we add support to this driver for the AXP813 which is slighlty different
> (basically a different offset in two registers and one less pin).
> 
> I suggest patches 1 to 8 go through Linus's tree and 9 via Lee's.
> 
> v5:
>   - add reference to pinctrl dt-bindings in driver's dt-binding,
>   - add statement that this driver employs per-pin muxing pattern,
>   - add a patch on top of the patch series to fix checkpatch warnings,
>   - add a few information to the Kconfig to make checkpatch happy,
> 
> v4:
>   - separate dt-binding patch when adding pinctrl feature,
>   - use - instead of _ in DT node name,
>   - remove muxing operation from pinctrl driver when choosing LDO mux in order
>   to not interfere with the regulator framework,
>   - add adc_mux to specify specific mux value for ADC (different between AXP209
>   and AXP813),
>   - misc modifications (header include reordering, unsigned int -> u8,
>   new line removal),
> 
> v3:
>   - add defines for GPIO funcs,
>   - use again get_regs function instead of drv_data (which was implemented in
>   v2),
>   - use of_device_id data for device specific data (gpio_status_offset and pins
>   description),
>   - change compatible from axp813-pctl to axp813-gpio,
>   - use axp81x DT label instead of axp813 since AXP813 and AXP818 are similar,
>   - add dtsi include for all boards embedding axp813/axp818,
> 
> v2:
>   - add support for AXP813 pins,
>   - split into more patches so it is easier to follow the modifications,
>   - reorder of some patches,
>   - register all pins within the same range instead of a range per pin,
> 
> Thanks,
> Quentin
> 
> Quentin Schulz (9):
>   gpio: axp209: switch unsigned variables to unsigned int
>   pinctrl: move gpio-axp209 to pinctrl
>   pinctrl: axp209: add pinctrl features
>   dt-bindings: gpio: gpio-axp209: add pinctrl features
>   pinctrl: axp209: rename everything from gpio to pctl
>   pinctrl: axp209: add programmable gpio_status_offset
>   pinctrl: axp209: add programmable ADC muxing value
>   pinctrl: axp209: add support for AXP813 GPIOs
>   mfd: axp20x: add pinctrl cell for AXP813
> 
>  .../devicetree/bindings/gpio/gpio-axp209.txt       |  49 ++-
>  drivers/gpio/Kconfig                               |   6 -
>  drivers/gpio/Makefile                              |   1 -
>  drivers/gpio/gpio-axp209.c                         | 188 --------
>  drivers/mfd/axp20x.c                               |   3 +
>  drivers/pinctrl/Kconfig                            |  10 +
>  drivers/pinctrl/Makefile                           |   1 +
>  drivers/pinctrl/pinctrl-axp209.c                   | 476 +++++++++++++++++++++
>  8 files changed, 537 insertions(+), 197 deletions(-)
>  delete mode 100644 drivers/gpio/gpio-axp209.c
>  create mode 100644 drivers/pinctrl/pinctrl-axp209.c
> 

-- 
Quentin Schulz, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  parent reply	other threads:[~2017-12-05 14:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05 14:46 [PATCH v5 00/11] add pinmuxing support for pins in AXP209 and AXP813 PMICs Quentin Schulz
2017-12-05 14:46 ` [PATCH v5 1/9] gpio: axp209: switch unsigned variables to unsigned int Quentin Schulz
2017-12-05 14:46 ` [PATCH v5 2/9] pinctrl: move gpio-axp209 to pinctrl Quentin Schulz
2017-12-05 14:46 ` [PATCH v5 3/9] pinctrl: axp209: add pinctrl features Quentin Schulz
2017-12-05 14:46 ` [PATCH v5 4/9] dt-bindings: gpio: gpio-axp209: " Quentin Schulz
2017-12-05 14:46 ` [PATCH v5 5/9] pinctrl: axp209: rename everything from gpio to pctl Quentin Schulz
2017-12-05 14:46 ` [PATCH v5 6/9] pinctrl: axp209: add programmable gpio_status_offset Quentin Schulz
2017-12-05 14:46 ` [PATCH v5 7/9] pinctrl: axp209: add programmable ADC muxing value Quentin Schulz
2017-12-05 14:46 ` [PATCH v5 8/9] pinctrl: axp209: add support for AXP813 GPIOs Quentin Schulz
2017-12-08 13:41   ` Quentin Schulz
2017-12-13  7:36     ` Linus Walleij
2017-12-05 14:46 ` [PATCH v5 9/9] mfd: axp20x: add pinctrl cell for AXP813 Quentin Schulz
2017-12-07  9:34   ` Lee Jones
2017-12-05 14:51 ` Quentin Schulz [this message]
2017-12-07  9:10 ` [PATCH v5 00/11] add pinmuxing support for pins in AXP209 and AXP813 PMICs 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=8ff99511-eccb-9d9f-ddc0-35b875cce92d@free-electrons.com \
    --to=quentin.schulz@free-electrons.com \
    --cc=linux-arm-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox