On 2014/8/1 21:52, Arnd Bergmann wrote:
On Wednesday 30 July 2014, Yijing Wang wrote:
On 2014/7/29 22:08, Arnd Bergmann wrote:
On Saturday 26 July 2014 11:08:37 Yijing Wang wrote:
The new data struct for generic MSI driver.
struct msi_irqs {
u8 msi_enabled:1; /* Enable flag */
On Monday 04 August 2014, Yijing Wang wrote:
I have another question is some drivers will request more than one
MSI/MSI-X IRQ, and the driver will use them to process different things.
Eg. network driver generally uses one of them to process trivial network
thins,
and others to
On Monday 04 August 2014, Yijing Wang wrote:
On 2014/8/1 21:52, Arnd Bergmann wrote:
On Wednesday 30 July 2014, Yijing Wang wrote:
On 2014/7/29 22:08, Arnd Bergmann wrote:
The other part I'm not completely sure about is how you want to
have MSIs map into normal IRQ descriptors. At the
Hi Yijing
-Original Message-
From: Yijing Wang [mailto:wangyij...@huawei.com]
Sent: Saturday, July 26, 2014 8:39 AM
To: linux-ker...@vger.kernel.org
Cc: Xinwei Hu; Wuyun; Bjorn Helgaas; linux-...@vger.kernel.org;
paul.mu...@huawei.com; James E.J. Bottomley; Marc Zyngier; linux-arm-
The method you describe here makes sense for PCI devices that are required
to support
legacy interrupts and may or may not support MSI on a given system, but not
so much
for platform devices for which we know exactly whether we want to use MSI
or legacy interrupts.
In particular if you
On 2014/8/4 22:45, Arnd Bergmann wrote:
On Monday 04 August 2014, Yijing Wang wrote:
I have another question is some drivers will request more than one
MSI/MSI-X IRQ, and the driver will use them to process different things.
Eg. network driver generally uses one of them to process trivial
