public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
	linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] mfd: dbx500/abx500: root out hardcoded IRQ assignments
Date: Tue, 11 Feb 2014 11:40:48 +0000	[thread overview]
Message-ID: <20140211114048.GO32042@lee--X1> (raw)
In-Reply-To: <1392114599-481-1-git-send-email-linus.walleij@linaro.org>

> The DBx500 and ABx500 should be getting their IRQs from the
> device tree and nowhere else. Get rid of all the static assignments
> everywhere, delete it from the driver, platform data and the
> board files in one swift strike.
> 
> Lots of cross-dependencies in the MFD drivers for PRCMU and
> AB8500 makes it necessary to strike everywhere at once to
> eradicate IRQs passed as resources and platform data to the left
> and right around the platform.
> 
> Cc: Mark Brown <broonie@kernel.org>
> Cc: Samuel Ortiz <sameo@linux.intel.com>
> Cc: Lee Jones <lee.jones@linaro.org>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> Sam/Lee: I'm looking for an ACK on this to take the result through
> ARM SoC.

Actually I have a better idea. Gather all of the Acks/head-nods you
need and I'll create an immutable branch for the pair of us to pull
from.

> I've been ambivalent on how to look up the IRQ resource for the
> AB8500 from the device tree (as it is hanging off the main GIC
> interrupt controller rather than the PRCMU) and eventually ended
> up with this solution. I experimented with modifying mfd-core.c
> to add resources from the device tree, but I didn't like the
> result, it seems MFD cells should get their resources exclusively
> from the parent instantiating the cell, so I ended up with this.

Well no one knows that h/w better than you do and the code looks fine
to be taking into account it _is_ the SoC and the relationship between
the AB8500 and DB8500.

> Maybe Broonie has ideas about this too?
> ---
>  arch/arm/mach-ux500/board-mop500-audio.c |   1 -
>  arch/arm/mach-ux500/cpu-db8500.c         |   4 -
>  arch/arm/mach-ux500/irqs-board-mop500.h  |  55 --------------
>  arch/arm/mach-ux500/irqs-db8500.h        | 125 -------------------------------
>  arch/arm/mach-ux500/irqs.h               |  49 ------------
>  drivers/mfd/ab8500-core.c                |  27 +++----
>  drivers/mfd/db8500-prcmu.c               |  34 ++++++---
>  include/linux/mfd/abx500/ab8500.h        |   2 -
>  include/linux/mfd/dbx500-prcmu.h         |   2 -
>  9 files changed, 36 insertions(+), 263 deletions(-)
>  delete mode 100644 arch/arm/mach-ux500/irqs-board-mop500.h
>  delete mode 100644 arch/arm/mach-ux500/irqs-db8500.h
>  delete mode 100644 arch/arm/mach-ux500/irqs.h

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2014-02-11 11:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11 10:29 [PATCH] mfd: dbx500/abx500: root out hardcoded IRQ assignments Linus Walleij
2014-02-11 11:40 ` Lee Jones [this message]
2014-02-11 11:55   ` Linus Walleij
2014-02-11 17:39 ` Mark Brown
2014-02-13 13:11 ` Linus Walleij
2014-02-13 13:17   ` Lee Jones
2014-02-14 10:46     ` Linus Walleij
2014-02-14 16:54       ` Arnd Bergmann
2014-02-24 13:40         ` Linus Walleij
2014-02-24 13:59           ` Lee Jones

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=20140211114048.GO32042@lee--X1 \
    --to=lee.jones@linaro.org \
    --cc=broonie@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sameo@linux.intel.com \
    /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