From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-gpio@vger.kernel.org, Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v1] pinctrl: intel: Allow to request locked pins
Date: Tue, 6 Aug 2019 14:01:26 +0300 [thread overview]
Message-ID: <20190806110126.GR2548@lahna.fi.intel.com> (raw)
In-Reply-To: <20190726200830.52728-1-andriy.shevchenko@linux.intel.com>
On Fri, Jul 26, 2019 at 11:08:30PM +0300, Andy Shevchenko wrote:
> Some firmwares would like to protect pins from being modified by OS
> and at the same time provide them to OS as a resource. So, the driver
> in such circumstances may request pin and may not change its state.
This is definitely good idea.
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> drivers/pinctrl/intel/pinctrl-intel.c | 55 +++++++++++++++++++--------
> 1 file changed, 39 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/pinctrl/intel/pinctrl-intel.c b/drivers/pinctrl/intel/pinctrl-intel.c
> index 3a945997b8eb..567fe43b238f 100644
> --- a/drivers/pinctrl/intel/pinctrl-intel.c
> +++ b/drivers/pinctrl/intel/pinctrl-intel.c
> @@ -220,22 +220,30 @@ static bool intel_pad_acpi_mode(struct intel_pinctrl *pctrl, unsigned int pin)
> return !(readl(hostown) & BIT(gpp_offset));
> }
>
> -static bool intel_pad_locked(struct intel_pinctrl *pctrl, unsigned int pin)
> +enum {
> + PAD_UNLOCKED = 0,
> + PAD_LOCKED = 1,
> + PAD_LOCKED_TX = 2,
> + PAD_LOCKED_FULL = PAD_LOCKED | PAD_LOCKED_TX,
> +};
> +
> +static int intel_pad_locked(struct intel_pinctrl *pctrl, unsigned int pin)
> {
> struct intel_community *community;
> const struct intel_padgroup *padgrp;
> unsigned int offset, gpp_offset;
> u32 value;
> + int ret = PAD_UNLOCKED;
>
> community = intel_get_community(pctrl, pin);
> if (!community)
> - return true;
> + return PAD_LOCKED_FULL;
> if (!community->padcfglock_offset)
> - return false;
> + return PAD_UNLOCKED;
>
> padgrp = intel_community_get_padgroup(community, pin);
> if (!padgrp)
> - return true;
> + return PAD_LOCKED_FULL;
>
> gpp_offset = padgroup_offset(padgrp, pin);
>
> @@ -244,23 +252,27 @@ static bool intel_pad_locked(struct intel_pinctrl *pctrl, unsigned int pin)
> * the pad is considered unlocked. Any other case means that it is
> * either fully or partially locked and we don't touch it.
I think you should update the above comment as well.
> */
> - offset = community->padcfglock_offset + padgrp->reg_num * 8;
> + offset = community->padcfglock_offset + 0 + padgrp->reg_num * 8;
> value = readl(community->regs + offset);
> if (value & BIT(gpp_offset))
> - return true;
> + ret |= PAD_LOCKED;
>
> offset = community->padcfglock_offset + 4 + padgrp->reg_num * 8;
> value = readl(community->regs + offset);
> if (value & BIT(gpp_offset))
> - return true;
> + ret |= PAD_LOCKED_TX;
>
> - return false;
> + return ret;
> +}
> +
> +static bool intel_pad_is_unlocked(struct intel_pinctrl *pctrl, unsigned int pin)
> +{
> + return (intel_pad_locked(pctrl, pin) & PAD_LOCKED) == PAD_UNLOCKED;
> }
>
> static bool intel_pad_usable(struct intel_pinctrl *pctrl, unsigned int pin)
> {
> - return intel_pad_owned_by_host(pctrl, pin) &&
> - !intel_pad_locked(pctrl, pin);
> + return intel_pad_owned_by_host(pctrl, pin) && intel_pad_is_unlocked(pctrl, pin);
> }
>
> static int intel_get_groups_count(struct pinctrl_dev *pctldev)
> @@ -294,7 +306,8 @@ static void intel_pin_dbg_show(struct pinctrl_dev *pctldev, struct seq_file *s,
> struct intel_pinctrl *pctrl = pinctrl_dev_get_drvdata(pctldev);
> void __iomem *padcfg;
> u32 cfg0, cfg1, mode;
> - bool locked, acpi;
> + int locked;
> + bool acpi;
>
> if (!intel_pad_owned_by_host(pctrl, pin)) {
> seq_puts(s, "not available");
> @@ -322,11 +335,16 @@ static void intel_pin_dbg_show(struct pinctrl_dev *pctldev, struct seq_file *s,
>
> if (locked || acpi) {
> seq_puts(s, " [");
> - if (locked) {
> + if (locked)
> seq_puts(s, "LOCKED");
> - if (acpi)
> - seq_puts(s, ", ");
> - }
> + if ((locked & PAD_LOCKED_FULL) == PAD_LOCKED_TX)
> + seq_puts(s, " TX");
> + else if ((locked & PAD_LOCKED_FULL) == PAD_LOCKED_FULL)
> + seq_puts(s, " FULL");
> +
> + if (locked && acpi)
> + seq_puts(s, ", ");
> +
> if (acpi)
> seq_puts(s, "ACPI");
> seq_puts(s, "]");
> @@ -448,11 +466,16 @@ static int intel_gpio_request_enable(struct pinctrl_dev *pctldev,
>
> raw_spin_lock_irqsave(&pctrl->lock, flags);
>
> - if (!intel_pad_usable(pctrl, pin)) {
> + if (!intel_pad_owned_by_host(pctrl, pin)) {
> raw_spin_unlock_irqrestore(&pctrl->lock, flags);
> return -EBUSY;
> }
>
> + if (!intel_pad_is_unlocked(pctrl, pin)) {
> + raw_spin_unlock_irqrestore(&pctrl->lock, flags);
> + return 0;
Hmm, if I'm reading this right it still does not allow requesting locked
pins. What I'm missing here?
> + }
> +
> padcfg0 = intel_get_padcfg(pctrl, pin, PADCFG0);
> intel_gpio_set_gpio_mode(padcfg0);
> /* Disable TX buffer and enable RX (this will be input) */
> --
> 2.20.1
next prev parent reply other threads:[~2019-08-06 11:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 20:08 [PATCH v1] pinctrl: intel: Allow to request locked pins Andy Shevchenko
2019-08-06 11:01 ` Mika Westerberg [this message]
2019-08-06 11:45 ` Andy Shevchenko
2019-08-06 11:47 ` Mika Westerberg
2019-08-06 14:27 ` Linus Walleij
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=20190806110126.GR2548@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.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: link
Be 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.