From: Cory Maccarrone <darkstar6262@gmail.com>
To: linux-omap@vger.kernel.org
Cc: linwizard-devel@lists.sf.net, Cory Maccarrone <darkstar6262@gmail.com>
Subject: [PATCH] OMAP1: UART / Bluetooth Support
Date: Tue, 1 Jun 2010 15:32:48 -0700 [thread overview]
Message-ID: <1275431571-28547-1-git-send-email-darkstar6262@gmail.com> (raw)
This set of changes is specifically geared towards enabling bluetooth
support on the HTC Herald. To do that, several things were done:
* I added in the necessary clock and mux configuration to enable
both UARTs to operate.
* I modified the omap1 serial code to only initialize two UARTs if
the CPU type is omap7xx. These chips don't have 3 UARTs, and trying
to initialize the third one causes deadlock.
* I created a common bluetooth-handling driver for HTC smartphones
like the herald. This will be used later by other similar boards,
such as the wizard and the opal. The driver itself only implements
an RFKILL switch to enable/disable the GPIO pins that control the
bluetooth on these devices.
* I added the new bluetooth driver and serial port init code to the
herald board.
* Finally, I updated the htcherald_defconfig both to add in bluetooth
support, and to remove old unneeded cruft.
The on-board chip is a TI BRF6150 attached to the first UART. Rather
than write (or port) a driver for this chip, this method was chosen because
bluez supports the chip over a UART with hciattach. So, rather than
implement a full brf6150 driver, I expose and configure the serial
port it's attached to.
Cory Maccarrone (3):
[omap1] omap7xx clocks, mux, serial fixes
[omap1] Bluetooth device code common to HTC smartphones
[htcherald] Add board support for UARTs, bluetooth
arch/arm/configs/htcherald_defconfig | 159 ++++++++-----------------
arch/arm/mach-omap1/Makefile | 2 +-
arch/arm/mach-omap1/board-htcherald.c | 23 ++++
arch/arm/mach-omap1/clock_data.c | 20 +++
arch/arm/mach-omap1/htc-bt.c | 183 +++++++++++++++++++++++++++++
arch/arm/mach-omap1/include/mach/htc-bt.h | 22 ++++
arch/arm/mach-omap1/mux.c | 4 +
arch/arm/mach-omap1/serial.c | 7 +
arch/arm/plat-omap/include/plat/mux.h | 4 +
9 files changed, 315 insertions(+), 109 deletions(-)
create mode 100644 arch/arm/mach-omap1/htc-bt.c
create mode 100644 arch/arm/mach-omap1/include/mach/htc-bt.h
next reply other threads:[~2010-06-01 22:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 22:32 Cory Maccarrone [this message]
2010-06-01 22:32 ` [PATCH] [omap1] omap7xx clocks, mux, serial fixes Cory Maccarrone
2010-07-05 13:22 ` Tony Lindgren
2010-07-08 13:50 ` Tony Lindgren
2010-06-01 22:32 ` [PATCH] [omap1] Bluetooth device code common to HTC smartphones Cory Maccarrone
2010-07-05 13:25 ` Tony Lindgren
2010-06-01 22:32 ` [PATCH] [htcherald] Add board support for UARTs, bluetooth Cory Maccarrone
2010-07-05 13:23 ` Tony Lindgren
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=1275431571-28547-1-git-send-email-darkstar6262@gmail.com \
--to=darkstar6262@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=linwizard-devel@lists.sf.net \
/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;
as well as URLs for NNTP newsgroup(s).