Re: [RFT PATCH 5/6] pinctrl: meson: use gpio-ranges from DT
Neil Armstrong writes: > On 03/28/2017 11:30 AM, Linus Walleij wrote: >> On Thu, Mar 23, 2017 at 5:27 PM, Neil Armstrong >> wrote: >> >> '> When trying to add a gpio-hog, we enter a weird loop where the gpio-ranges >>> is needed when gpiochip_add_data() is called but in the current >>> implementation >>> the ranges are added from the driver afterwards. >>> >>> A simple solution is to rely on the DR gpio-ranges attribute and remove the >>> call to gpiochip_add_pin_range(). >>> >>> Signed-off-by: Neil Armstrong >> >> This is fine once the ranges have been applied to the device trees I guess. >> >> Tell me when you want me to merge this. >> >> Yours, >> Linus Walleij >> > > Hi Linus, > > Kevin should merge the DT patches since they have now Tested and Reviewed > by's, so you can merge it now if you can. > Since it will live in you pinctrl tree, it will only impact linux-next until > Kevin merges them. I've applied the DT patches now (branch: v4.12/dt64) Kevin
Re: [RFT PATCH 5/6] pinctrl: meson: use gpio-ranges from DT
On Thu, Mar 23, 2017 at 5:27 PM, Neil Armstrong wrote: > When trying to add a gpio-hog, we enter a weird loop where the gpio-ranges > is needed when gpiochip_add_data() is called but in the current implementation > the ranges are added from the driver afterwards. > > A simple solution is to rely on the DR gpio-ranges attribute and remove the > call to gpiochip_add_pin_range(). > > Signed-off-by: Neil Armstrong Patch applied. Yours, Linus Walleij
Re: [RFT PATCH 5/6] pinctrl: meson: use gpio-ranges from DT
On Thu, Mar 23, 2017 at 5:27 PM, Neil Armstrong wrote: '> When trying to add a gpio-hog, we enter a weird loop where the gpio-ranges > is needed when gpiochip_add_data() is called but in the current implementation > the ranges are added from the driver afterwards. > > A simple solution is to rely on the DR gpio-ranges attribute and remove the > call to gpiochip_add_pin_range(). > > Signed-off-by: Neil Armstrong This is fine once the ranges have been applied to the device trees I guess. Tell me when you want me to merge this. Yours, Linus Walleij
Re: [RFT PATCH 5/6] pinctrl: meson: use gpio-ranges from DT
On 03/28/2017 11:30 AM, Linus Walleij wrote: > On Thu, Mar 23, 2017 at 5:27 PM, Neil Armstrong > wrote: > > '> When trying to add a gpio-hog, we enter a weird loop where the gpio-ranges >> is needed when gpiochip_add_data() is called but in the current >> implementation >> the ranges are added from the driver afterwards. >> >> A simple solution is to rely on the DR gpio-ranges attribute and remove the >> call to gpiochip_add_pin_range(). >> >> Signed-off-by: Neil Armstrong > > This is fine once the ranges have been applied to the device trees I guess. > > Tell me when you want me to merge this. > > Yours, > Linus Walleij > Hi Linus, Kevin should merge the DT patches since they have now Tested and Reviewed by's, so you can merge it now if you can. Since it will live in you pinctrl tree, it will only impact linux-next until Kevin merges them. Thanks, Neil
Re: [RFT PATCH 5/6] pinctrl: meson: use gpio-ranges from DT
On 03/23/2017 09:09 PM, Martin Blumenstingl wrote: > Hi Neil, > > On Thu, Mar 23, 2017 at 5:27 PM, Neil Armstrong > wrote: >> When trying to add a gpio-hog, we enter a weird loop where the gpio-ranges >> is needed when gpiochip_add_data() is called but in the current >> implementation >> the ranges are added from the driver afterwards. >> >> A simple solution is to rely on the DR gpio-ranges attribute and remove the >> call to gpiochip_add_pin_range(). > did you mean devicetree or DT instead of "DR"? > > > Regards, > Martin > Indeed, sorry for the typo. Neil
Re: [RFT PATCH 5/6] pinctrl: meson: use gpio-ranges from DT
Hi Neil, On Thu, Mar 23, 2017 at 5:27 PM, Neil Armstrong wrote: > When trying to add a gpio-hog, we enter a weird loop where the gpio-ranges > is needed when gpiochip_add_data() is called but in the current implementation > the ranges are added from the driver afterwards. > > A simple solution is to rely on the DR gpio-ranges attribute and remove the > call to gpiochip_add_pin_range(). did you mean devicetree or DT instead of "DR"? Regards, Martin
[RFT PATCH 5/6] pinctrl: meson: use gpio-ranges from DT
When trying to add a gpio-hog, we enter a weird loop where the gpio-ranges
is needed when gpiochip_add_data() is called but in the current implementation
the ranges are added from the driver afterwards.
A simple solution is to rely on the DR gpio-ranges attribute and remove the
call to gpiochip_add_pin_range().
Signed-off-by: Neil Armstrong
---
drivers/pinctrl/meson/pinctrl-meson.c | 14 +-
1 file changed, 1 insertion(+), 13 deletions(-)
diff --git a/drivers/pinctrl/meson/pinctrl-meson.c
b/drivers/pinctrl/meson/pinctrl-meson.c
index cf1686e..66ed70c 100644
--- a/drivers/pinctrl/meson/pinctrl-meson.c
+++ b/drivers/pinctrl/meson/pinctrl-meson.c
@@ -555,22 +555,10 @@ static int meson_gpiolib_register(struct meson_pinctrl
*pc)
if (ret) {
dev_err(pc->dev, "can't add gpio chip %s\n",
pc->data->name);
- goto fail;
- }
-
- ret = gpiochip_add_pin_range(&pc->chip, dev_name(pc->dev),
-0, pc->data->pin_base,
-pc->chip.ngpio);
- if (ret) {
- dev_err(pc->dev, "can't add pin range\n");
- goto fail;
+ return ret;
}
return 0;
-fail:
- gpiochip_remove(&pc->chip);
-
- return ret;
}
static struct regmap_config meson_regmap_config = {
--
1.9.1
