All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joonyoung Shim <jy0922.shim@samsung.com>
To: Naveen Krishna Ch <naveenkrishna.ch@gmail.com>
Cc: kyungmin.park@samsung.com, alsa-devel@alsa-project.org,
	knhoon.baik@samsung.com
Subject: Re: A question about the soc jack status
Date: Wed, 28 Oct 2009 18:04:18 +0900	[thread overview]
Message-ID: <4AE80912.1020500@samsung.com> (raw)
In-Reply-To: <ef0d8a250910280032n7f9a12c0x12dd7e9c30ad3e25@mail.gmail.com>

On 10/28/2009 4:32 PM, Naveen Krishna Ch wrote:
> 2009/10/28 Joonyoung Shim <jy0922.shim@samsung.com>
> 
>> Hi, all.
>>
>> I have a question about soc jack. I know the soc jack reports the jack
>> status when the jack status is change only. For example when the jack
>> is inserted or released, the soc jack reports the jack status to user
>> via input subsystem.
>>
>> But i want to know the jack status always regardless of the event to
>> insert or release a jack. For example we can check the jack status
>> always if the jack status is reported via sysfs file.
>>
> There is a /sys/class/soc/jack/status
> Dont remember the exact path.
> Cat of that file will tell us right
> 

I cannot find "jack" word under /sys directory.
Can you give me the exact path?

>> So, is there how to know the jack status always the currently?
>> _______________________________________________
>> Alsa-devel mailing list
>> Alsa-devel@alsa-project.org
>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>>
> 
> 
> 

  parent reply	other threads:[~2009-10-28  9:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-28  7:16 A question about the soc jack status Joonyoung Shim
     [not found] ` <ef0d8a250910280032n7f9a12c0x12dd7e9c30ad3e25@mail.gmail.com>
2009-10-28  9:04   ` Joonyoung Shim [this message]
2009-10-28 10:21 ` Mark Brown

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=4AE80912.1020500@samsung.com \
    --to=jy0922.shim@samsung.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=knhoon.baik@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=naveenkrishna.ch@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.