public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@linux.intel.com>
To: Andres Salomon <dilinger@queued.net>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	linux-kernel@vger.kernel.org
Subject: Re: MFD sharing support (v3, full)
Date: Mon, 28 Feb 2011 17:39:28 +0100	[thread overview]
Message-ID: <20110228163836.GA5263@sortiz-mobl> (raw)
In-Reply-To: <1297998456-7615-1-git-send-email-dilinger@queued.net>

Hi Andres,

On Thu, Feb 17, 2011 at 07:07:07PM -0800, Andres Salomon wrote:
> Here's all of my third attempt at MFD cell sharing.  This includes all
> parts; some of the patches from v2 are being resent without changes.  I
> apologize for the noise, but since I screwed up the threading in the first 
> batch and people were having trouble finding some of the patches, I figured
> I'd resend everything together.  There are some changes in there as well;
> they've been marked in commit messages.
> 
> This whole set does the following things:
>  - make mfd_cell structs always accessible to platform devices
>  - adjust the mfd_cell API to (hopefully) be cleaner, replacing platform_data
> and driver_data with mfd_data
>  - add wrapper functions to access mfd cell and data fields
>  - adjust all mfd clients/drivers to use the new API
>  - add a reference counting wrapper for mfd_cell's enable/disable hooks
>  - add platform device sharing wrappers to allow mfd clients to create
>    new platform devices (at the same time as platform drivers are being
>    registered)
>  - update the cs5535-mfd driver (and clients) to make use of the new
>    sharing code
> 
> This effectively provides the ability for mfd clients to share a single 
> mfd_cell, and provide the framework for mfd-core be handle shared hardware
> resources.
Thanks a lot for that. I applied all patches now. I have some really minor
comment regarding the naming in patch #28, but we can fix that later.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

      parent reply	other threads:[~2011-02-28 16:39 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-18  3:07 MFD sharing support (v3, full) Andres Salomon
2011-02-18  3:07 ` [PATCH 01/29] mfd-core: fix up typos/vagueness in comment Andres Salomon
2011-02-18  3:07 ` [PATCH 02/29] mfd-core: unconditionally add mfd_cell to every platform_device Andres Salomon
2011-02-18  3:07 ` [PATCH 03/29] jz4740: mfd_cell is now implicitly available to drivers Andres Salomon
2011-02-18  3:07 ` [PATCH 04/29] ab3550: " Andres Salomon
2011-02-18  3:07 ` [PATCH 05/29] ab3100: mfd_cell is now implicitly available to drivers (v2) Andres Salomon
2011-02-18  3:07 ` [PATCH 06/29] asic3: mfd_cell is now implicitly available to drivers Andres Salomon
2011-02-18  3:07 ` [PATCH 07/29] htc-pasic3: " Andres Salomon
2011-02-18  3:07 ` [PATCH 08/29] timberdale: mfd_cell is now implicitly available to drivers (v2) Andres Salomon
2011-02-18  3:07 ` [PATCH 09/29] t7166xb: mfd_cell is now implicitly available to drivers Andres Salomon
2011-02-25  9:05   ` Artem Bityutskiy
2011-02-25 10:47     ` Samuel Ortiz
2011-02-18  3:07 ` [PATCH 10/29] wl1273: " Andres Salomon
2011-02-18  3:07 ` [PATCH 11/29] sh_mobile_sdhi: " Andres Salomon
2011-02-18  3:07 ` [PATCH 12/29] tc6393xb: " Andres Salomon
2011-02-18  3:07 ` [PATCH 13/29] twl4030: mfd_cell is now implicitly available to drivers (v2) Andres Salomon
2011-02-18  6:44   ` Peter Ujfalusi
2011-02-18  3:07 ` [PATCH 14/29] tc6387xb: mfd_cell is now implicitly available to drivers Andres Salomon
2011-02-18  3:07 ` [PATCH 15/29] janz: mfd_cell is now implicitly available to drivers (v2) Andres Salomon
2011-02-18  3:07 ` [PATCH 16/29] mc13xxx: " Andres Salomon
2011-02-18  3:07 ` [PATCH 17/29] mfd-core: drop data_size from mfd_cell struct Andres Salomon
2011-02-18  3:07 ` [PATCH 18/29] mfd-core: rename platform_data field of mfd_cell to mfd_data Andres Salomon
2011-02-18  3:07 ` [PATCH 19/29] davinci_voicecodec: use mfd_data instead of driver_data Andres Salomon
2011-02-18  3:07 ` [PATCH 20/29] wm8400-codec: use mfd_data instead of driver_data (v2) Andres Salomon
2011-02-18  3:51   ` Mark Brown
2011-02-18  3:07 ` [PATCH 21/29] ds1wm: use mfd_data instead of driver_data Andres Salomon
2011-02-18  3:07 ` [PATCH 22/29] tmio-mmc: " Andres Salomon
2011-02-18  3:07 ` [PATCH 23/29] tmio-nand: " Andres Salomon
2011-02-18  3:07 ` [PATCH 24/29] tmio-fb: " Andres Salomon
2011-02-18  3:07 ` [PATCH 25/29] rdc321x-southbridge: use mfd_data instead of driver_data (v2) Andres Salomon
2011-02-18  3:07 ` [PATCH 26/29] mfd-core: remove driver_data field from mfd_cell Andres Salomon
2011-02-18  3:07 ` [PATCH 27/29] mfd-core: add refcounting support to mfd_cells (v2) Andres Salomon
2011-02-28 16:39   ` Samuel Ortiz
2011-02-18  3:07 ` [PATCH 28/29] mfd-core: add platform_device sharing support for mfd (v2) Andres Salomon
2011-02-28 16:40   ` Samuel Ortiz
2011-02-18  3:07 ` [PATCH 29/29] cs5535-mfd: add sharing for acpi/pms cells Andres Salomon
2011-02-28 16:39 ` Samuel Ortiz [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=20110228163836.GA5263@sortiz-mobl \
    --to=sameo@linux.intel.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=dilinger@queued.net \
    --cc=linux-kernel@vger.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