public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: mazziesaccount@gmail.com, gregkh@linuxfoundation.org,
	rafael@kernel.org, linux-kernel@vger.kernel.org,
	heikki.haikola@fi.rohmeurope.com,
	mikko.mutanen@fi.rohmeurope.com
Subject: Re: [RFC v2] regmap: regmap-irq: Add main status register support
Date: Mon, 17 Dec 2018 17:32:44 +0000	[thread overview]
Message-ID: <20181217173244.GE27909@sirena.org.uk> (raw)
In-Reply-To: <20181214140812.GA28723@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 755 bytes --]

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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-12-17 17:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-14 14:08 [RFC v2] regmap: regmap-irq: Add main status register support Matti Vaittinen
2018-12-17 17:32 ` Mark Brown [this message]
2018-12-18  8:58   ` Matti Vaittinen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181217173244.GE27909@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.haikola@fi.rohmeurope.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matti.vaittinen@fi.rohmeurope.com \
    --cc=mazziesaccount@gmail.com \
    --cc=mikko.mutanen@fi.rohmeurope.com \
    --cc=rafael@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox