linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Péter Ujfalusi" <peter.ujfalusi@ti.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Samuel Ortiz <samuel.ortiz@intel.com>, 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 11:05:06 +0300	[thread overview]
Message-ID: <2188183.hGjzCdyui0@barack> (raw)
In-Reply-To: <20111011160142.GB10286@core.coreip.homeip.net>

On Tuesday 11 October 2011 09:01:42 Dmitry Torokhov wrote:
> I'm OK with all patches going through MFD - I do not believe it will
> cause any merge issues.

Thanks Dmitry.

> For the record I still do not like returning EBUSY when device is not
> available - I think if device can't serve any requests it should not
> exists at all.

While I tend to agree with this, in embedded systems this might (not 
certainly) cause issues. Embedded SW (middleware, high level) tends to take 
the underlaying HW as static.
Before I can do the dynamic input device creation/destruction I need to make 
sure that the userspace is ready for this.
I'm planning to address your concern regarding to twl6040, and at the same 
time I'm going to change the twl4030 vibra/MFD/audio driver to behave in a 
same way.

--
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

  reply	other threads:[~2011-10-12  8:05 UTC|newest]

Thread overview: 16+ 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-10-10 19:04   ` Samuel Ortiz
2011-10-11 14:48   ` Mark Brown
2011-10-11 16:01     ` Dmitry Torokhov
2011-10-12  8:05       ` 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-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

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=2188183.hGjzCdyui0@barack \
    --to=peter.ujfalusi@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=dmitry.torokhov@gmail.com \
    --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 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).