From: "majun (F)" <majun258@huawei.com>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: <Catalin.Marinas@arm.com>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <Will.Deacon@arm.com>,
<mark.rutland@arm.com>, <jason@lakedaemon.net>,
<tglx@linutronix.de>, <lizefan@huawei.com>, <huxinwei@huawei.com>,
<dingtianhong@huawei.com>, <zhaojunhua@hisilicon.com>,
<liguozhu@hisilicon.com>, <xuwei5@hisilicon.com>,
<wei.chenwei@hisilicon.com>, <guohanjun@huawei.com>,
<wuyun.wu@huawei.com>, <guodong.xu@linaro.org>,
<haojian.zhuang@linaro.org>, <zhangfei.gao@linaro.org>,
<usman.ahmad@linaro.org>, <klimov.linux@gmail.com>,
<gabriele.paoloni@huawei.com>
Subject: Re: [PATCH v8 4/4] irqchip:implement the mbigen irq chip operation functions
Date: Thu, 19 Nov 2015 18:53:01 +0800 [thread overview]
Message-ID: <564DAA0D.80200@huawei.com> (raw)
In-Reply-To: <20151119094127.7db3522c@arm.com>
Hi Marc:
在 2015/11/19 17:41, Marc Zyngier 写道:
> On Fri, 6 Nov 2015 16:28:42 +0800
> MaJun <majun258@huawei.com> wrote:
>
>> From: Ma Jun <majun258@huawei.com>
>>
[...]
>> struct mbigen_irq_data {
>> void __iomem *base;
>> + unsigned int pin_offset;
>> unsigned int reg_vec;
>> + unsigned int reg_type;
>> + unsigned int reg_clear;
>> + unsigned int type;
>> };
>
> I have the same comments here as for patch #3. You're storing
> information that are just a pure function of hwirq, and essentially
> free to compute at runtime. Please fix it in a similar way.
>
ok, I'll fix this.
>>
>> static inline int get_mbigen_vec_reg(u32 nid, u32 offset)
>> @@ -77,8 +98,68 @@ static inline int get_mbigen_vec_reg(u32 nid, u32 offset)
>> + REG_MBIGEN_VEC_OFFSET;
>> }
>>
>> +static int get_mbigen_type_reg(u32 nid, u32 offset)
>> +{
>> + int ofst;
>> +
>> + ofst = offset / 32 * 4;
>> + return ofst + nid * MBIGEN_NODE_OFFSET
>> + + REG_MBIGEN_TYPE_OFFSET;
>> +}
>> +
>> +static int get_mbigen_clear_reg(u32 nid, u32 offset)
>> +{
>> + int ofst;
>> +
>> + ofst = offset / 32 * 4;
>> + return ofst + nid * MBIGEN_NODE_OFFSET
>> + + REG_MBIGEN_CLEAR_OFFSET;
>> +}
>> +
>> +static void mbigen_eoi_irq(struct irq_data *data)
>> +{
>> + struct mbigen_irq_data *mgn_irq_data = irq_data_get_irq_chip_data(data);
>> + u32 mask;
>> +
>> + /* only level triggered interrupt need to clear status */
>> + if (mgn_irq_data->type == IRQ_TYPE_LEVEL_HIGH) {
>> + mask = 1 << (mgn_irq_data->pin_offset % 32);
>> + writel_relaxed(mask, mgn_irq_data->reg_clear + mgn_irq_data->base);
>> + }
>
> Does this have the effect of regenerating an edge if the level is still
> active?
>
yes, it does.
>> +
>> + irq_chip_eoi_parent(data);
>> +}
>> +
>> +static int mbigen_set_type(struct irq_data *d, unsigned int type)
>> +{
>> + struct mbigen_irq_data *mgn_irq_data = irq_data_get_irq_chip_data(d);
>> + u32 mask;
>> + int val;
>> +
>> + if (type != IRQ_TYPE_LEVEL_HIGH && type != IRQ_TYPE_EDGE_RISING)
>> + return -EINVAL;
>
> If these are the only two interrupt triggers you support, then you
> should update the documentation (DT binding) to reflect this, as all it
> says is "The 2nd cell is the interrupt trigger type" which is pretty
> vague.
>
I'll specify this point in DT binding.
Thanks
Ma Jun
>> +
>> + mask = 1 << (mgn_irq_data->pin_offset % 32);
>> +
>> + val = readl_relaxed(mgn_irq_data->reg_type + mgn_irq_data->base);
>> +
>> + if (type == IRQ_TYPE_LEVEL_HIGH)
>> + val |= mask;
>> + else if (type == IRQ_TYPE_EDGE_RISING)
>> + val &= ~mask;
>
> Given that you've excluded anything but LEVEL_HIGH and EDGE_RISING
> already, the second if() is superfluous.
>
>> +
>> + writel_relaxed(val, mgn_irq_data->reg_type + mgn_irq_data->base);
>> +
>> + return 0;
>> +}
>> +
>> static struct irq_chip mbigen_irq_chip = {
>> .name = "mbigen-v2",
>> + .irq_mask = irq_chip_mask_parent,
>> + .irq_unmask = irq_chip_unmask_parent,
>> + .irq_eoi = mbigen_eoi_irq,
>> + .irq_set_type = mbigen_set_type,
>> + .irq_set_affinity = irq_chip_set_affinity_parent,
>> };
>>
>> static void mbigen_write_msg(struct msi_desc *desc, struct msi_msg *msg)
>> @@ -94,10 +175,11 @@ static void mbigen_write_msg(struct msi_desc *desc, struct msi_msg *msg)
>> writel_relaxed(val, mgn_irq_data->reg_vec + mgn_irq_data->base);
>> }
>>
>> -static struct mbigen_irq_data *set_mbigen_irq_data(int hwirq)
>> +static struct mbigen_irq_data *set_mbigen_irq_data(int hwirq,
>> + unsigned int type)
>> {
>> struct mbigen_irq_data *datap;
>> - unsigned int nid, pin_offset;
>> + unsigned int nid;
>>
>> datap = kzalloc(sizeof(*datap), GFP_KERNEL);
>> if (!datap)
>> @@ -106,10 +188,20 @@ static struct mbigen_irq_data *set_mbigen_irq_data(int hwirq)
>> /* get the mbigen node number */
>> nid = (hwirq - RESERVED_IRQ_PER_MBIGEN_CHIP) / IRQS_PER_MBIGEN_NODE + 1;
>>
>> - pin_offset = (hwirq - RESERVED_IRQ_PER_MBIGEN_CHIP)
>> + datap->pin_offset = (hwirq - RESERVED_IRQ_PER_MBIGEN_CHIP)
>> % IRQS_PER_MBIGEN_NODE;
>>
>> - datap->reg_vec = get_mbigen_vec_reg(nid, pin_offset);
>> + datap->reg_vec = get_mbigen_vec_reg(nid, datap->pin_offset);
>> + datap->reg_type = get_mbigen_type_reg(nid, datap->pin_offset);
>> +
>> + /* no clear register for edge triggered interrupt */
>> + if (type == IRQ_TYPE_EDGE_RISING)
>> + datap->reg_clear = 0;
>> + else
>> + datap->reg_clear = get_mbigen_clear_reg(nid,
>> + datap->pin_offset);
>> +
>> + datap->type = type;
>> return datap;
>> }
>
> That function can entirely go.
>
>>
>> @@ -151,7 +243,7 @@ static int mbigen_irq_domain_alloc(struct irq_domain *domain,
>> return err;
>>
>> /* set related information of this irq */
>> - mgn_irq_data = set_mbigen_irq_data(hwirq);
>> + mgn_irq_data = set_mbigen_irq_data(hwirq, type);
>> if (!mgn_irq_data)
>> return err;
>>
>
> Thanks,
>
> M.
>
prev parent reply other threads:[~2015-11-19 10:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 8:28 [PATCH v8 0/4] irqchip:support mbigen interrupt controller MaJun
2015-11-06 8:28 ` [PATCH v8 1/4] dt-binding:Documents of the mbigen bindings MaJun
2015-11-18 17:50 ` Marc Zyngier
2015-11-19 10:53 ` majun (F)
2015-11-06 8:28 ` [PATCH v8 2/4] irqchip: add platform device driver for mbigen device MaJun
2015-11-19 8:48 ` Marc Zyngier
2015-11-06 8:28 ` [PATCH v8 3/4] irqchip:create irq domain for each " MaJun
2015-11-18 19:30 ` Marc Zyngier
2015-11-06 8:28 ` [PATCH v8 4/4] irqchip:implement the mbigen irq chip operation functions MaJun
2015-11-19 9:41 ` Marc Zyngier
2015-11-19 10:53 ` majun (F) [this message]
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=564DAA0D.80200@huawei.com \
--to=majun258@huawei.com \
--cc=Catalin.Marinas@arm.com \
--cc=Will.Deacon@arm.com \
--cc=dingtianhong@huawei.com \
--cc=gabriele.paoloni@huawei.com \
--cc=guodong.xu@linaro.org \
--cc=guohanjun@huawei.com \
--cc=haojian.zhuang@linaro.org \
--cc=huxinwei@huawei.com \
--cc=jason@lakedaemon.net \
--cc=klimov.linux@gmail.com \
--cc=liguozhu@hisilicon.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=tglx@linutronix.de \
--cc=usman.ahmad@linaro.org \
--cc=wei.chenwei@hisilicon.com \
--cc=wuyun.wu@huawei.com \
--cc=xuwei5@hisilicon.com \
--cc=zhangfei.gao@linaro.org \
--cc=zhaojunhua@hisilicon.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