From: Hanjun Guo <guohanjun@huawei.com>
To: Yang Yingliang <yangyingliang@huawei.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: <marc.zyngier@arm.com>, <tglx@linutronix.de>,
Linuxarm <linuxarm@huawei.com>
Subject: Re: [PATCH v2 0/4] add support for MBIGEN generating message based SPIs
Date: Wed, 9 Jan 2019 18:18:10 +0800 [thread overview]
Message-ID: <08646b86-8228-4920-00cb-6c3f44c4484b@huawei.com> (raw)
In-Reply-To: <1540540280-26612-1-git-send-email-yangyingliang@huawei.com>
Hi Marc,
Sorry for ping you...
On 2018/10/26 15:51, Yang Yingliang wrote:
> Now MBIGENs have pins that used to generate SPIs,
> with
> 5052875 ("irqchip/gic-v3: Add support for Message Based Interrupts as an MSI controller"),
> we can support MBIGEN to generate message based SPIs by writing
> GICD_SETSPIR. This patchset add support for MBIGEN generating
> message based SPIs and a bugfix for MBI driver.
What's you suggestion for this patch set? We would like your input
for next steps.
>
>
> Patch #1 is a bugfix for MBI driver.
At least this patch can be merged first as it's an obvious bug,
without this patch, the MBI dirver can't work I think because
the mutex lock is not initialized.
Thanks
Hanjun
WARNING: multiple messages have this Message-ID (diff)
From: Hanjun Guo <guohanjun@huawei.com>
To: Yang Yingliang <yangyingliang@huawei.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: marc.zyngier@arm.com, tglx@linutronix.de, Linuxarm <linuxarm@huawei.com>
Subject: Re: [PATCH v2 0/4] add support for MBIGEN generating message based SPIs
Date: Wed, 9 Jan 2019 18:18:10 +0800 [thread overview]
Message-ID: <08646b86-8228-4920-00cb-6c3f44c4484b@huawei.com> (raw)
In-Reply-To: <1540540280-26612-1-git-send-email-yangyingliang@huawei.com>
Hi Marc,
Sorry for ping you...
On 2018/10/26 15:51, Yang Yingliang wrote:
> Now MBIGENs have pins that used to generate SPIs,
> with
> 5052875 ("irqchip/gic-v3: Add support for Message Based Interrupts as an MSI controller"),
> we can support MBIGEN to generate message based SPIs by writing
> GICD_SETSPIR. This patchset add support for MBIGEN generating
> message based SPIs and a bugfix for MBI driver.
What's you suggestion for this patch set? We would like your input
for next steps.
>
>
> Patch #1 is a bugfix for MBI driver.
At least this patch can be merged first as it's an obvious bug,
without this patch, the MBI dirver can't work I think because
the mutex lock is not initialized.
Thanks
Hanjun
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-09 10:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 7:51 [PATCH v2 0/4] add support for MBIGEN generating message based SPIs Yang Yingliang
2018-10-26 7:51 ` Yang Yingliang
2018-10-26 7:51 ` [PATCH v2 1/4] irqchip/gic-v3-mbi: fix uninitialized mbi_lock Yang Yingliang
2018-10-26 7:51 ` Yang Yingliang
2018-10-26 7:51 ` [PATCH v2 2/4] irqchip/mbigen: rename register marcros Yang Yingliang
2018-10-26 7:51 ` Yang Yingliang
2018-10-26 7:51 ` [PATCH v2 3/4] irqchip/mbigen: add support for a MBIGEN generating SPIs Yang Yingliang
2018-10-26 7:51 ` Yang Yingliang
2018-10-26 7:51 ` [PATCH v2 4/4] dt-bindings/irqchip/mbigen: add example of MBIGEN generate SPIs Yang Yingliang
2018-10-26 7:51 ` Yang Yingliang
2019-01-09 10:48 ` Marc Zyngier
2019-01-09 10:48 ` Marc Zyngier
2019-01-09 10:18 ` Hanjun Guo [this message]
2019-01-09 10:18 ` [PATCH v2 0/4] add support for MBIGEN generating message based SPIs Hanjun Guo
2019-01-09 10:33 ` Marc Zyngier
2019-01-09 10:33 ` Marc Zyngier
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=08646b86-8228-4920-00cb-6c3f44c4484b@huawei.com \
--to=guohanjun@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=marc.zyngier@arm.com \
--cc=tglx@linutronix.de \
--cc=yangyingliang@huawei.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.