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 4/4] pinctrl: intel: Convert capability list to features
Date: Fri, 8 Jan 2021 09:07:22 +0200 [thread overview]
Message-ID: <20210108070722.GX968855@lahna.fi.intel.com> (raw)
In-Reply-To: <20210107190200.41221-4-andriy.shevchenko@linux.intel.com>
On Thu, Jan 07, 2021 at 09:02:00PM +0200, Andy Shevchenko wrote:
> Communities can have features provided in the capability list.
> Traverse the list and convert to respective features.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> drivers/pinctrl/intel/pinctrl-intel.c | 41 +++++++++++++++++++++++++--
> drivers/pinctrl/intel/pinctrl-intel.h | 4 +++
> 2 files changed, 42 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/pinctrl/intel/pinctrl-intel.c b/drivers/pinctrl/intel/pinctrl-intel.c
> index 00979acb0203..3d9f22ee987a 100644
> --- a/drivers/pinctrl/intel/pinctrl-intel.c
> +++ b/drivers/pinctrl/intel/pinctrl-intel.c
> @@ -29,6 +29,16 @@
> #define REVID_SHIFT 16
> #define REVID_MASK GENMASK(31, 16)
>
> +#define CAPLIST 0x004
> +#define CAPLIST_ID_SHIFT 16
> +#define CAPLIST_ID_MASK GENMASK(23, 16)
> +#define CAPLIST_ID_GPIO_HW_INFO 1
> +#define CAPLIST_ID_PWM 2
> +#define CAPLIST_ID_BLINK 3
> +#define CAPLIST_ID_EXP 4
> +#define CAPLIST_NEXT_SHIFT 0
> +#define CAPLIST_NEXT_MASK GENMASK(15, 0)
> +
> #define PADBAR 0x00c
>
> #define PADOWN_BITS 4
> @@ -1472,7 +1482,7 @@ static int intel_pinctrl_probe(struct platform_device *pdev,
> for (i = 0; i < pctrl->ncommunities; i++) {
> struct intel_community *community = &pctrl->communities[i];
> void __iomem *regs;
> - u32 padbar;
> + u32 offset;
> u32 value;
>
> *community = pctrl->soc->communities[i];
> @@ -1492,11 +1502,36 @@ static int intel_pinctrl_probe(struct platform_device *pdev,
> break;
> }
>
> + /* Determine community features based on the capabilities */
> + offset = CAPLIST;
> + do {
> + value = readl(regs + offset);
> + switch ((value & CAPLIST_ID_MASK) >> CAPLIST_ID_SHIFT) {
> + case CAPLIST_ID_GPIO_HW_INFO:
> + community->features |= PINCTRL_FEATURE_GPIO_HW_INFO;
> + break;
> + case CAPLIST_ID_PWM:
> + community->features |= PINCTRL_FEATURE_PWM;
> + break;
> + case CAPLIST_ID_BLINK:
> + community->features |= PINCTRL_FEATURE_BLINK;
> + break;
> + case CAPLIST_ID_EXP:
> + community->features |= PINCTRL_FEATURE_EXP;
> + break;
> + default:
> + break;
> + }
> + offset = (value & CAPLIST_NEXT_MASK) >> CAPLIST_NEXT_SHIFT;
I suggest adding some check, like that we visited the previous offset
already, so that we do not loop here forever if we find wrongly
formatted capability list.
Otherwise looks good.
> + } while (offset);
next prev parent reply other threads:[~2021-01-08 7:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 19:01 [PATCH v1 1/4] pinctrl: intel: Split intel_pinctrl_add_padgroups() for better maintenance Andy Shevchenko
2021-01-07 19:01 ` [PATCH v1 2/4] pinctrl: intel: Drop unnecessary check for predefined features Andy Shevchenko
2021-01-08 7:08 ` Mika Westerberg
2021-01-07 19:01 ` [PATCH v1 3/4] pinctrl: intel: Convert revision conditional to switch-case Andy Shevchenko
2021-01-08 7:05 ` Mika Westerberg
2021-01-07 19:02 ` [PATCH v1 4/4] pinctrl: intel: Convert capability list to features Andy Shevchenko
2021-01-08 7:07 ` Mika Westerberg [this message]
2021-01-08 12:22 ` Andy Shevchenko
2021-01-08 12:31 ` Andy Shevchenko
2021-01-08 12:46 ` Mika Westerberg
2021-01-08 12:51 ` Andy Shevchenko
2021-01-08 13:11 ` Mika Westerberg
2021-01-08 13:45 ` Andy Shevchenko
2021-01-08 7:07 ` [PATCH v1 1/4] pinctrl: intel: Split intel_pinctrl_add_padgroups() for better maintenance Mika Westerberg
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=20210108070722.GX968855@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox