linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: haojian.zhuang@gmail.com (Haojian Zhuang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 02/09] mfd: support 88pm8606 in 860x driver
Date: Thu, 7 Jan 2010 22:40:50 -0500	[thread overview]
Message-ID: <771cded01001071940o3a97321bkf7eb14cd361cc4ff@mail.gmail.com> (raw)
In-Reply-To: <771cded01001071939i463d22c0jea400a56305cd489@mail.gmail.com>

On Thu, Jan 7, 2010 at 10:39 PM, Haojian Zhuang
<haojian.zhuang@gmail.com> wrote:
> On Thu, Jan 7, 2010 at 2:44 PM, Samuel Ortiz <sameo@linux.intel.com> wrote:
>> Hi Haojian,
>>
>> On Wed, Dec 09, 2009 at 08:11:22AM -0500, Haojian Zhuang wrote:
>>> From c5f9ccd5b1f2ce57b9e10b7e2b6c134fc8116f29 Mon Sep 17 00:00:00 2001
>>> From: Haojian Zhuang <haojian.zhuang@marvell.com>
>>> Date: Tue, 8 Dec 2009 09:05:28 -0500
>>> Subject: [PATCH] mfd: support 88pm8606 in 860x driver
>>>
>>> 88PM8606 and 88PM8607 are two discrete chips used for power management.
>>> Hardware designer can use them together or only one of them according to
>>> requirement.
>>>
>>> There's some logic tightly linked between these two chips. For example, USB
>>> charger driver needs to access both chips by I2C interface.
>>>
>>> Now share one driver to these two devices. Only one I2C client is identified
>>> in platform init data. If another chip is also used, user should mark it in
>>> companion_addr field of platform init data. Then driver could create another
>>> I2C client for the companion chip.
>>>
>>> All I2C operations are accessed by 860x-i2c driver. In order to support both
>>> I2C client address, the read/write API is changed in below.
>>>
>>> reg_read(client, offset)
>>> reg_write(client, offset, data)
>>>
>>> The benefit is that client drivers only need one kind of read/write API. I2C
>>> and MFD driver can be shared in both 8606 and 8607.
>> After merging this patch, I get many drivers/regulator/88pm8607.c build
>> failures. Could you please include fixes for this driver with this patch, and
>> also update patch #9 accordingly ?
>>
>
> Update these patches. #9 is merged into #2. #3 is also changed.
>
> Thanks
> Haojian
>

Attach compressed file as attachment.

Thanks
Haojian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mfd_8607.tgz
Type: application/x-gzip
Size: 22505 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100107/c3245cd0/attachment-0001.tgz>

  reply	other threads:[~2010-01-08  3:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09 13:11 [PATCH v2 02/09] mfd: support 88pm8606 in 860x driver Haojian Zhuang
2009-12-10 10:35 ` Samuel Ortiz
2009-12-16  5:29   ` Haojian Zhuang
2009-12-16  5:37     ` Haojian Zhuang
2010-01-07 19:44 ` Samuel Ortiz
2010-01-08  3:39   ` Haojian Zhuang
2010-01-08  3:40     ` Haojian Zhuang [this message]
2010-01-08 11:46     ` Samuel Ortiz

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=771cded01001071940o3a97321bkf7eb14cd361cc4ff@mail.gmail.com \
    --to=haojian.zhuang@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).