From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Raag Jadav <raag.jadav@intel.com>
Cc: linus.walleij@linaro.org, mika.westerberg@linux.intel.com,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
mallikarjunappa.sangannavar@intel.com, pandith.n@intel.com
Subject: Re: [PATCH v4] pinctrl: intel: refine ->irq_set_type() hook
Date: Thu, 15 Jun 2023 16:14:36 +0300 [thread overview]
Message-ID: <ZIsOvBGLJTCo45jp@smile.fi.intel.com> (raw)
In-Reply-To: <20230615125022.27421-1-raag.jadav@intel.com>
On Thu, Jun 15, 2023 at 06:20:22PM +0530, Raag Jadav wrote:
> Refine ->irq_set_type() hook and improve its readability by:
>
> - Reducing scope of spinlock by moving unneeded operations out of it.
> - Dropping redundant PADCFG0_RXEVCFG_SHIFT and including it directly
> into PADCFG0_RXEVCFG_* definitions.
> - Utilizing temporary variables for common operations.
> - Simplifying if-else-if chain.
Two questions out of curiosity.
Do we gain or lose bytes with this?
> Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> ---
> drivers/pinctrl/intel/pinctrl-intel.c | 45 ++++++++++++++-------------
> 1 file changed, 24 insertions(+), 21 deletions(-)
>
> diff --git a/drivers/pinctrl/intel/pinctrl-intel.c b/drivers/pinctrl/intel/pinctrl-intel.c
> index e8adf2580321..036eae74c479 100644
> --- a/drivers/pinctrl/intel/pinctrl-intel.c
> +++ b/drivers/pinctrl/intel/pinctrl-intel.c
> @@ -55,12 +55,11 @@
>
> /* Offset from pad_regs */
> #define PADCFG0 0x000
> -#define PADCFG0_RXEVCFG_SHIFT 25
> #define PADCFG0_RXEVCFG_MASK GENMASK(26, 25)
> -#define PADCFG0_RXEVCFG_LEVEL 0
> -#define PADCFG0_RXEVCFG_EDGE 1
> -#define PADCFG0_RXEVCFG_DISABLED 2
> -#define PADCFG0_RXEVCFG_EDGE_BOTH 3
> +#define PADCFG0_RXEVCFG_LEVEL (0 << 25)
> +#define PADCFG0_RXEVCFG_EDGE (1 << 25)
> +#define PADCFG0_RXEVCFG_DISABLED (2 << 25)
> +#define PADCFG0_RXEVCFG_EDGE_BOTH (3 << 25)
> #define PADCFG0_PREGFRXSEL BIT(24)
> #define PADCFG0_RXINV BIT(23)
> #define PADCFG0_GPIROUTIOXAPIC BIT(20)
> @@ -1127,9 +1126,9 @@ static int intel_gpio_irq_type(struct irq_data *d, unsigned int type)
> struct gpio_chip *gc = irq_data_get_irq_chip_data(d);
> struct intel_pinctrl *pctrl = gpiochip_get_data(gc);
> unsigned int pin = intel_gpio_to_pin(pctrl, irqd_to_hwirq(d), NULL, NULL);
> + u32 rxevcfg, rxinv, value;
> unsigned long flags;
> void __iomem *reg;
> - u32 value;
>
> reg = intel_get_padcfg(pctrl, pin, PADCFG0);
> if (!reg)
> @@ -1145,28 +1144,32 @@ static int intel_gpio_irq_type(struct irq_data *d, unsigned int type)
> return -EPERM;
> }
>
> - raw_spin_lock_irqsave(&pctrl->lock, flags);
> -
> - intel_gpio_set_gpio_mode(reg);
> -
> - value = readl(reg);
> -
> - value &= ~(PADCFG0_RXEVCFG_MASK | PADCFG0_RXINV);
> -
> if ((type & IRQ_TYPE_EDGE_BOTH) == IRQ_TYPE_EDGE_BOTH) {
> - value |= PADCFG0_RXEVCFG_EDGE_BOTH << PADCFG0_RXEVCFG_SHIFT;
> + rxevcfg = PADCFG0_RXEVCFG_EDGE_BOTH;
> } else if (type & IRQ_TYPE_EDGE_FALLING) {
> - value |= PADCFG0_RXEVCFG_EDGE << PADCFG0_RXEVCFG_SHIFT;
> - value |= PADCFG0_RXINV;
> + rxevcfg = PADCFG0_RXEVCFG_EDGE;
> } else if (type & IRQ_TYPE_EDGE_RISING) {
> - value |= PADCFG0_RXEVCFG_EDGE << PADCFG0_RXEVCFG_SHIFT;
> + rxevcfg = PADCFG0_RXEVCFG_EDGE;
> } else if (type & IRQ_TYPE_LEVEL_MASK) {
> - if (type & IRQ_TYPE_LEVEL_LOW)
> - value |= PADCFG0_RXINV;
> + rxevcfg = PADCFG0_RXEVCFG_LEVEL;
> } else {
> - value |= PADCFG0_RXEVCFG_DISABLED << PADCFG0_RXEVCFG_SHIFT;
> + rxevcfg = PADCFG0_RXEVCFG_DISABLED;
> }
>
> + if (type == IRQ_TYPE_EDGE_FALLING || type == IRQ_TYPE_LEVEL_LOW)
> + rxinv = PADCFG0_RXINV;
> + else
> + rxinv = 0;
> +
> + raw_spin_lock_irqsave(&pctrl->lock, flags);
> +
> + intel_gpio_set_gpio_mode(reg);
> +
> + value = readl(reg);
> + value = (value & ~PADCFG0_RXINV) | rxinv;
> + value = (value & ~PADCFG0_RXEVCFG_MASK) | rxevcfg;
Same question if we change this to be similar to the current code, i.e.
value = readl(reg);
value &= ~(PADCFG0_RXEVCFG_MASK | PADCFG0_RXINV);
value |= rxevcfg;
value |= rxinv;
And I would keep blank lines after readl() and before writel() since we have
more than a single line in between.
> writel(value, reg);
>
> if (type & IRQ_TYPE_EDGE_BOTH)
>
> base-commit: e95433c367e681dc6d4613706bd74f483a25acd8
> --
> 2.17.1
>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-06-15 13:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 12:50 [PATCH v4] pinctrl: intel: refine ->irq_set_type() hook Raag Jadav
2023-06-15 13:14 ` Andy Shevchenko [this message]
2023-06-15 13:35 ` Jadav, Raag
2023-06-15 14:09 ` Andy Shevchenko
2023-06-15 15:05 ` Jadav, Raag
2023-06-15 15:16 ` Andy Shevchenko
2023-06-15 15:28 ` Andy Shevchenko
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=ZIsOvBGLJTCo45jp@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mallikarjunappa.sangannavar@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=pandith.n@intel.com \
--cc=raag.jadav@intel.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: 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.