lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <2fea5a0c-7410-97fd-91d1-ae6a06ab1a52@gmail.com>
Date:   Wed, 4 Jan 2017 08:47:43 +0530
From:   valmiki <valmikibow@...il.com>
To:     linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
Cc:     helgaas@...nel.org, marc.zyngier@....com, arnd@...db.de,
        mark.rutland@....com
Subject: Need clarity on PCIe MSI interrupt in device tree

Hi,

I have confusion on MSI interrupt flags in PCIe documetation.

MSI interrupts are edge triggered, but i see some controllers use 
Ex:tegra <0 99 0x4>, here interrupt flags show 0x4 which means level 
sensitive as per include/dt-bindings/interrupt-controller/irq.h.

May i know why is it like this, why MSI depicted as level sensitive in 
device tree.

Regards,
valmiki

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ