From: "Madhusudhan Chikkature Rajashekar" <madhu.cr@ti.com>
To: linux-omap-open-source@linux.omap.com
Subject: HDQ/1-wire module
Date: Wed, 7 Nov 2007 14:12:15 +0530 [thread overview]
Message-ID: <005a01c8211a$1a143f60$918818ac@ent.ti.com> (raw)
Hi All,
This is regarding the HDQ/1-wire support for omap24xx/34xx.
The controller on the above OMAP platforms supports both HDQ and 1-wire protocol.The difference between HDQ and 1-wire protocol is
very minimal as explained below.
HDQ Mode:
In HDQ mode, the firmware does not require the host to create an initialization pulse to the slave.
However, the slave can be reset by using an initialization pulse (also referred to as a break pulse).
The slave does not respond with a presence pulse.
1-Wire Mode:
In 1-Wire protocol, the host first sends an initialization pulse (by pulling the line to a logic-low state)
and then waits for the slave to respond with a presence pulse before enabling any communication sequence.
A typical application of the HDQ/1-Wire module is the communication with battery monitor (gas gauge)
integrated circuits.
Has anyone in the past worked on the above module or has written a driver for the same? I can not recollect of having read any mails
on the above module
in the list. Please correct me if I am wrong.
There is no support for HDQ devices as of today in Linux. Whereas there is a W1 subsystem for 1-wire devices. Right now, I only have
a device
that is complaint to HDQ protocol only.I guess we can still write a driver to support this which can be integrated to the 1-wire
subsystem. If anyone has a different opinion, please do share the views.
Regards,
Madhu
next reply other threads:[~2007-11-07 8:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 8:42 Madhusudhan Chikkature Rajashekar [this message]
2007-11-08 12:29 ` HDQ/1-wire module Nishanth Menon
-- strict thread matches above, loose matches on Subject: below --
2007-12-10 10:11 Madhusudhan Chikkature Rajashekar
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='005a01c8211a$1a143f60$918818ac@ent.ti.com' \
--to=madhu.cr@ti.com \
--cc=linux-omap-open-source@linux.omap.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