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-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 9 Nov 2021 14:42:35 -0800
From:   Saravana Kannan <saravanak@...gle.com>
To:     Puranjay Mohan <puranjay12@...il.com>
Cc:     gregkh@...uxfoundation.org, rafael@...nel.org,
        heikki.krogerus@...ux.intel.com, andriy.shevchenko@...ux.intel.com,
        kuba@...nel.org, linux-kernel@...r.kernel.org, lars@...afoo.de,
        Michael.Hennerich@...log.com, jic23@...nel.org,
        linux-iio@...r.kernel.org
Subject: Re: [PATCH v2 0/2] device property: Adding fwnode_irq_get_byname()

On Tue, Nov 9, 2021 at 12:09 PM Puranjay Mohan <puranjay12@...il.com> wrote:
>
> The first patch in this series adds the fwnode_irq_get_byname() which is
> the generic version of the of_irq_get_byname(). It is used to get the
> IRQ number from name of the interrupt.
>
> The second patch in this series uses the fwnode_irq_get_byname()
> function in the IIO driver of the ADXL355 accelerometer. The driver has
> been tested after applying this patch on a Raspberry PI. The ADXL355 was
> connected to the Raspberry Pi using I2C and fwnode_irq_get_byname() was
> used to get the IRQ number for the "DRDY" interrupt. Earlier this driver
> was using of_irq_get_byname() to get this IRQ number.

Why do we need these changes though? Is there a non-OF device this
driver would ever probe?

-Saravana

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ