From: Stephen Boyd <sboyd@codeaurora.org> To: Linus Walleij <linus.walleij@linaro.org> Cc: Timur Tabi <timur@codeaurora.org>, Andy Gross <andy.gross@linaro.org>, David Brown <david.brown@linaro.org>, anjiandi@codeaurora.org, Bjorn Andersson <bjorn.andersson@linaro.org>, "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>, "thierry.reding@gmail.com" <thierry.reding@gmail.com>, Mika Westerberg <mika.westerberg@linux.intel.com>, Andy Shevchenko <andriy.shevchenko@linux.intel.com> Subject: Re: [PATCH 0/2] [v5] pinctrl: qcom: add support for sparse GPIOs Date: Thu, 12 Oct 2017 00:39:22 -0700 [thread overview] Message-ID: <20171012073922.GB18706@codeaurora.org> (raw) In-Reply-To: <CACRpkdYXsY5eixYkEeuZTHJn7q6_6BdTxZ-2yneUyEKUjKF3Gw@mail.gmail.com> On 10/11, Linus Walleij wrote: > On Wed, Oct 4, 2017 at 12:03 AM, Stephen Boyd <sboyd@codeaurora.org> wrote: > > > Could we remove the pin direction finding part here in > > gpiochip_add_pin_range() and lazily resolve the pin direction > > when a pin is requested? We would need a similar check in the msm > > specific debugfs code where we skip pins that aren't requested. > > This is basically a revert of commit 72d320006177 ("gpio: set up > > initial state from .get_direction()"). > > It seems reasonable for the gpiolib to be able to call this > function immediately after registering the new GPIO chip > with its vtable. I agree. I don't see the benefit though. Reading the direction later would achieve the same effect and also work for ACPI qcom platforms. > > I think it is more up to the driver to numb the reply with > some dummy return value (i.e. input mode) or refactor the > callback so that it is acceptable for gpiolib to get an -EINVAL > or so from the driver (again it will assume input mode) if the > driver can't return the direction at this time. > For qcom platforms the driver will never be able to return the direction for these certain pins because reading the register is not allowed by the firmware. Doing so will cause the device to crash with a security violation. If you don't want to delay reading the direction until request time, we should have the DT msm pinctrl drivers leave the get_direction() pointer as NULL. We don't need to read the direction on DT platforms to make anything work. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 0/2] [v5] pinctrl: qcom: add support for sparse GPIOs Date: Thu, 12 Oct 2017 00:39:22 -0700 [thread overview] Message-ID: <20171012073922.GB18706@codeaurora.org> (raw) In-Reply-To: <CACRpkdYXsY5eixYkEeuZTHJn7q6_6BdTxZ-2yneUyEKUjKF3Gw@mail.gmail.com> On 10/11, Linus Walleij wrote: > On Wed, Oct 4, 2017 at 12:03 AM, Stephen Boyd <sboyd@codeaurora.org> wrote: > > > Could we remove the pin direction finding part here in > > gpiochip_add_pin_range() and lazily resolve the pin direction > > when a pin is requested? We would need a similar check in the msm > > specific debugfs code where we skip pins that aren't requested. > > This is basically a revert of commit 72d320006177 ("gpio: set up > > initial state from .get_direction()"). > > It seems reasonable for the gpiolib to be able to call this > function immediately after registering the new GPIO chip > with its vtable. I agree. I don't see the benefit though. Reading the direction later would achieve the same effect and also work for ACPI qcom platforms. > > I think it is more up to the driver to numb the reply with > some dummy return value (i.e. input mode) or refactor the > callback so that it is acceptable for gpiolib to get an -EINVAL > or so from the driver (again it will assume input mode) if the > driver can't return the direction at this time. > For qcom platforms the driver will never be able to return the direction for these certain pins because reading the register is not allowed by the firmware. Doing so will cause the device to crash with a security violation. If you don't want to delay reading the direction until request time, we should have the DT msm pinctrl drivers leave the get_direction() pointer as NULL. We don't need to read the direction on DT platforms to make anything work. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-10-12 7:39 UTC|newest] Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-09-07 15:33 [PATCH 0/2] [v5] pinctrl: qcom: add support for sparse GPIOs Timur Tabi 2017-09-07 15:33 ` Timur Tabi 2017-09-07 15:33 ` [PATCH 1/2] [v5] pinctrl: qcom: disable GPIO groups with no pins Timur Tabi 2017-09-07 15:33 ` Timur Tabi 2017-10-02 17:44 ` Bjorn Andersson 2017-10-02 17:44 ` Bjorn Andersson 2017-10-02 20:47 ` Timur Tabi 2017-10-02 20:47 ` Timur Tabi 2017-10-07 11:07 ` Linus Walleij 2017-10-07 11:07 ` Linus Walleij 2017-10-13 23:35 ` Timur Tabi 2017-10-13 23:35 ` Timur Tabi 2017-10-19 22:44 ` Timur Tabi 2017-10-19 22:44 ` Timur Tabi 2017-10-16 8:01 ` Thierry Reding 2017-10-16 8:01 ` Thierry Reding 2017-10-16 13:52 ` Timur Tabi 2017-10-16 13:52 ` Timur Tabi 2017-09-07 15:33 ` [PATCH 2/2] [v3] pinctrl: qcom: qdf2xxx: add support for new ACPI HID QCOM8002 Timur Tabi 2017-09-07 15:33 ` Timur Tabi 2017-09-08 12:50 ` [PATCH 0/2] [v5] pinctrl: qcom: add support for sparse GPIOs Linus Walleij 2017-09-08 12:50 ` Linus Walleij 2017-09-13 17:09 ` Timur Tabi 2017-09-13 17:09 ` Timur Tabi 2017-09-19 7:04 ` Stephen Boyd 2017-09-19 7:04 ` Stephen Boyd 2017-09-19 8:15 ` Linus Walleij 2017-09-19 8:15 ` Linus Walleij 2017-09-19 12:32 ` Timur Tabi 2017-09-19 12:32 ` Timur Tabi 2017-09-20 11:43 ` Linus Walleij 2017-09-20 11:43 ` Linus Walleij 2017-09-20 13:04 ` Timur Tabi 2017-09-20 13:04 ` Timur Tabi 2017-09-21 12:08 ` Linus Walleij 2017-09-21 12:08 ` Linus Walleij 2017-09-21 12:12 ` Timur Tabi 2017-09-21 12:12 ` Timur Tabi 2017-09-22 13:29 ` Linus Walleij 2017-09-22 13:29 ` Linus Walleij 2017-09-22 13:37 ` Timur Tabi 2017-09-22 13:37 ` Timur Tabi 2017-10-03 22:03 ` Stephen Boyd 2017-10-03 22:03 ` Stephen Boyd 2017-10-03 22:12 ` Timur Tabi 2017-10-03 22:12 ` Timur Tabi 2017-10-04 21:50 ` Stephen Boyd 2017-10-04 21:50 ` Stephen Boyd 2017-10-04 22:41 ` Timur Tabi 2017-10-04 22:41 ` Timur Tabi 2017-10-05 21:30 ` Stephen Boyd 2017-10-05 21:30 ` Stephen Boyd 2017-10-11 7:51 ` Linus Walleij 2017-10-11 7:51 ` Linus Walleij 2017-10-12 7:39 ` Stephen Boyd [this message] 2017-10-12 7:39 ` Stephen Boyd 2017-10-14 22:43 ` Linus Walleij 2017-10-14 22:43 ` Linus Walleij 2017-10-16 13:42 ` Timur Tabi 2017-10-16 13:42 ` Timur Tabi 2017-10-13 23:26 ` Timur Tabi 2017-10-13 23:26 ` Timur Tabi 2017-10-15 20:18 ` Thierry Reding 2017-10-15 20:18 ` Thierry Reding 2017-10-15 21:09 ` Timur Tabi 2017-10-15 21:09 ` Timur Tabi 2017-10-02 16:02 ` Timur Tabi 2017-10-02 16:02 ` Timur Tabi
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=20171012073922.GB18706@codeaurora.org \ --to=sboyd@codeaurora.org \ --cc=andriy.shevchenko@linux.intel.com \ --cc=andy.gross@linaro.org \ --cc=anjiandi@codeaurora.org \ --cc=bjorn.andersson@linaro.org \ --cc=david.brown@linaro.org \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-gpio@vger.kernel.org \ --cc=mika.westerberg@linux.intel.com \ --cc=thierry.reding@gmail.com \ --cc=timur@codeaurora.org \ /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.