linux-kernel - Re: [PATCH 1/4] MFD: Palmas: Add Interrupt feature

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]

Message-ID: <20130617161615.GH1403@sirena.org.uk>
Date:	Mon, 17 Jun 2013 17:16:15 +0100
From:	Mark Brown <broonie@...nel.org>
To:	J Keerthy <j-keerthy@...com>
Cc:	linux-omap@...r.kernel.org, ldewangan@...dia.com,
	sameo@...ux.intel.com, grant.likely@...retlab.ca,
	swarren@...dia.com, linux-kernel@...r.kernel.org,
	linux-doc@...r.kernel.org, gg@...mlogic.co.uk
Subject: Re: [PATCH 1/4] MFD: Palmas: Add Interrupt feature

On Mon, Jun 17, 2013 at 05:39:11PM +0530, J Keerthy wrote:

> Palmas PMICs have an INT line. This line is one single
> Interrupt line to the application processor. The interrupt
> feature enables to selectively request irq for only those
> specific chips which have INT line connected to a valid
> IRQ line of the application processor.

Does the support for the interrupt line need to be explicitly flagged
like this or can the driver not simply support an interrupt line not
being configured?  That would also support cases where the hardware has
an interrupt line but the system integrator has opeted not to connect it
for some reason which seems generally more flexible than doing things on
a chip ID basis.

> +/**
> + * DOC: Palmas PMIC feature types
> + *

Is "DOC: " normal kerneldoc?

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)