From: Clemens Ladisch <clemens@ladisch.de>
To: Shreshtha <shreshthakumar@gmail.com>
Cc: "Alsa-devel@alsa-project.org" <Alsa-devel@alsa-project.org>,
Lu Guanqun <guanqun.lu@intel.com>
Subject: Re: Accessing already probed snd_card in kernel space
Date: Fri, 15 Apr 2011 09:57:23 +0200 [thread overview]
Message-ID: <4DA7FA63.3070803@ladisch.de> (raw)
In-Reply-To: <BANLkTim6fPPjrNJE3Rijc4h3rnvRthJeTQ@mail.gmail.com>
Shreshtha wrote:
> Vibrator hardware is connected to D-Class amplifier of Audio block.
Does this mean that you have to generate the vibration waveform as
sound data and write it to the sound device? This would be rather
unwieldy in kernel space. (Just accessing a mixer control would be
possible.)
> But as you described that accessing from out side the sound subsystem is
> prohibited in Kernel.
It's not prohibited, it's just not the way the API was designed.
> So only way remains is to access the sound card from user space using ALSA
> lib APIs and replace current usage of sysfs for haptic feedback. Please
> suggest if it is right direction.
Is the sysfs API a _required_ Android API, or would Android allow you
to write a user space driver?
Regards,
Clemens
next prev parent reply other threads:[~2011-04-15 7:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 5:46 Accessing already probed snd_card in kernel space Shreshtha
2011-04-15 6:30 ` Lu Guanqun
2011-04-15 7:49 ` Shreshtha
2011-04-15 7:57 ` Clemens Ladisch [this message]
2011-04-15 8:27 ` Shreshtha
2011-04-15 8:36 ` Lu Guanqun
2011-04-15 9:00 ` Shreshtha
2011-04-28 5:55 ` Koul, Vinod
2011-04-15 7:37 ` Clemens Ladisch
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=4DA7FA63.3070803@ladisch.de \
--to=clemens@ladisch.de \
--cc=Alsa-devel@alsa-project.org \
--cc=guanqun.lu@intel.com \
--cc=shreshthakumar@gmail.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.