From: "Raphaël Assénat" <raph@8d.com>
To: linux-omap@vger.kernel.org
Subject: [RFC PATCH 0/2] omap-serial: A way to implement modem lines through GPIO
Date: Thu, 11 Aug 2011 15:46:53 -0400 [thread overview]
Message-ID: <4E4431AD.4070305@8d.com> (raw)
Hello,
At least in the am3505/3517 CPUs, the built-in uarts only expose the
RX/TX/RTS/CTS signals. Other signals such as DTR/DSR/RI and DCD,
while very useful when controlling a modem, are not available.
My design has the above mentioned extra signals wired to GPIOs.
Controlling them through sysfs is possible, but not convenient as I
needed the standard serial port ioctls to work.
There did not seem to be anything in place to do this so I've come up
with the following two patches which I am using for now.
What do you think? Is there a simpler, more obvious solution?
Did anyone attempt doing something to attain a similar goal in the past?
Best regards,
Raphaël Assénat
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" 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-08-11 19:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E4431AD.4070305@8d.com \
--to=raph@8d.com \
--cc=linux-omap@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox