[Top] [All Lists]

Re: [PATCH] pinctrl: Pass all configs to driver on pin_config_set()

To: Sherman Yin <>
Subject: Re: [PATCH] pinctrl: Pass all configs to driver on pin_config_set()
From: Linus Walleij <>
Date: Thu, 22 Aug 2013 00:14:02 +0200
Cc: "" <>, "" <>,,, Christian Daudt <>, Markus Mayer <>, James Hogan <>
In-reply-to: <>
List-archive: <>
List-help: <>
List-id: linux-mips <>
List-owner: <>
List-post: <>
List-software: Ecartis version 1.0.0
List-subscribe: <>
List-unsubscribe: <>
Original-recipient: rfc822;
References: <>
Hi Sherman,

On Fri, Aug 16, 2013 at 12:42 AM, Sherman Yin <> wrote:

> When setting pin configuration in the pinctrl framework, pin_config_set() or
> pin_config_group_set() is called in a loop to set one configuration at a time
> for the specified pin or group.
> This patch 1) removes the loop and 2) changes the API to pass the whole pin
> config array to the driver.  It is now up to the driver to loop through the
> configs.  This allows the driver to potentially combine configs and reduce the
> number of writes to pin config registers.
> Signed-off-by: Sherman Yin <>
> Reviewed-by: Christian Daudt <>
> Reviewed-by: Matt Porter <>
> Change-Id: I99cbfa2ae7b774456eb71edb276711b1ddcd42c8
> ---
> Please refer to the discussion with Linus W. "[PATCH] ARM: Adds pin config API
> to set all configs in one function" here:
> All c files changed have been build-tested to verify the change compiles and
> that the corresponding .o are successfully generated.

Good work! This is obviously the right thing to do and it's looking
very good.

Right now this does not apply to my "devel" branch, so I'd like you
to rebase on that right now. (This is what will go into v3.12).

This is also late in the development cycle so I believe this is going to
be v3.13 material unless there are more release candidates.

You can also hold on until after the v3.12 merge window and then
rebase it and we'll merge it as a first patch in the v3.13 development

What do you say?

Linus Walleij

<Prev in Thread] Current Thread [Next in Thread>