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>] [day] [month] [year] [list]
Message-ID: <fc6ec56f-77a4-aec6-debb-ab5f1fde9ffa@gmail.com>
Date:   Sat, 7 Jan 2017 07:54:40 +0530
From:   valmiki <valmikibow@...il.com>
To:     linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
Cc:     Marc Zyngier <marc.zyngier@....com>, helgaas@...nel.org,
        arnd@...db.de
Subject: Need clarity on legacy RC interrupt handling

Hi,

Legacy interrupts are level triggered, but i see some RC drivers use 
flow handler "handle_simple_irq" instead why they are not using 
"handle_level_irq" ?

Why they are registering dummy_irq_chip with "handle_simple_irq", if 
they use this chip how the irq type is set for this virtual irq (level 
or edge).

Regards,
vamiki

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ