| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CACRpkda3m4ipTsS8FZoU1QDwrvwmKFn4awyfXOy2VOiuV63y6A@mail.gmail.com>
Date: Tue, 24 Sep 2013 14:52:48 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: "rtc-linux@...glegroups.com" <rtc-linux@...glegroups.com>
Cc: Lee Jones <lee.jones@...aro.org>,
Samuel Ortiz <sameo@...ux.intel.com>,
Mark Brown <broonie@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
Rob Herring <rob.herring@...xeda.com>,
Mark Rutland <mark.rutland@....com>,
Pawel Moll <pawel.moll@....com>,
Stephen Warren <swarren@...dotorg.org>,
Rob Landley <rob@...dley.net>,
"ijc+devicetree@...lion.org.uk" <ijc+devicetree@...lion.org.uk>,
Grant Likely <grant.likely@...aro.org>,
Laxman Dewangan <ldewangan@...dia.com>,
Florian Lobmaier <florian.lobmaier@....com>
Subject: Re: [rtc-linux] [PATCH V3 2/3] pincntrl: add support for AMS AS3722
pin control driver
On Tue, Sep 24, 2013 at 1:58 PM, Laxman Dewangan <ldewangan@...dia.com> wrote:
> The AS3722 is a compact system PMU suitable for mobile phones, tablets etc.
>
> Add a driver to support accessing the GPIO, pinmux and pin configuration
> of 8 GPIO pins found on the AMS AS3722 through pin control driver and
> gpiolib.
>
> The driver will register itself as the pincontrol driver and gpio driver.
>
> Signed-off-by: Laxman Dewangan <ldewangan@...dia.com>
> Signed-off-by: Florian Lobmaier <florian.lobmaier@....com>
That was quick! :-)
This is starting to look a lot better.
> +static int as3722_pinconf_group_get(struct pinctrl_dev *pctldev,
> + unsigned group, unsigned long *config)
> +{
> + dev_err(pctldev->dev, "as3722_pinconf_group_get op not supported\n");
> + return -ENOTSUPP;
> +}
> +
> +static int as3722_pinconf_group_set(struct pinctrl_dev *pctldev,
> + unsigned group, unsigned long *configs,
> + unsigned num_configs)
> +{
> + dev_err(pctldev->dev, "as3722_pinconf_group_set op not supported\n");
> + return -ENOTSUPP;
> +}
> +
> +static const struct pinconf_ops as3722_pinconf_ops = {
> + .pin_config_get = as3722_pinconf_get,
> + .pin_config_set = as3722_pinconf_set,
> + .pin_config_group_get = as3722_pinconf_group_get,
> + .pin_config_group_set = as3722_pinconf_group_set,
Can't you just leave .pin_config_group_[get|set] undefined as
you don't support that?
> +static struct pinctrl_desc as3722_pinctrl_desc = {
> + .pctlops = (struct pinctrl_ops *)&as3722_pinctrl_ops,
> + .pmxops = (struct pinmux_ops *)&as3722_pinmux_ops,
> + .confops = (struct pinconf_ops *)&as3722_pinconf_ops,
Why do you need these casts? Should not be necessary.
> +static int as_pci_direction_input(struct gpio_chip *chip, unsigned offset)
> +{
> + struct as3722_pctrl_info *as_pci = to_as_pci(chip);
> + struct as3722 *as3722 = as_pci->as3722;
> + int mode;
> +
> + mode = as_pci_get_mode(as_pci->gpio_control[offset].mode_prop,
> + true);
> + if (mode < 0) {
> + dev_err(as_pci->dev,
> + "Input direction for GPIO %d not supported\n", offset);
> + return mode;
> + }
> +
> + if (as_pci->gpio_control[offset].enable_gpio_invert)
> + mode |= AS3722_GPIO_INV;
> +
> + return as3722_write(as3722, AS3722_GPIOn_CONTROL_REG(offset), mode);
> +}
Why is this function not calling
pinctrl_gpio_direction_input(chip->base + offset) instea of setting up
the mode intself?
The GPIO part of the driver should use the pinctrl part of the
driver as back-end.
> +static int as_pci_direction_output(struct gpio_chip *chip,
> + unsigned offset, int value)
> +{
> + struct as3722_pctrl_info *as_pci = to_as_pci(chip);
> + struct as3722 *as3722 = as_pci->as3722;
> + int mode;
> +
> + mode = as_pci_get_mode(as_pci->gpio_control[offset].mode_prop,
> + false);
> + if (mode < 0) {
> + dev_err(as_pci->dev,
> + "Output direction for GPIO %d not supported\n", offset);
> + return mode;
> + }
> +
> + as_pci_set(chip, offset, value);
> + if (as_pci->gpio_control[offset].enable_gpio_invert)
> + mode |= AS3722_GPIO_INV;
> + return as3722_write(as3722, AS3722_GPIOn_CONTROL_REG(offset), mode);
> +}
Dito:
pinctrl_gpio_direction_output()
> +static int as_pci_to_irq(struct gpio_chip *chip, unsigned offset)
> +{
> + struct as3722_pctrl_info *as_pci = to_as_pci(chip);
> +
> + return as3722_irq_get_virq(as_pci->as3722, offset);
> +}
> +
> +static int as_pci_request(struct gpio_chip *chip, unsigned offset)
> +{
> + struct as3722_pctrl_info *as_pci = to_as_pci(chip);
> +
> + if (as_pci->gpio_control[offset].io_function)
> + return -EBUSY;
> + return 0;
> +}
Why is this not calling pinctrl_request_gpio(as_pci->chip.base + offset)
instead of just checking if we happen to be GPIO and failing if
we are not?
I would implement .free calling pinctrl_free_gpio(gpio) as well.
See e.g. pinctrl-abx500.c
> +static const struct gpio_chip as_pci_chip = {
> + .label = "as3722-gpio",
> + .owner = THIS_MODULE,
> + .direction_input = as_pci_direction_input,
> + .get = as_pci_get,
> + .direction_output = as_pci_direction_output,
> + .set = as_pci_set,
> + .to_irq = as_pci_to_irq,
> + .request = as_pci_request,
> + .can_sleep = 1,
> + .ngpio = AS3722_PIN_NUM,
> + .base = -1,
> +};
> +
> +static int as3722_pinctrl_probe(struct platform_device *pdev)
> +{
> + struct as3722_pctrl_info *as_pci;
> + int ret;
> +
> + as_pci = devm_kzalloc(&pdev->dev, sizeof(*as_pci), GFP_KERNEL);
> + if (!as_pci)
> + return -ENOMEM;
> +
> + as_pci->dev = &pdev->dev;
> + as_pci->dev->of_node = pdev->dev.parent->of_node;
> + as_pci->as3722 = dev_get_drvdata(pdev->dev.parent);
> + platform_set_drvdata(pdev, as_pci);
> +
> + as_pci->pins = as3722_pins_desc;
> + as_pci->num_pins = ARRAY_SIZE(as3722_pins_desc);
> + as_pci->functions = as3722_pin_function;
> + as_pci->num_functions = ARRAY_SIZE(as3722_pin_function);
> + as_pci->pin_groups = as3722_pingroups;
> + as_pci->num_pin_groups = ARRAY_SIZE(as3722_pingroups);
> + as3722_pinctrl_desc.name = dev_name(&pdev->dev);
> + as3722_pinctrl_desc.pins = as3722_pins_desc;
> + as3722_pinctrl_desc.npins = ARRAY_SIZE(as3722_pins_desc);
> + as_pci->pctl = pinctrl_register(&as3722_pinctrl_desc,
> + &pdev->dev, as_pci);
> + if (!as_pci->pctl) {
> + dev_err(&pdev->dev, "Couldn't register pinctrl driver\n");
> + return -ENODEV;
> + }
> +
> + as_pci->gpio_chip = as_pci_chip;
> + as_pci->gpio_chip.dev = &pdev->dev;
> + as_pci->gpio_chip.of_node = pdev->dev.parent->of_node;
> + ret = gpiochip_add(&as_pci->gpio_chip);
> + if (ret < 0) {
> + dev_err(&pdev->dev, "Could not register gpiochip, %d\n", ret);
> + goto scrub;
> + }
Right here you should register a GPIO range using
gpiochip_add_pin_range() so that all calls from the gpio_chip
side can happily fall through to the pinctrl driver and set up
pins as GPIO.
It's very nice how you contained the driver in one state container.
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