[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZrLZZwpVCzo_Ms2=7SqUoryt-6OtF7ePhGp4kwJgDgXQ@mail.gmail.com>
Date: Tue, 22 Apr 2014 14:48:04 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Antoine Ténart <antoine.tenart@...e-electrons.com>
Cc: Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
zmxu@...vell.com, Jisheng Zhang <jszhang@...vell.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RESEND 1/5] pinctrl: allows not to define the
get_group_pins operation
On Thu, Apr 10, 2014 at 3:07 PM, Antoine Ténart
<antoine.tenart@...e-electrons.com> wrote:
> When using a group only pinctrl driver, which does not have any
> information on the pins it is useless to define a get_group_pins
> always returning an empty list of pins.
>
> When not using get_group_pin[1], a driver must implement it so
> pins = NULL and num_pins = 0. This patch makes it the default
> behaviour if not defined in the pinctrl driver when used in
> pinmux enable and disable funtions and in pinctrl_groups_show.
>
> It also adds a check in pinctrl_get_group_pins and return -EINVAL if
> not defined. This function is called in the gpiolib when adding when
> pingroup range. It cannot be used if no group is defined, so this seams
> reasonable.
>
> [1] get_group_pin(struct pinctrl_dev *pctldev,
> unsigned selector,
> const unsigned **pins,
> unsigned *num_pins);
>
> Signed-off-by: Antoine Ténart <antoine.tenart@...e-electrons.com>
OK makes perfect sense.
Patch applied.
Can you please check the Documentation/pinctrl.txt to see
if anything needs to be updated due to this?
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists