2014-01-08 18:40:54 +08:00
|
|
|
/*
|
|
|
|
|
* Internal GPIO functions.
|
|
|
|
|
*
|
|
|
|
|
* Copyright (C) 2013, Intel Corporation
|
|
|
|
|
* Author: Mika Westerberg <mika.westerberg@linux.intel.com>
|
|
|
|
|
*
|
|
|
|
|
* This program is free software; you can redistribute it and/or modify
|
|
|
|
|
* it under the terms of the GNU General Public License version 2 as
|
|
|
|
|
* published by the Free Software Foundation.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifndef GPIOLIB_H
|
|
|
|
|
#define GPIOLIB_H
|
|
|
|
|
|
2015-10-20 17:10:38 +08:00
|
|
|
#include <linux/gpio/driver.h>
|
2014-01-08 18:40:56 +08:00
|
|
|
#include <linux/err.h>
|
|
|
|
|
#include <linux/device.h>
|
2015-10-20 17:10:38 +08:00
|
|
|
#include <linux/module.h>
|
|
|
|
|
#include <linux/cdev.h>
|
2014-01-08 18:40:56 +08:00
|
|
|
|
2014-05-17 13:54:50 +08:00
|
|
|
enum of_gpio_flags;
|
2015-12-09 05:45:10 +08:00
|
|
|
enum gpiod_flags;
|
2015-03-17 06:49:03 +08:00
|
|
|
struct acpi_device;
|
|
|
|
|
|
2015-10-20 17:10:38 +08:00
|
|
|
/**
|
|
|
|
|
* struct gpio_device - internal state container for GPIO devices
|
|
|
|
|
* @id: numerical ID number for the GPIO chip
|
|
|
|
|
* @dev: the GPIO device struct
|
gpio: add a userspace chardev ABI for GPIOs
A new chardev that is to be used for userspace GPIO access is
added in this patch. It is intended to gradually replace the
horribly broken sysfs ABI.
Using a chardev has many upsides:
- All operations are per-gpiochip, which is the actual
device underlying the GPIOs, making us tie in to the
kernel device model properly.
- Hotpluggable GPIO controllers can come and go, as this
kind of problem has been know to userspace for character
devices since ages, and if a gpiochip handle is held in
userspace we know we will break something, whereas the
sysfs is stateless.
- The one-value-per-file rule of sysfs is really hard to
maintain when you want to twist more than one knob at a time,
for example have in-kernel APIs to switch several GPIO
lines at the same time, and this will be possible to do
with a single ioctl() from userspace, saving a lot of
context switching.
We also need to add a new bus type for GPIO. This is
necessary for example for userspace coldplug, where sysfs is
traversed to find the boot-time device nodes and create the
character devices in /dev.
This new chardev ABI is *non* *optional* and can be counted
on to be present in the future, emphasizing the preference
of this ABI.
The ABI only implements one single ioctl() to get the name
and number of GPIO lines of a chip. Even this is debatable:
see it as a minimal example for review. This ABI shall be
ruthlessly reviewed and etched in stone.
The old /sys/class/gpio is still optional to compile in,
but will be deprecated.
Unique device IDs are created using IDR, which is overkill
and insanely scalable, but also well tested.
Cc: Johan Hovold <johan@kernel.org>
Cc: Michael Welling <mwelling@ieee.org>
Cc: Markus Pargmann <mpa@pengutronix.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
2015-10-21 21:29:53 +08:00
|
|
|
* @chrdev: character device for the GPIO device
|
2016-02-09 20:21:06 +08:00
|
|
|
* @mockdev: class device used by the deprecated sysfs interface (may be
|
|
|
|
|
* NULL)
|
2015-10-20 17:10:38 +08:00
|
|
|
* @owner: helps prevent removal of modules exporting active GPIOs
|
|
|
|
|
* @chip: pointer to the corresponding gpiochip, holding static
|
|
|
|
|
* data for this device
|
2016-02-09 20:51:59 +08:00
|
|
|
* @descs: array of ngpio descriptors.
|
gpio: reflect base and ngpio into gpio_device
Some information about the GPIO chip need to stay around also
after the gpio_chip has been removed and only the gpio_device
persist. The base and ngpio are such things, for example we
don't want a new chip arriving to overlap the number space
of a dangling gpio_device, and the chardev may still query
the device for the number of lines etc.
Note that the code that assigns base and insert gpio_device
into the global list no longer check for a missing gpio_chip:
we respect the number space allocated by any other gpio_device.
As a consequence of the gdev being referenced directly from
the gpio_desc, we need to verify it differently from all
in-kernel API calls that fall through to direct queries to
the gpio_chip vtable: we first check that desc is !NULL, then
that desc->gdev is !NULL, then, if desc->gdev->chip is NULL,
we *BAIL OUT* without any error, so as to manage the case
where operations are requested on a device that is gone.
These checks were non-uniform and partly missing in the past:
so to simplify: create the macros VALIDATE_DESC() that will
return -EINVAL if the desc or desc->gdev is missing and just
0 if the chip is gone, and conversely VALIDATE_DESC_VOID()
for the case where the function does not return an error.
By using these macros, we get warning messages about missing
gdev with reference to the right function in the kernel log.
Despite the macro business this simplifies the code and make
it more readable than if we copy/paste the same descriptor
checking code into all code ABI call sites (IMHO).
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
2016-02-10 17:57:36 +08:00
|
|
|
* @ngpio: the number of GPIO lines on this GPIO device, equal to the size
|
|
|
|
|
* of the @descs array.
|
|
|
|
|
* @base: GPIO base in the DEPRECATED global Linux GPIO numberspace, assigned
|
|
|
|
|
* at device creation time.
|
2016-02-12 21:48:23 +08:00
|
|
|
* @label: a descriptive name for the GPIO device, such as the part number
|
|
|
|
|
* or name of the IP component in a System on Chip.
|
2016-02-11 18:37:48 +08:00
|
|
|
* @data: per-instance data assigned by the driver
|
2015-10-20 17:10:38 +08:00
|
|
|
* @list: links gpio_device:s together for traversal
|
|
|
|
|
*
|
|
|
|
|
* This state container holds most of the runtime variable data
|
|
|
|
|
* for a GPIO device and can hold references and live on after the
|
|
|
|
|
* GPIO chip has been removed, if it is still being used from
|
|
|
|
|
* userspace.
|
|
|
|
|
*/
|
|
|
|
|
struct gpio_device {
|
|
|
|
|
int id;
|
|
|
|
|
struct device dev;
|
gpio: add a userspace chardev ABI for GPIOs
A new chardev that is to be used for userspace GPIO access is
added in this patch. It is intended to gradually replace the
horribly broken sysfs ABI.
Using a chardev has many upsides:
- All operations are per-gpiochip, which is the actual
device underlying the GPIOs, making us tie in to the
kernel device model properly.
- Hotpluggable GPIO controllers can come and go, as this
kind of problem has been know to userspace for character
devices since ages, and if a gpiochip handle is held in
userspace we know we will break something, whereas the
sysfs is stateless.
- The one-value-per-file rule of sysfs is really hard to
maintain when you want to twist more than one knob at a time,
for example have in-kernel APIs to switch several GPIO
lines at the same time, and this will be possible to do
with a single ioctl() from userspace, saving a lot of
context switching.
We also need to add a new bus type for GPIO. This is
necessary for example for userspace coldplug, where sysfs is
traversed to find the boot-time device nodes and create the
character devices in /dev.
This new chardev ABI is *non* *optional* and can be counted
on to be present in the future, emphasizing the preference
of this ABI.
The ABI only implements one single ioctl() to get the name
and number of GPIO lines of a chip. Even this is debatable:
see it as a minimal example for review. This ABI shall be
ruthlessly reviewed and etched in stone.
The old /sys/class/gpio is still optional to compile in,
but will be deprecated.
Unique device IDs are created using IDR, which is overkill
and insanely scalable, but also well tested.
Cc: Johan Hovold <johan@kernel.org>
Cc: Michael Welling <mwelling@ieee.org>
Cc: Markus Pargmann <mpa@pengutronix.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
2015-10-21 21:29:53 +08:00
|
|
|
struct cdev chrdev;
|
2016-02-09 20:21:06 +08:00
|
|
|
struct device *mockdev;
|
2015-10-20 17:10:38 +08:00
|
|
|
struct module *owner;
|
|
|
|
|
struct gpio_chip *chip;
|
2016-02-09 20:51:59 +08:00
|
|
|
struct gpio_desc *descs;
|
gpio: reflect base and ngpio into gpio_device
Some information about the GPIO chip need to stay around also
after the gpio_chip has been removed and only the gpio_device
persist. The base and ngpio are such things, for example we
don't want a new chip arriving to overlap the number space
of a dangling gpio_device, and the chardev may still query
the device for the number of lines etc.
Note that the code that assigns base and insert gpio_device
into the global list no longer check for a missing gpio_chip:
we respect the number space allocated by any other gpio_device.
As a consequence of the gdev being referenced directly from
the gpio_desc, we need to verify it differently from all
in-kernel API calls that fall through to direct queries to
the gpio_chip vtable: we first check that desc is !NULL, then
that desc->gdev is !NULL, then, if desc->gdev->chip is NULL,
we *BAIL OUT* without any error, so as to manage the case
where operations are requested on a device that is gone.
These checks were non-uniform and partly missing in the past:
so to simplify: create the macros VALIDATE_DESC() that will
return -EINVAL if the desc or desc->gdev is missing and just
0 if the chip is gone, and conversely VALIDATE_DESC_VOID()
for the case where the function does not return an error.
By using these macros, we get warning messages about missing
gdev with reference to the right function in the kernel log.
Despite the macro business this simplifies the code and make
it more readable than if we copy/paste the same descriptor
checking code into all code ABI call sites (IMHO).
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
2016-02-10 17:57:36 +08:00
|
|
|
int base;
|
|
|
|
|
u16 ngpio;
|
2016-02-12 21:48:23 +08:00
|
|
|
char *label;
|
2016-02-11 18:37:48 +08:00
|
|
|
void *data;
|
2015-10-20 17:10:38 +08:00
|
|
|
struct list_head list;
|
2016-02-11 18:03:06 +08:00
|
|
|
|
|
|
|
|
#ifdef CONFIG_PINCTRL
|
|
|
|
|
/*
|
|
|
|
|
* If CONFIG_PINCTRL is enabled, then gpio controllers can optionally
|
|
|
|
|
* describe the actual pin range which they serve in an SoC. This
|
|
|
|
|
* information would be used by pinctrl subsystem to configure
|
|
|
|
|
* corresponding pins for gpio usage.
|
|
|
|
|
*/
|
|
|
|
|
struct list_head pin_ranges;
|
|
|
|
|
#endif
|
2015-10-20 17:10:38 +08:00
|
|
|
};
|
|
|
|
|
|
2014-01-08 18:40:56 +08:00
|
|
|
/**
|
|
|
|
|
* struct acpi_gpio_info - ACPI GPIO specific information
|
|
|
|
|
* @gpioint: if %true this GPIO is of type GpioInt otherwise type is GpioIo
|
|
|
|
|
* @active_low: in case of @gpioint, the pin is active low
|
|
|
|
|
*/
|
|
|
|
|
struct acpi_gpio_info {
|
|
|
|
|
bool gpioint;
|
2015-12-24 06:25:34 +08:00
|
|
|
int polarity;
|
|
|
|
|
int triggering;
|
2014-01-08 18:40:56 +08:00
|
|
|
};
|
|
|
|
|
|
2015-02-12 00:27:55 +08:00
|
|
|
/* gpio suffixes used for ACPI and device tree lookup */
|
|
|
|
|
static const char * const gpio_suffixes[] = { "gpios", "gpio" };
|
|
|
|
|
|
2014-01-08 18:40:54 +08:00
|
|
|
#ifdef CONFIG_ACPI
|
|
|
|
|
void acpi_gpiochip_add(struct gpio_chip *chip);
|
|
|
|
|
void acpi_gpiochip_remove(struct gpio_chip *chip);
|
2014-01-08 18:40:56 +08:00
|
|
|
|
2014-07-25 14:54:48 +08:00
|
|
|
void acpi_gpiochip_request_interrupts(struct gpio_chip *chip);
|
|
|
|
|
void acpi_gpiochip_free_interrupts(struct gpio_chip *chip);
|
|
|
|
|
|
gpio / ACPI: Add support for _DSD device properties
With release of ACPI 5.1 and _DSD method we can finally name GPIOs (and
other things as well) returned by _CRS. Previously we were only able to
use integer index to find the corresponding GPIO, which is pretty error
prone if the order changes.
With _DSD we can now query GPIOs using name instead of an integer index,
like the below example shows:
// Bluetooth device with reset and shutdown GPIOs
Device (BTH)
{
Name (_HID, ...)
Name (_CRS, ResourceTemplate ()
{
GpioIo (Exclusive, PullUp, 0, 0, IoRestrictionInputOnly,
"\\_SB.GPO0", 0, ResourceConsumer) {15}
GpioIo (Exclusive, PullUp, 0, 0, IoRestrictionInputOnly,
"\\_SB.GPO0", 0, ResourceConsumer) {27, 31}
})
Name (_DSD, Package ()
{
ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
Package ()
{
Package () {"reset-gpio", Package() {^BTH, 1, 1, 0 }},
Package () {"shutdown-gpio", Package() {^BTH, 0, 0, 0 }},
}
})
}
The format of the supported GPIO property is:
Package () { "name", Package () { ref, index, pin, active_low }}
ref - The device that has _CRS containing GpioIo()/GpioInt() resources,
typically this is the device itself (BTH in our case).
index - Index of the GpioIo()/GpioInt() resource in _CRS starting from zero.
pin - Pin in the GpioIo()/GpioInt() resource. Typically this is zero.
active_low - If 1 the GPIO is marked as active_low.
Since ACPI GpioIo() resource does not have field saying whether it is
active low or high, the "active_low" argument can be used here. Setting
it to 1 marks the GPIO as active low.
In our Bluetooth example the "reset-gpio" refers to the second GpioIo()
resource, second pin in that resource with the GPIO number of 31.
This patch implements necessary support to gpiolib for extracting GPIOs
using _DSD device properties.
Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Grant Likely <grant.likely@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2014-10-29 22:41:01 +08:00
|
|
|
struct gpio_desc *acpi_get_gpiod_by_index(struct acpi_device *adev,
|
|
|
|
|
const char *propname, int index,
|
2014-01-08 18:40:56 +08:00
|
|
|
struct acpi_gpio_info *info);
|
2015-08-27 10:42:33 +08:00
|
|
|
struct gpio_desc *acpi_node_get_gpiod(struct fwnode_handle *fwnode,
|
|
|
|
|
const char *propname, int index,
|
|
|
|
|
struct acpi_gpio_info *info);
|
2015-02-12 00:27:58 +08:00
|
|
|
|
|
|
|
|
int acpi_gpio_count(struct device *dev, const char *con_id);
|
2015-11-12 03:45:30 +08:00
|
|
|
|
|
|
|
|
bool acpi_can_fallback_to_crs(struct acpi_device *adev, const char *con_id);
|
2014-01-08 18:40:54 +08:00
|
|
|
#else
|
|
|
|
|
static inline void acpi_gpiochip_add(struct gpio_chip *chip) { }
|
|
|
|
|
static inline void acpi_gpiochip_remove(struct gpio_chip *chip) { }
|
2014-01-08 18:40:56 +08:00
|
|
|
|
2014-07-25 14:54:48 +08:00
|
|
|
static inline void
|
|
|
|
|
acpi_gpiochip_request_interrupts(struct gpio_chip *chip) { }
|
|
|
|
|
|
|
|
|
|
static inline void
|
|
|
|
|
acpi_gpiochip_free_interrupts(struct gpio_chip *chip) { }
|
|
|
|
|
|
2014-01-08 18:40:56 +08:00
|
|
|
static inline struct gpio_desc *
|
gpio / ACPI: Add support for _DSD device properties
With release of ACPI 5.1 and _DSD method we can finally name GPIOs (and
other things as well) returned by _CRS. Previously we were only able to
use integer index to find the corresponding GPIO, which is pretty error
prone if the order changes.
With _DSD we can now query GPIOs using name instead of an integer index,
like the below example shows:
// Bluetooth device with reset and shutdown GPIOs
Device (BTH)
{
Name (_HID, ...)
Name (_CRS, ResourceTemplate ()
{
GpioIo (Exclusive, PullUp, 0, 0, IoRestrictionInputOnly,
"\\_SB.GPO0", 0, ResourceConsumer) {15}
GpioIo (Exclusive, PullUp, 0, 0, IoRestrictionInputOnly,
"\\_SB.GPO0", 0, ResourceConsumer) {27, 31}
})
Name (_DSD, Package ()
{
ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
Package ()
{
Package () {"reset-gpio", Package() {^BTH, 1, 1, 0 }},
Package () {"shutdown-gpio", Package() {^BTH, 0, 0, 0 }},
}
})
}
The format of the supported GPIO property is:
Package () { "name", Package () { ref, index, pin, active_low }}
ref - The device that has _CRS containing GpioIo()/GpioInt() resources,
typically this is the device itself (BTH in our case).
index - Index of the GpioIo()/GpioInt() resource in _CRS starting from zero.
pin - Pin in the GpioIo()/GpioInt() resource. Typically this is zero.
active_low - If 1 the GPIO is marked as active_low.
Since ACPI GpioIo() resource does not have field saying whether it is
active low or high, the "active_low" argument can be used here. Setting
it to 1 marks the GPIO as active low.
In our Bluetooth example the "reset-gpio" refers to the second GpioIo()
resource, second pin in that resource with the GPIO number of 31.
This patch implements necessary support to gpiolib for extracting GPIOs
using _DSD device properties.
Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Grant Likely <grant.likely@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2014-10-29 22:41:01 +08:00
|
|
|
acpi_get_gpiod_by_index(struct acpi_device *adev, const char *propname,
|
|
|
|
|
int index, struct acpi_gpio_info *info)
|
2014-01-08 18:40:56 +08:00
|
|
|
{
|
|
|
|
|
return ERR_PTR(-ENOSYS);
|
|
|
|
|
}
|
2015-08-27 10:42:33 +08:00
|
|
|
static inline struct gpio_desc *
|
|
|
|
|
acpi_node_get_gpiod(struct fwnode_handle *fwnode, const char *propname,
|
|
|
|
|
int index, struct acpi_gpio_info *info)
|
|
|
|
|
{
|
|
|
|
|
return ERR_PTR(-ENXIO);
|
|
|
|
|
}
|
2015-02-12 00:27:58 +08:00
|
|
|
static inline int acpi_gpio_count(struct device *dev, const char *con_id)
|
|
|
|
|
{
|
|
|
|
|
return -ENODEV;
|
|
|
|
|
}
|
2015-11-12 03:45:30 +08:00
|
|
|
|
|
|
|
|
static inline bool acpi_can_fallback_to_crs(struct acpi_device *adev,
|
|
|
|
|
const char *con_id)
|
|
|
|
|
{
|
|
|
|
|
return false;
|
|
|
|
|
}
|
2014-01-08 18:40:54 +08:00
|
|
|
#endif
|
|
|
|
|
|
2014-05-17 13:54:50 +08:00
|
|
|
struct gpio_desc *of_get_named_gpiod_flags(struct device_node *np,
|
|
|
|
|
const char *list_name, int index, enum of_gpio_flags *flags);
|
|
|
|
|
|
2014-07-22 15:17:41 +08:00
|
|
|
struct gpio_desc *gpiochip_get_desc(struct gpio_chip *chip, u16 hwnum);
|
|
|
|
|
|
2014-07-01 13:45:15 +08:00
|
|
|
extern struct spinlock gpio_lock;
|
2015-10-20 17:10:38 +08:00
|
|
|
extern struct list_head gpio_devices;
|
2014-07-01 13:45:15 +08:00
|
|
|
|
|
|
|
|
struct gpio_desc {
|
gpio: reflect base and ngpio into gpio_device
Some information about the GPIO chip need to stay around also
after the gpio_chip has been removed and only the gpio_device
persist. The base and ngpio are such things, for example we
don't want a new chip arriving to overlap the number space
of a dangling gpio_device, and the chardev may still query
the device for the number of lines etc.
Note that the code that assigns base and insert gpio_device
into the global list no longer check for a missing gpio_chip:
we respect the number space allocated by any other gpio_device.
As a consequence of the gdev being referenced directly from
the gpio_desc, we need to verify it differently from all
in-kernel API calls that fall through to direct queries to
the gpio_chip vtable: we first check that desc is !NULL, then
that desc->gdev is !NULL, then, if desc->gdev->chip is NULL,
we *BAIL OUT* without any error, so as to manage the case
where operations are requested on a device that is gone.
These checks were non-uniform and partly missing in the past:
so to simplify: create the macros VALIDATE_DESC() that will
return -EINVAL if the desc or desc->gdev is missing and just
0 if the chip is gone, and conversely VALIDATE_DESC_VOID()
for the case where the function does not return an error.
By using these macros, we get warning messages about missing
gdev with reference to the right function in the kernel log.
Despite the macro business this simplifies the code and make
it more readable than if we copy/paste the same descriptor
checking code into all code ABI call sites (IMHO).
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
2016-02-10 17:57:36 +08:00
|
|
|
struct gpio_device *gdev;
|
2014-07-01 13:45:15 +08:00
|
|
|
unsigned long flags;
|
|
|
|
|
/* flag symbols are bit numbers */
|
|
|
|
|
#define FLAG_REQUESTED 0
|
|
|
|
|
#define FLAG_IS_OUT 1
|
|
|
|
|
#define FLAG_EXPORT 2 /* protected by sysfs_lock */
|
|
|
|
|
#define FLAG_SYSFS 3 /* exported via /sys/class/gpio/control */
|
|
|
|
|
#define FLAG_ACTIVE_LOW 6 /* value has active low */
|
|
|
|
|
#define FLAG_OPEN_DRAIN 7 /* Gpio is open drain type */
|
|
|
|
|
#define FLAG_OPEN_SOURCE 8 /* Gpio is open source type */
|
|
|
|
|
#define FLAG_USED_AS_IRQ 9 /* GPIO is connected to an IRQ */
|
2015-02-03 01:44:44 +08:00
|
|
|
#define FLAG_IS_HOGGED 11 /* GPIO is hogged */
|
2014-07-01 13:45:15 +08:00
|
|
|
|
2015-08-14 22:10:59 +08:00
|
|
|
/* Connection label */
|
2014-07-01 13:45:15 +08:00
|
|
|
const char *label;
|
2015-08-14 22:10:59 +08:00
|
|
|
/* Name of the GPIO */
|
|
|
|
|
const char *name;
|
2014-07-01 13:45:15 +08:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
int gpiod_request(struct gpio_desc *desc, const char *label);
|
|
|
|
|
void gpiod_free(struct gpio_desc *desc);
|
2015-02-03 01:44:44 +08:00
|
|
|
int gpiod_hog(struct gpio_desc *desc, const char *name,
|
|
|
|
|
unsigned long lflags, enum gpiod_flags dflags);
|
2014-07-01 13:45:15 +08:00
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Return the GPIO number of the passed descriptor relative to its chip
|
|
|
|
|
*/
|
|
|
|
|
static int __maybe_unused gpio_chip_hwgpio(const struct gpio_desc *desc)
|
|
|
|
|
{
|
gpio: reflect base and ngpio into gpio_device
Some information about the GPIO chip need to stay around also
after the gpio_chip has been removed and only the gpio_device
persist. The base and ngpio are such things, for example we
don't want a new chip arriving to overlap the number space
of a dangling gpio_device, and the chardev may still query
the device for the number of lines etc.
Note that the code that assigns base and insert gpio_device
into the global list no longer check for a missing gpio_chip:
we respect the number space allocated by any other gpio_device.
As a consequence of the gdev being referenced directly from
the gpio_desc, we need to verify it differently from all
in-kernel API calls that fall through to direct queries to
the gpio_chip vtable: we first check that desc is !NULL, then
that desc->gdev is !NULL, then, if desc->gdev->chip is NULL,
we *BAIL OUT* without any error, so as to manage the case
where operations are requested on a device that is gone.
These checks were non-uniform and partly missing in the past:
so to simplify: create the macros VALIDATE_DESC() that will
return -EINVAL if the desc or desc->gdev is missing and just
0 if the chip is gone, and conversely VALIDATE_DESC_VOID()
for the case where the function does not return an error.
By using these macros, we get warning messages about missing
gdev with reference to the right function in the kernel log.
Despite the macro business this simplifies the code and make
it more readable than if we copy/paste the same descriptor
checking code into all code ABI call sites (IMHO).
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
2016-02-10 17:57:36 +08:00
|
|
|
return desc - &desc->gdev->descs[0];
|
2014-07-01 13:45:15 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* With descriptor prefix */
|
|
|
|
|
|
|
|
|
|
#define gpiod_emerg(desc, fmt, ...) \
|
|
|
|
|
pr_emerg("gpio-%d (%s): " fmt, desc_to_gpio(desc), desc->label ? : "?",\
|
|
|
|
|
##__VA_ARGS__)
|
|
|
|
|
#define gpiod_crit(desc, fmt, ...) \
|
|
|
|
|
pr_crit("gpio-%d (%s): " fmt, desc_to_gpio(desc), desc->label ? : "?", \
|
|
|
|
|
##__VA_ARGS__)
|
|
|
|
|
#define gpiod_err(desc, fmt, ...) \
|
|
|
|
|
pr_err("gpio-%d (%s): " fmt, desc_to_gpio(desc), desc->label ? : "?", \
|
|
|
|
|
##__VA_ARGS__)
|
|
|
|
|
#define gpiod_warn(desc, fmt, ...) \
|
|
|
|
|
pr_warn("gpio-%d (%s): " fmt, desc_to_gpio(desc), desc->label ? : "?", \
|
|
|
|
|
##__VA_ARGS__)
|
|
|
|
|
#define gpiod_info(desc, fmt, ...) \
|
|
|
|
|
pr_info("gpio-%d (%s): " fmt, desc_to_gpio(desc), desc->label ? : "?", \
|
|
|
|
|
##__VA_ARGS__)
|
|
|
|
|
#define gpiod_dbg(desc, fmt, ...) \
|
|
|
|
|
pr_debug("gpio-%d (%s): " fmt, desc_to_gpio(desc), desc->label ? : "?",\
|
|
|
|
|
##__VA_ARGS__)
|
|
|
|
|
|
|
|
|
|
/* With chip prefix */
|
|
|
|
|
|
|
|
|
|
#define chip_emerg(chip, fmt, ...) \
|
2015-10-20 17:31:54 +08:00
|
|
|
dev_emerg(&chip->gpiodev->dev, "(%s): " fmt, chip->label, ##__VA_ARGS__)
|
2014-07-01 13:45:15 +08:00
|
|
|
#define chip_crit(chip, fmt, ...) \
|
2015-10-20 17:31:54 +08:00
|
|
|
dev_crit(&chip->gpiodev->dev, "(%s): " fmt, chip->label, ##__VA_ARGS__)
|
2014-07-01 13:45:15 +08:00
|
|
|
#define chip_err(chip, fmt, ...) \
|
2015-10-20 17:31:54 +08:00
|
|
|
dev_err(&chip->gpiodev->dev, "(%s): " fmt, chip->label, ##__VA_ARGS__)
|
2014-07-01 13:45:15 +08:00
|
|
|
#define chip_warn(chip, fmt, ...) \
|
2015-10-20 17:31:54 +08:00
|
|
|
dev_warn(&chip->gpiodev->dev, "(%s): " fmt, chip->label, ##__VA_ARGS__)
|
2014-07-01 13:45:15 +08:00
|
|
|
#define chip_info(chip, fmt, ...) \
|
2015-10-20 17:31:54 +08:00
|
|
|
dev_info(&chip->gpiodev->dev, "(%s): " fmt, chip->label, ##__VA_ARGS__)
|
2014-07-01 13:45:15 +08:00
|
|
|
#define chip_dbg(chip, fmt, ...) \
|
2015-10-20 17:31:54 +08:00
|
|
|
dev_dbg(&chip->gpiodev->dev, "(%s): " fmt, chip->label, ##__VA_ARGS__)
|
2014-07-01 13:45:15 +08:00
|
|
|
|
|
|
|
|
#ifdef CONFIG_GPIO_SYSFS
|
|
|
|
|
|
2016-02-09 20:21:06 +08:00
|
|
|
int gpiochip_sysfs_register(struct gpio_device *gdev);
|
|
|
|
|
void gpiochip_sysfs_unregister(struct gpio_device *gdev);
|
2014-07-01 13:45:15 +08:00
|
|
|
|
|
|
|
|
#else
|
|
|
|
|
|
2016-02-09 20:21:06 +08:00
|
|
|
static inline int gpiochip_sysfs_register(struct gpio_device *gdev)
|
2014-07-01 13:45:15 +08:00
|
|
|
{
|
|
|
|
|
return 0;
|
|
|
|
|
}
|
|
|
|
|
|
2016-02-09 20:21:06 +08:00
|
|
|
static inline void gpiochip_sysfs_unregister(struct gpio_device *gdev)
|
2014-07-01 13:45:15 +08:00
|
|
|
{
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#endif /* CONFIG_GPIO_SYSFS */
|
|
|
|
|
|
2014-01-08 18:40:54 +08:00
|
|
|
#endif /* GPIOLIB_H */
|
