From: AKASHI Takahiro <takahiro.akashi@linaro.org> To: sudeep.holla@arm.com, cristian.marussi@arm.com, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org, linus.walleij@linaro.org Cc: Oleksii_Moisieiev@epam.com, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org, AKASHI Takahiro <takahiro.akashi@linaro.org> Subject: [RFC v2 1/5] pinctrl: define PIN_CONFIG_INPUT Date: Thu, 5 Oct 2023 11:58:39 +0900 [thread overview] Message-ID: <20231005025843.508689-2-takahiro.akashi@linaro.org> (raw) In-Reply-To: <20231005025843.508689-1-takahiro.akashi@linaro.org> This configuration is intended to be used to allow a pin controller based GPIO driver to obtain a value at a gpio input pin. Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org> --- RFC v2 (Oct 5, 2023) * improve a comment against @PIN_CONFIG_INPUT as per Linus RFC(Oct 2, 2023) --- include/linux/pinctrl/pinconf-generic.h | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/include/linux/pinctrl/pinconf-generic.h b/include/linux/pinctrl/pinconf-generic.h index d74b7a4ea154..da0d80aa532d 100644 --- a/include/linux/pinctrl/pinconf-generic.h +++ b/include/linux/pinctrl/pinconf-generic.h @@ -67,6 +67,10 @@ struct pinctrl_map; * passed as argument. The argument is in mA. * @PIN_CONFIG_DRIVE_STRENGTH_UA: the pin will sink or source at most the current * passed as argument. The argument is in uA. + * @PIN_CONFIG_INPUT: This will obtain a value on an input pin. To put a line + * into input mode, @PIN_CONFIG_INPUT_ENABLE must be used. Otherwise, + * an error will be returned. The returned argument is 1 for logic high + * and 0 for logic low. * @PIN_CONFIG_INPUT_DEBOUNCE: this will configure the pin to debounce mode, * which means it will wait for signals to settle when reading inputs. The * argument gives the debounce time in usecs. Setting the @@ -128,6 +132,7 @@ enum pin_config_param { PIN_CONFIG_DRIVE_PUSH_PULL, PIN_CONFIG_DRIVE_STRENGTH, PIN_CONFIG_DRIVE_STRENGTH_UA, + PIN_CONFIG_INPUT, PIN_CONFIG_INPUT_DEBOUNCE, PIN_CONFIG_INPUT_ENABLE, PIN_CONFIG_INPUT_SCHMITT, -- 2.34.1
WARNING: multiple messages have this Message-ID (diff)
From: AKASHI Takahiro <takahiro.akashi@linaro.org> To: sudeep.holla@arm.com, cristian.marussi@arm.com, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org, linus.walleij@linaro.org Cc: Oleksii_Moisieiev@epam.com, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org, AKASHI Takahiro <takahiro.akashi@linaro.org> Subject: [RFC v2 1/5] pinctrl: define PIN_CONFIG_INPUT Date: Thu, 5 Oct 2023 11:58:39 +0900 [thread overview] Message-ID: <20231005025843.508689-2-takahiro.akashi@linaro.org> (raw) In-Reply-To: <20231005025843.508689-1-takahiro.akashi@linaro.org> This configuration is intended to be used to allow a pin controller based GPIO driver to obtain a value at a gpio input pin. Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org> --- RFC v2 (Oct 5, 2023) * improve a comment against @PIN_CONFIG_INPUT as per Linus RFC(Oct 2, 2023) --- include/linux/pinctrl/pinconf-generic.h | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/include/linux/pinctrl/pinconf-generic.h b/include/linux/pinctrl/pinconf-generic.h index d74b7a4ea154..da0d80aa532d 100644 --- a/include/linux/pinctrl/pinconf-generic.h +++ b/include/linux/pinctrl/pinconf-generic.h @@ -67,6 +67,10 @@ struct pinctrl_map; * passed as argument. The argument is in mA. * @PIN_CONFIG_DRIVE_STRENGTH_UA: the pin will sink or source at most the current * passed as argument. The argument is in uA. + * @PIN_CONFIG_INPUT: This will obtain a value on an input pin. To put a line + * into input mode, @PIN_CONFIG_INPUT_ENABLE must be used. Otherwise, + * an error will be returned. The returned argument is 1 for logic high + * and 0 for logic low. * @PIN_CONFIG_INPUT_DEBOUNCE: this will configure the pin to debounce mode, * which means it will wait for signals to settle when reading inputs. The * argument gives the debounce time in usecs. Setting the @@ -128,6 +132,7 @@ enum pin_config_param { PIN_CONFIG_DRIVE_PUSH_PULL, PIN_CONFIG_DRIVE_STRENGTH, PIN_CONFIG_DRIVE_STRENGTH_UA, + PIN_CONFIG_INPUT, PIN_CONFIG_INPUT_DEBOUNCE, PIN_CONFIG_INPUT_ENABLE, PIN_CONFIG_INPUT_SCHMITT, -- 2.34.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-10-05 14:18 UTC|newest] Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-05 2:58 [RFC v2 0/5] gpio: add pinctrl based generic gpio driver AKASHI Takahiro 2023-10-05 2:58 ` AKASHI Takahiro 2023-10-05 2:58 ` AKASHI Takahiro [this message] 2023-10-05 2:58 ` [RFC v2 1/5] pinctrl: define PIN_CONFIG_INPUT AKASHI Takahiro 2023-10-10 11:53 ` Linus Walleij 2023-10-10 11:53 ` Linus Walleij 2023-10-05 2:58 ` [RFC v2 2/5] pinctrl: always export pin_config_get_for_pin() AKASHI Takahiro 2023-10-05 2:58 ` AKASHI Takahiro 2023-10-10 11:54 ` Linus Walleij 2023-10-10 11:54 ` Linus Walleij 2023-10-05 2:58 ` [RFC v2 3/5] pinctrl: add pinctrl_gpio_get_config() AKASHI Takahiro 2023-10-05 2:58 ` AKASHI Takahiro 2023-10-05 2:58 ` [RFC v2 4/5] gpio: add pinctrl based generic gpio driver AKASHI Takahiro 2023-10-05 2:58 ` AKASHI Takahiro 2023-10-10 12:00 ` Linus Walleij 2023-10-10 12:00 ` Linus Walleij 2023-10-12 1:08 ` AKASHI Takahiro 2023-10-12 1:08 ` AKASHI Takahiro 2023-10-05 2:58 ` [RFC v2 5/5] dt-bindings: gpio: Add bindings for " AKASHI Takahiro 2023-10-05 2:58 ` AKASHI Takahiro 2023-10-05 19:48 ` Krzysztof Kozlowski 2023-10-05 19:48 ` Krzysztof Kozlowski 2023-10-12 1:15 ` AKASHI Takahiro 2023-10-12 1:15 ` AKASHI Takahiro 2023-10-12 7:27 ` Krzysztof Kozlowski 2023-10-12 7:27 ` Krzysztof Kozlowski 2023-10-06 13:18 ` Rob Herring 2023-10-06 13:18 ` Rob Herring 2023-10-06 13:23 ` Rob Herring 2023-10-06 13:23 ` Rob Herring 2023-10-09 7:49 ` Linus Walleij 2023-10-09 7:49 ` Linus Walleij 2023-10-09 9:08 ` Cristian Marussi 2023-10-09 9:08 ` Cristian Marussi 2023-10-09 13:13 ` Linus Walleij 2023-10-09 13:13 ` Linus Walleij 2023-10-09 15:08 ` Cristian Marussi 2023-10-09 15:08 ` Cristian Marussi 2023-10-10 5:14 ` AKASHI Takahiro 2023-10-10 5:14 ` AKASHI Takahiro 2023-10-10 5:25 ` AKASHI Takahiro 2023-10-10 5:25 ` AKASHI Takahiro 2023-10-12 7:25 ` Linus Walleij 2023-10-12 7:25 ` Linus Walleij 2023-10-17 2:32 ` AKASHI Takahiro 2023-10-17 2:32 ` AKASHI Takahiro 2023-10-23 8:12 ` Linus Walleij 2023-10-23 8:12 ` Linus Walleij 2023-10-24 7:12 ` AKASHI Takahiro 2023-10-24 7:12 ` AKASHI Takahiro 2023-10-24 9:40 ` Linus Walleij 2023-10-24 9:40 ` Linus Walleij 2023-10-24 10:55 ` Cristian Marussi 2023-10-24 10:55 ` Cristian Marussi 2023-10-24 13:01 ` Linus Walleij 2023-10-24 13:01 ` Linus Walleij 2023-10-24 11:09 ` AKASHI Takahiro 2023-10-24 11:09 ` AKASHI Takahiro 2023-10-24 13:12 ` Linus Walleij 2023-10-24 13:12 ` Linus Walleij 2023-10-24 13:42 ` AKASHI Takahiro 2023-10-24 13:42 ` AKASHI Takahiro 2023-11-05 22:15 ` Linus Walleij 2023-11-05 22:15 ` Linus Walleij 2023-10-19 21:27 ` [RFC v2 0/5] gpio: add " andy.shevchenko 2023-10-19 21:27 ` andy.shevchenko 2023-10-20 0:21 ` AKASHI Takahiro 2023-10-20 0:21 ` AKASHI Takahiro
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20231005025843.508689-2-takahiro.akashi@linaro.org \ --to=takahiro.akashi@linaro.org \ --cc=Oleksii_Moisieiev@epam.com \ --cc=conor+dt@kernel.org \ --cc=cristian.marussi@arm.com \ --cc=devicetree@vger.kernel.org \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-gpio@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=robh+dt@kernel.org \ --cc=sudeep.holla@arm.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.