All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Peter 'p2' De Schrijver <peter.de-schrijver@nokia.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 2/3] Adapt twl4030 power code to new twl4030 code
Date: Wed, 8 Oct 2008 00:16:49 -0700	[thread overview]
Message-ID: <200810080016.49188.david-b@pacbell.net> (raw)
In-Reply-To: <20081008064913.GA4542@codecarver.research.nokia.com>

On Tuesday 07 October 2008, Peter 'p2' De Schrijver wrote:
> > And I can't help but wonder why this isn't just part of
> > the twl4030-core code, without even a platform device/driver.
> 
> If you think all this script loading stuff can go into twl4030-core, I
> can make a patch to move it there.

Well, link it with twl-core, call it as a subroutine,
add some kind of header to hold the subroutine decl.
Not unlike the linkage structure "today".

Right now I'm thinking the {core, irq, "power"} structure
will be OK, if the "irq" gets generalized so it's not just
the one SIH module (which I have, partially done) ... and
the "power" bits lose the board-specific stuff.

 
> > I didn't move it to drivers/mfd because it seemed almost all
> > SDP-specific.  But to the extent that it's something generic
> > and "part of the core", maybe that's where it should be.
> > Not necessarily part of the same file.
> > 
> 
> It's not SDP specific, but it is OMAP specific I think. At least I can't
> see use cases outside OMAP2/3.

We'll know when/if this is used on non-OMAP hardware!

Likely not soon.  I'd like to have the code build cleanly
on most hardware, so we get the build fixes and API update
that implies.  That's mostly IRQ cleanup.  Board designers
will do what they want, and I suspect you're right there.

- Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-10-08  7:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-07 14:34 [PATCH 0/3] Move twl4030 scripts to platform data Peter 'p2' De Schrijver
2008-10-07 14:34 ` [PATCH 1/3] Add twl4030 scripts to 3430sdp " Peter 'p2' De Schrijver
2008-10-07 14:34   ` [PATCH 2/3] Adapt twl4030 power code to new twl4030 code Peter 'p2' De Schrijver
2008-10-07 14:34     ` [PATCH 3/3] Add twl4030 power platform device Peter 'p2' De Schrijver
2008-10-07 16:19     ` [PATCH 2/3] Adapt twl4030 power code to new twl4030 code David Brownell
2008-10-08  6:49       ` Peter 'p2' De Schrijver
2008-10-08  7:16         ` David Brownell [this message]
2008-10-08  7:22         ` David Brownell
2008-11-08  0:05         ` David Brownell
2008-10-07 16:05 ` [PATCH 0/3] Move twl4030 scripts to platform data David Brownell

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=200810080016.49188.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-omap@vger.kernel.org \
    --cc=peter.de-schrijver@nokia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.