| 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
| ||
|
Date: Tue, 13 Oct 2015 12:03:06 +0900
From: Chanwoo Choi <cw00.choi@...sung.com>
To: Mark Rutland <mark.rutland@....com>
Cc: linux-kernel@...r.kernel.org, robh+dt@...nel.org,
pawel.moll@....com, ijc+devicetree@...lion.org.uk,
galak@...eaurora.org, myungjoo.ham@...sung.com,
devicetree@...r.kernel.org
Subject: Re: [PATCH v2] extcon: gpio: Add the support for Device tree bindings
Hi Mark,
On 2015년 10월 05일 20:13, Mark Rutland wrote:
> On Mon, Oct 05, 2015 at 03:58:19PM +0900, Chanwoo Choi wrote:
>> This patch adds the support for Device tree bindings of extcon-gpio driver.
>> The extcon-gpio device tree node must include the both 'extcon-id' and
>> 'extcon-gpio' property.
>>
>> For exmaple:
>> usb_cable: extcon-gpio-0 {
>> compatible = "extcon-gpio";
>> extcon-id = <EXTCON_USB>;
>> extcon-gpio = <&gpio6 1 GPIO_ACTIVE_HIGH>;
>> }
>>
>> ta_cable: extcon-gpio-1 {
>> compatible = "extcon-gpio";
>> extcon-id = <EXTCON_CHG_USB_DCP>;
>> extcon-gpio = <&gpio3 2 GPIO_ACTIVE_LOW>;
>> debounce-ms = <50>; /* 50 millisecond */
>> wakeup-source;
>> }
>>
>> &dwc3_usb {
>> extcon = <&usb_cable>;
>> };
>>
>> &charger {
>> extcon = <&ta_cable>;
>> };
>>
>> Signed-off-by: Chanwoo Choi <cw00.choi@...sung.com>
>> ---
>> Changes from v1:
>> - Create the include/dt-bindings/extcon/extcon.h including the identification
>> of external connector. These definitions are used in dts file.
>> - Fix error if CONFIG_OF is disabled.
>>
>> .../devicetree/bindings/extcon/extcon-gpio.txt | 38 +++++++
>> drivers/extcon/extcon-gpio.c | 110 ++++++++++++++++-----
>> include/dt-bindings/extcon/extcon.h | 44 +++++++++
>> include/linux/extcon/extcon-gpio.h | 6 +-
>> 4 files changed, 173 insertions(+), 25 deletions(-)
>> create mode 100644 Documentation/devicetree/bindings/extcon/extcon-gpio.txt
>> create mode 100644 include/dt-bindings/extcon/extcon.h
>>
>> diff --git a/Documentation/devicetree/bindings/extcon/extcon-gpio.txt b/Documentation/devicetree/bindings/extcon/extcon-gpio.txt
>> new file mode 100644
>> index 000000000000..70c36f729963
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/extcon/extcon-gpio.txt
>> @@ -0,0 +1,38 @@
>> +GPIO Extcon device
>> +
>> +This is a virtual device used to generate specific external connector
>> +from the GPIO pin connected to a GPIO pin.
>> +
>> +Required properties:
>> +- compatible: Must be "extcon-gpio".
>> +- extcon-id: unique id for specific external connector.
>> + See include/dt-bindings/extcon/extcon.h.
>
> This property is either misnamed and badly described, or it is
> pointless (the node is sufficient to form a unique ID which can be
> referenced by phandle).
>
> What is this used for exactly?
OK, I'll modify the description of 'extcon-id' property as following:
- extcon-id: The extcon support the various type of external connector to check
whether connector is attached or detached. The each external connector has
the unique number to identify it. So this property includes the unique number
which indicates the specific external connector. When external connector is
attached or detached, GPIO pin detect the changed state. See include/
dt-bindings/extcon/extcon.h which defines the unique number for supported
external connector from extcon framework.
>
>> +- extcon-gpio: GPIO pin to detect the external connector. See gpio binding.
>> +
>> +Optional properties:
>> +- debounce-ms: the debounce dealy for GPIO pin in millisecond.
>> +- wakeup-source: Boolean, extcon can wake-up the system.
>> +
>> +Example: Examples of extcon-gpio node as listed below:
>> +
>> + usb_cable: extcon-gpio-0 {
>> + compatible = "extcon-gpio";
>> + extcon-id = <EXTCON_USB>;
>> + extcon-gpio = <&gpio6 1 GPIO_ACTIVE_HIGH>;
>> + }
>> +
>> + ta_cable: extcon-gpio-1 {
>> + compatible = "extcon-gpio";
>> + extcon-id = <EXTCON_CHG_USB_DCP>;
>> + extcon-gpio = <&gpio3 2 GPIO_ACTIVE_LOW>;
>> + debounce-ms = <50>; /* 50 millisecond */
>> + wakeup-source;
>> + }
>> +
>> + &dwc3_usb {
>> + extcon = <&usb_cable>;
>> + };
>> +
>> + &charger {
>> + extcon = <&ta_cable>;
>> + };
>> diff --git a/drivers/extcon/extcon-gpio.c b/drivers/extcon/extcon-gpio.c
>> index 279ff8f6637d..7f3e24aae0c4 100644
>> --- a/drivers/extcon/extcon-gpio.c
>> +++ b/drivers/extcon/extcon-gpio.c
>> @@ -1,8 +1,8 @@
>> /*
>> * extcon_gpio.c - Single-state GPIO extcon driver based on extcon class
>> *
>> - * Copyright (C) 2008 Google, Inc.
>> - * Author: Mike Lockwood <lockwood@...roid.com>
>> + * Copyright (C) 2015 Chanwoo Choi <cw00.choi@...sung.com>, Samsung Electronics
>> + * Copyright (C) 2008 Mike Lockwood <lockwood@...roid.com>, Google, Inc.
>> *
>> * Modified by MyungJoo Ham <myungjoo.ham@...sung.com> to support extcon
>> * (originally switch class is supported)
>> @@ -26,12 +26,14 @@
>> #include <linux/kernel.h>
>> #include <linux/module.h>
>> #include <linux/platform_device.h>
>> +#include <linux/property.h>
>> #include <linux/slab.h>
>> #include <linux/workqueue.h>
>>
>> struct gpio_extcon_data {
>> struct extcon_dev *edev;
>> int irq;
>> + bool irq_wakeup;
>> struct delayed_work work;
>> unsigned long debounce_jiffies;
>>
>> @@ -61,19 +63,50 @@ static irqreturn_t gpio_irq_handler(int irq, void *dev_id)
>> return IRQ_HANDLED;
>> }
>>
>> -static int gpio_extcon_init(struct device *dev, struct gpio_extcon_data *data)
>> +static int gpio_extcon_parse_of(struct device *dev,
>> + struct gpio_extcon_data *data)
>> {
>> - struct gpio_extcon_pdata *pdata = data->pdata;
>> + struct gpio_extcon_pdata *pdata;
>> int ret;
>>
>> - ret = devm_gpio_request_one(dev, pdata->gpio, GPIOF_DIR_IN,
>> - dev_name(dev));
>> + pdata = devm_kzalloc(dev, sizeof(*pdata), GFP_KERNEL);
>> + if (!pdata)
>> + return -ENOMEM;
>> +
>> + ret = device_property_read_u32(dev, "extcon-id", &pdata->extcon_id);
>> + if (ret < 0)
>> + return -EINVAL;
>
> No sanity checking of the value?
When checking the validation of value,
I should check both the unique number and name.
But, the name of external connector is only accessed
in the extcon core driver(drivers/extcon/extcon.c)
So, I'll implement the sanity checking on extcon core
when calling the extcon_dev_allocate(*supported_cable).
>
> Why device_property rather than of_property?
There is no special reason. When using the device_property_*(),
It is well-working without any problem.
>> +
>> + data->id_gpiod = devm_gpiod_get(dev, "extcon", GPIOD_IN);
>> if (ret < 0)
>> return ret;
>>
>> - data->id_gpiod = gpio_to_desc(pdata->gpio);
>> - if (!data->id_gpiod)
>> - return -EINVAL;
>> + data->irq_wakeup = device_property_read_bool(dev, "wakeup-source");
>> +
>> + device_property_read_u32(dev, "debounce-ms", &pdata->debounce);
>
> Likewise, surely there's an upper bound above?
The unit of debounce-ms is millisecond. It is not determined limit value for just time.
Thanks,
Chanwoo Choi
--
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