From: arrao@cdac.in (Raghavendra)
To: kernelnewbies@lists.kernelnewbies.org
Subject: sysfs bind/unbind attributes usage
Date: Tue, 01 Jul 2014 14:37:20 +0530 [thread overview]
Message-ID: <53B27A48.3060000@cdac.in> (raw)
Hello,
I would like to know more about manually probing/removing the devices
through sysfs attributes.
After searching for a while I came across two attributes 'bind' and
'unbind' present in all the drivers.
Now how may I correctly use them to probe my devices.
I sense the probing syntax is different for different kinds of drivers
(I2C, SPI, PCI, USB, etc).
I am mainly looking for probing I2C and SPI devices.
Also I found related attributes called 'new_id and remove_id' (for PCI
drivers) and also 'new_device and delete_device' (present in the i2c
adapter devices). Now how are they different from the bind/unbind
attributes, because as far as I know, even they do the same thing.
Could any one guide me through any documentation regarding all these issues
Thanks,
Raghavendra
-------------------------------------------------------------------------------------------------------------------------------
[ C-DAC is on Social-Media too. Kindly follow us at:
Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]
This e-mail is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies and the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
is strictly prohibited and appropriate legal action will be taken.
-------------------------------------------------------------------------------------------------------------------------------
next reply other threads:[~2014-07-01 9:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 9:07 Raghavendra [this message]
2014-07-01 10:43 ` sysfs bind/unbind attributes usage Bjørn Mork
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=53B27A48.3060000@cdac.in \
--to=arrao@cdac.in \
--cc=kernelnewbies@lists.kernelnewbies.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 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.