linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.ml.walleij@gmail.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
	linux-kernel@vger.kernel.org,
	STEricsson_nomadik_linux@list.st.com,
	Mattias Wallin <mattias.wallin@stericsson.com>
Subject: Re: [PATCH 1/3] MFD: renamed ab3100.h to abx500.h
Date: Sat, 17 Apr 2010 07:37:09 +0200	[thread overview]
Message-ID: <r2n63386a3d1004162237k9095e85fz40fede9ad501fb5c@mail.gmail.com> (raw)
In-Reply-To: <20100416152041.GA28863@sortiz.org>

2010/4/16 Samuel Ortiz <sameo@linux.intel.com>:
> On Tue, Apr 13, 2010 at 01:04:56AM +0200, Linus Walleij wrote:
>> The goal here is to make way for a more general interface for the
>> analog baseband chips ab3100 ab3550 ab550 and future chips.
> I have an initial question for you:

> Do you plan to have one single driver supporting the 3100, 3550 and the 550
> chips ?

Not really, just one common interface. The 3100, 3550 and 5500 share
sub-blocks so for example the RTC driver in drivers/rtc/rtc-ab3100.c should
be possible to use with either of them, but the core driver implementation
will likely differ. (We might need to rename the file for clarity though.)

A main point of difference will be how these are accessed: right now the
AB3100 and AB3550 are on the I2C bus, the AB5500 will have access
through a special on-chip controller instead.

So the driver/mfd/ab3100.c|ab3550.c|ab5500.c will be different, but all
implement the API from include/linux/mfd/abx500.h and subdrivers will
hopefully be possible to share.

Yours,
Linus Walleij

      reply	other threads:[~2010-04-17  5:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12 23:04 [PATCH 1/3] MFD: renamed ab3100.h to abx500.h Linus Walleij
2010-04-13  5:30 ` srinidhi
2010-04-13 15:14   ` Linus Walleij
2010-04-16 15:20 ` Samuel Ortiz
2010-04-17  5:37   ` Linus Walleij [this message]

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=r2n63386a3d1004162237k9095e85fz40fede9ad501fb5c@mail.gmail.com \
    --to=linus.ml.walleij@gmail.com \
    --cc=STEricsson_nomadik_linux@list.st.com \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mattias.wallin@stericsson.com \
    --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;
as well as URLs for NNTP newsgroup(s).