linux-kernel - Re: [RFC v2] regmap: regmap-irq: Add main status register support

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: <20181217173244.GE27909@sirena.org.uk>
Date:   Mon, 17 Dec 2018 17:32:44 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Matti Vaittinen <matti.vaittinen@...rohmeurope.com>
Cc:     mazziesaccount@...il.com, gregkh@...uxfoundation.org,
        rafael@...nel.org, linux-kernel@...r.kernel.org,
        heikki.haikola@...rohmeurope.com, mikko.mutanen@...rohmeurope.com
Subject: Re: [RFC v2] regmap: regmap-irq: Add main status register support

On Fri, Dec 14, 2018 at 04:08:12PM +0200, Matti Vaittinen wrote:

> This is draft for approach proposed by Mark here:
> http://lkml.iu.edu/hypermail/linux/kernel/1812.1/07117.html

> Pretty untested and diff is done against tree where the level active IRQ
> support for regmap-irq was added. So please consider this just as a RFC
> introducing the concept. I will format correct and better tested patch if
> this is the preferred way to go.

Hrm, so the parsing code is indeed quite complicated.  I suspect it
could be simplified if instead of trying to allocate just what's used it
was a bit more wasteful and allocated the biggest arrays we might need
but I'm not sure how much that'd really help so yeah, doing it the other
way around might be better.

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