From: Marc Zyngier <maz@kernel.org>
To: Qianggui Song <qianggui.song@amlogic.com>
Cc: Hanjie Lin <hanjie.lin@amlogic.com>,
Jason Cooper <jason@lakedaemon.net>,
Jianxin Pan <jianxin.pan@amlogic.com>,
Neil Armstrong <narmstrong@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org,
Thomas Gleixner <tglx@linutronix.de>,
Xingyu Chen <xingyu.chen@amlogic.com>,
Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: [PATCH 2/4] irqchip/meson-gpio: rework meson irqchip driver to support meson-A1 SoCs
Date: Fri, 06 Dec 2019 13:13:50 +0000 [thread overview]
Message-ID: <542e3e819e584d6e433d2c4276c3b379@www.loen.fr> (raw)
In-Reply-To: <20191206121714.14579-3-qianggui.song@amlogic.com>
On 2019-12-06 12:17, Qianggui Song wrote:
> Since Meson-A1 Socs register layout of gpio interrupt controller have
> difference with previous chips, registers to decide irq line and
> offset
> of trigger method are all changed, the current driver should be
> modified.
>
> Signed-off-by: Qianggui Song <qianggui.song@amlogic.com>
> ---
> drivers/irqchip/irq-meson-gpio.c | 79
> ++++++++++++++++++++++++--------
> 1 file changed, 60 insertions(+), 19 deletions(-)
>
> diff --git a/drivers/irqchip/irq-meson-gpio.c
> b/drivers/irqchip/irq-meson-gpio.c
> index 829084b568fa..1824ffc30de2 100644
> --- a/drivers/irqchip/irq-meson-gpio.c
> +++ b/drivers/irqchip/irq-meson-gpio.c
> @@ -30,44 +30,74 @@
> * stuck at 0. Bits 8 to 15 are responsive and have the expected
> * effect.
> */
> -#define REG_EDGE_POL_EDGE(x) BIT(x)
> -#define REG_EDGE_POL_LOW(x) BIT(16 + (x))
> -#define REG_BOTH_EDGE(x) BIT(8 + (x))
> -#define REG_EDGE_POL_MASK(x) ( \
> - REG_EDGE_POL_EDGE(x) | \
> - REG_EDGE_POL_LOW(x) | \
> - REG_BOTH_EDGE(x))
> +#define REG_EDGE_POL_EDGE(params,
> x) BIT((params)->edge_single_offset + (x))
> +#define REG_EDGE_POL_LOW(params, x) BIT((params)->pol_low_offset +
> (x))
> +#define REG_BOTH_EDGE(params, x) BIT((params)->edge_both_offset +
> (x))
> +#define REG_EDGE_POL_MASK(params, x) ( \
> + REG_EDGE_POL_EDGE(params, x) | \
> + REG_EDGE_POL_LOW(params, x) | \
> + REG_BOTH_EDGE(params, x))
> #define REG_PIN_SEL_SHIFT(x) (((x) % 4) * 8)
> #define REG_FILTER_SEL_SHIFT(x) ((x) * 4)
>
> +#define INIT_MESON8_COMMON_DATA \
> + .edge_single_offset = 0, \
> + .pol_low_offset = 16, \
> + .pin_sel_mask = 0xff, \
> + .ops = { \
> + .gpio_irq_sel_pin = meson8_gpio_irq_sel_pin, \
> + },
Please place the #defines that operate on the various data structures
*after* the definition of the structures. It would greatly help
reading the changes.
> +
> +struct meson_gpio_irq_controller;
> +static void meson8_gpio_irq_sel_pin(struct meson_gpio_irq_controller
> *ctl,
> + unsigned int channel, unsigned long hwirq);
> +struct irq_ctl_ops {
> + void (*gpio_irq_sel_pin)(struct meson_gpio_irq_controller *ctl,
> + unsigned int channel,
> + unsigned long hwirq);
> + void (*gpio_irq_init)(struct meson_gpio_irq_controller *ctl);
> +};
> +
> struct meson_gpio_irq_params {
> unsigned int nr_hwirq;
> bool support_edge_both;
> + unsigned int edge_both_offset;
> + unsigned int edge_single_offset;
> + unsigned int pol_low_offset;
> + unsigned int pin_sel_mask;
> + struct irq_ctl_ops ops;
> };
>
> static const struct meson_gpio_irq_params meson8_params = {
> .nr_hwirq = 134,
> + INIT_MESON8_COMMON_DATA
> };
>
> static const struct meson_gpio_irq_params meson8b_params = {
> .nr_hwirq = 119,
> + INIT_MESON8_COMMON_DATA
> };
>
> static const struct meson_gpio_irq_params gxbb_params = {
> .nr_hwirq = 133,
> + INIT_MESON8_COMMON_DATA
> };
>
> static const struct meson_gpio_irq_params gxl_params = {
> .nr_hwirq = 110,
> + INIT_MESON8_COMMON_DATA
> };
>
> static const struct meson_gpio_irq_params axg_params = {
> .nr_hwirq = 100,
> + INIT_MESON8_COMMON_DATA
> };
>
> static const struct meson_gpio_irq_params sm1_params = {
> .nr_hwirq = 100,
> .support_edge_both = true,
> + .edge_both_offset = 8,
> + INIT_MESON8_COMMON_DATA
> };
OK, this isn't great. The least you could do is to make
your initializer parametric, so that it takes the nr_hwirq as
a parameter.
Then, any additional member that overrides common behaviour
should come after the main initializer.
Also, do you need 'support_edge_both'? Isn't a non-zero
'edge_both_offset' enough to detect the feature?
>
> static const struct of_device_id meson_irq_gpio_matches[] = {
> @@ -100,9 +130,18 @@ static void meson_gpio_irq_update_bits(struct
> meson_gpio_irq_controller *ctl,
> writel_relaxed(tmp, ctl->base + reg);
> }
>
> -static unsigned int meson_gpio_irq_channel_to_reg(unsigned int
> channel)
> +static void meson8_gpio_irq_sel_pin(struct meson_gpio_irq_controller
> *ctl,
> + unsigned int channel, unsigned long hwirq)
> {
> - return (channel < 4) ? REG_PIN_03_SEL : REG_PIN_47_SEL;
> + unsigned int reg_offset;
> + unsigned int bit_offset;
> +
> + reg_offset = (channel < 4) ? REG_PIN_03_SEL : REG_PIN_47_SEL;
> + bit_offset = REG_PIN_SEL_SHIFT(channel);
> +
> + meson_gpio_irq_update_bits(ctl, reg_offset,
> + ctl->params->pin_sel_mask << bit_offset,
> + hwirq << bit_offset);
> }
>
> static int
> @@ -110,7 +149,7 @@ meson_gpio_irq_request_channel(struct
> meson_gpio_irq_controller *ctl,
> unsigned long hwirq,
> u32 **channel_hwirq)
> {
> - unsigned int reg, idx;
> + unsigned int idx;
>
> spin_lock(&ctl->lock);
>
> @@ -129,10 +168,7 @@ meson_gpio_irq_request_channel(struct
> meson_gpio_irq_controller *ctl,
> * Setup the mux of the channel to route the signal of the pad
> * to the appropriate input of the GIC
> */
> - reg = meson_gpio_irq_channel_to_reg(idx);
> - meson_gpio_irq_update_bits(ctl, reg,
> - 0xff << REG_PIN_SEL_SHIFT(idx),
> - hwirq << REG_PIN_SEL_SHIFT(idx));
> + ctl->params->ops.gpio_irq_sel_pin(ctl, idx, hwirq);
>
> /*
> * Get the hwirq number assigned to this channel through
> @@ -173,7 +209,9 @@ static int meson_gpio_irq_type_setup(struct
> meson_gpio_irq_controller *ctl,
> {
> u32 val = 0;
> unsigned int idx;
> + const struct meson_gpio_irq_params *params;
>
> + params = ctl->params;
> idx = meson_gpio_irq_get_channel_idx(ctl, channel_hwirq);
>
> /*
> @@ -190,22 +228,22 @@ static int meson_gpio_irq_type_setup(struct
> meson_gpio_irq_controller *ctl,
> * precedence over the other edge/polarity settings
> */
> if (type == IRQ_TYPE_EDGE_BOTH) {
> - if (!ctl->params->support_edge_both)
> + if (!params->support_edge_both)
> return -EINVAL;
>
> - val |= REG_BOTH_EDGE(idx);
> + val |= REG_BOTH_EDGE(params, idx);
> } else {
> if (type & (IRQ_TYPE_EDGE_RISING | IRQ_TYPE_EDGE_FALLING))
> - val |= REG_EDGE_POL_EDGE(idx);
> + val |= REG_EDGE_POL_EDGE(params, idx);
>
> if (type & (IRQ_TYPE_LEVEL_LOW | IRQ_TYPE_EDGE_FALLING))
> - val |= REG_EDGE_POL_LOW(idx);
> + val |= REG_EDGE_POL_LOW(params, idx);
> }
>
> spin_lock(&ctl->lock);
>
> meson_gpio_irq_update_bits(ctl, REG_EDGE_POL,
> - REG_EDGE_POL_MASK(idx), val);
> + REG_EDGE_POL_MASK(params, idx), val);
>
> spin_unlock(&ctl->lock);
>
> @@ -371,6 +409,9 @@ static int __init meson_gpio_irq_parse_dt(struct
> device_node *node,
> return ret;
> }
>
> + if (ctl->params->ops.gpio_irq_init)
> + ctl->params->ops.gpio_irq_init(ctl);
It would make sense to provide a dummy init() method, since
you have all the infrastructure already.
> +
> return 0;
> }
Thanks,
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2019-12-06 13:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 12:17 [PATCH 0/4] irqchip/meson-gpio: Add support for Meson-A1 SoC Qianggui Song
2019-12-06 12:17 ` [PATCH 1/4] dt-bindings: interrupt-controller: New binding for Meson-A1 SoCs Qianggui Song
2019-12-06 12:17 ` [PATCH 2/4] irqchip/meson-gpio: rework meson irqchip driver to support meson-A1 SoCs Qianggui Song
2019-12-06 13:13 ` Marc Zyngier [this message]
2019-12-10 2:08 ` Qianggui Song
2019-12-11 17:26 ` Marc Zyngier
2019-12-12 11:13 ` Qianggui Song
2019-12-06 12:17 ` [PATCH 3/4] irqchip/meson-gpio: Add support for meson a1 SoCs Qianggui Song
2019-12-06 12:17 ` [PATCH 4/4] arm64: dts: meson: a1: add gpio interrupt controller support Qianggui Song
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=542e3e819e584d6e433d2c4276c3b379@www.loen.fr \
--to=maz@kernel.org \
--cc=hanjie.lin@amlogic.com \
--cc=jason@lakedaemon.net \
--cc=jbrunet@baylibre.com \
--cc=jianxin.pan@amlogic.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=qianggui.song@amlogic.com \
--cc=tglx@linutronix.de \
--cc=xingyu.chen@amlogic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®