All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Péter Ujfalusi" <peter.ujfalusi@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Samuel Ortiz <samuel.ortiz@intel.com>,
	Dmitry Torokhov <dtor@mail.ru>, Liam Girdwood <lrg@ti.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	Misael Lopez Cruz <misael.lopez@ti.com>,
	linux-input@vger.kernel.org
Subject: Re: Re: [PATCH v2 2/6] MFD: twl6040: Cache the vibra control registers
Date: Wed, 12 Oct 2011 10:53:18 +0300	[thread overview]
Message-ID: <2683250.RVKxy9YcCb@barack> (raw)
In-Reply-To: <20111011144824.GE1098@sirena.org.uk>

On Tuesday 11 October 2011 15:48:24 Mark Brown wrote:
> It strikes me that it might be useful to just convert the driver to
> regmap and get cache for everything...

Good idea, I'll take a look at regmap
 
> Anyway, could you please restructure this series to minimize the
> dependency on the input subsystem?  Then we can get the rest of it
> applied.

Will send the v3 series soon.

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

WARNING: multiple messages have this Message-ID (diff)
From: "Péter Ujfalusi" <peter.ujfalusi@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Samuel Ortiz <samuel.ortiz@intel.com>,
	Dmitry Torokhov <dtor@mail.ru>, Liam Girdwood <lrg@ti.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	Misael Lopez Cruz <misael.lopez@ti.com>,
	linux-input@vger.kernel.org
Subject: Re: Re: [PATCH v2 2/6] MFD: twl6040: Cache the vibra control registers
Date: Wed, 12 Oct 2011 10:53:18 +0300	[thread overview]
Message-ID: <2683250.RVKxy9YcCb@barack> (raw)
In-Reply-To: <20111011144824.GE1098@sirena.org.uk>

On Tuesday 11 October 2011 15:48:24 Mark Brown wrote:
> It strikes me that it might be useful to just convert the driver to
> regmap and get cache for everything...

Good idea, I'll take a look at regmap
 
> Anyway, could you please restructure this series to minimize the
> dependency on the input subsystem?  Then we can get the rest of it
> applied.

Will send the v3 series soon.

--
Péter

  parent reply	other threads:[~2011-10-12  7:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-23  6:49 [PATCH v2 0/6] ASoC/MFD/Input: twl6040: Support for audio driven vibra Peter Ujfalusi
2011-09-23  6:49 ` [PATCH v2 1/6] Input: twl6040: Simplify vibra regsiter definitions Peter Ujfalusi
2011-09-23  6:49 ` [PATCH v2 2/6] MFD: twl6040: Cache the vibra control registers Peter Ujfalusi
2011-09-23  6:49   ` Peter Ujfalusi
2011-10-10 19:04   ` Samuel Ortiz
2011-10-11 14:48   ` Mark Brown
2011-10-11 14:48     ` Mark Brown
2011-10-11 16:01     ` Dmitry Torokhov
2011-10-12  8:05       ` Péter Ujfalusi
2011-10-12  8:05         ` Péter Ujfalusi
2011-10-12  7:53     ` Péter Ujfalusi [this message]
2011-10-12  7:53       ` Péter Ujfalusi
2011-09-23  6:49 ` [PATCH v2 3/6] MFD: twl6040: function to query the vibra status for clients Peter Ujfalusi
2011-10-10 19:05   ` Samuel Ortiz
2011-10-11  3:49     ` Ujfalusi, Peter
2011-10-11  3:49       ` Ujfalusi, Peter
2011-09-23  6:49 ` [PATCH v2 4/6] Input: twl6040-vibra: Check the selected path for vibra Peter Ujfalusi
2011-09-23  6:49 ` [PATCH v2 5/6] ASoC: omap-mcpdm: Correct the supported number of channels Peter Ujfalusi
2011-09-23 10:52   ` Mark Brown
2011-09-23  6:49 ` [PATCH v2 6/6] ASoC: twl6040: Support for vibra output paths Peter Ujfalusi
2011-10-10 18:36 ` [PATCH v2 0/6] ASoC/MFD/Input: twl6040: Support for audio driven vibra Ujfalusi, Peter
2011-10-10 18:36   ` Ujfalusi, Peter

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=2683250.RVKxy9YcCb@barack \
    --to=peter.ujfalusi@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=dtor@mail.ru \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=misael.lopez@ti.com \
    --cc=samuel.ortiz@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 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.