Patch from David Brownell and Dmitry Torokhov: convert the ads7846 driver
to use input_allocate_device. Also fixes the bug where the SPI message was
not initialized with spi_message_init().
Signed-off-by: Imre Deak <imre.deak@nokia.com>
Signed-off-by: Juha Yrjl <juha.yrjola@nokia.com>

Signed-off-by: Imre Deak <imre.deak@nokia.com>
Signed-off-by: Juha Yrjl <juha.yrjola@nokia.com>

The DMA register read was done to an incorrent address.
Signed-off-by: Juha Yrjölä <juha.yrjola@nokia.com>

Signed-off-by: Juha Yrjl <juha.yrjola@nokia.com>

Signed-off-by: Juha Yrjl <juha.yrjola@nokia.com>

Signed-off-by: Juha Yrjl <juha.yrjola@nokia.com>

OMAP1 was using STI_DR instead of STI_RX_DR, which was causing problems
in the RX path. OMAP2 has a consolidated XTI_TRACESELECT, the logic for
trace clearing is the logical inverse of the OMAP1 STI_DR, so fix that
while we're at it.
Signed-off-by: Mikko K. Ylinen <mikko.k.ylinen@nokia.com>
Signed-off-by: Paul Mundt <paul.mundt@nokia.com>

Clock framework specifies that the selection of clock should be
done based on the device id for similar clocks. This patch adds
support for MMC clocks. Clock device id handling adapted from
mach-s3c2410/clock.c.

Add error checking to clock functions

In the uWire driver only one of the clock dividers was used to set
the clock to the required frequency. This will add a loop to try all
possible combinations using the other divider as well.
Signed-off-by: Imre Deak <imre.deak@nokia.com>
Signed-off-by: Juha Yrjölä <juha.yrjola@nokia.com>

The RX path maintained the number of received bytes incorrectly causing
the transmission to be aborted.
Signed-off-by: Imre Deak <imre.deak@nokia.com>
Signed-off-by: Juha Yrjölä <juha.yrjola@nokia.com>

- Add api_ck control needed for McBSP initialization.
- Bug fix for process list handling
- Conversion from internal pool allocators to mempool API.
Signed-off-by: Toshihiro Kobayashi <toshihiro.kobayashi@nokia.com>
Signed-off-by: Paul Mundt <paul.mundt@nokia.com>

Signed-off-by: Samuel Ortiz <samuel.ortiz@nokia.com>
Signed-off-by: Juha Yrjl <juha.yrjola@nokia.com>

Some bootloaders have the ability to send information about the
various component versions (e.g. HW revision, bootloader version)
through the ATAG mechanism. This patch implements a procfs entry
for reading such information.
Signed-off-by: Juha Yrjölä <juha.yrjola@nokia.com>

- Reserve the DMA channel at init time to reduce xfer overhead
- PSC values need to be increased in some cases where the driving
  clock runs at a high frequency
- Enable auto idling
Signed-off-by: Juha Yrjölä <juha.yrjola@nokia.com>

- Support for the Philips LPH8923 LCD panel
- Support for the Epson HWA742 LCD controller

- Support for frame buffer located in SRAM and/or SDRAM
- Support for boot loader initialized LCD controller / frame buffer
  content.

- LCD panels will now register a device in the relevant board-* files
  instead of specifying the LCD type as an OMAP_TAG_LCD. The controller
  type is still specified in OMAP_TAG_LCD.
- A new ATAG OMAP_TAG_FBMEM is used to describe the frame buffer memory
  configuration (SRAM and SDRAM regions)

- Changed the OMAP1 LCD controller driver to export its functions
  through the lcd_ctrl object.
- OMAP1 pixel clock divider will now round up in lcdc.c
- Changed the OMAP1 SoSSI driver to export its functions through the
  lcd_ctrl_extif object.
- OMAP1 SoSSI clock calculation goes through all possible clock
  dividers. Rounding of clock tick values now takes places at each
  timing parameter.

- OMAP2 RFBI clock calculation goes through all possible clock
  dividers. Rounding of clock tick values now takes places at each
  timing parameter.
- OMAP2 pixel clock divider will now round up in dispc.c
Signed-off-by: Imre Deak <imre.deak@nokia.com>
Signed-off-by: Juha Yrjl <juha.yrjola@nokia.com>

Presently we have OMAP_TAG_SERIAL_CONSOLE that wraps in to
add_preferred_console() for the serial console, this does the same
thing with OMAP_TAG_STI_CONSOLE so it's selectable who gets tty
control.
Signed-off-by: Paul Mundt <paul.mundt@nokia.com>

This patch adds a Bluetooth HCI driver for the TI BRF6150
chip with Nokia H4 extensions. The chip is e.g. on the Nokia 770.
Signed-off-by: Ville Tervo <ville.tervo@nokia.com>
Signed-off-by: Juha Yrjl <juha.yrjola@nokia.com>

The converted driver originated from David Brownell, with some
modifications by Imre.
Signed-off-by: Imre Deak <imre.deak@nokia.com>
Signed-off-by: Juha Yrjl <juha.yrjola@nokia.com>

Signed-off-by: Juha Yrjl <juha.yrjola@nokia.com>

Signed-off-by: Juha Yrjl <juha.yrjola@nokia.com>

Signed-off-by: Juha Yrjl <juha.yrjola@nokia.com>

Signed-off-by: Juha Yrjl <juha.yrjola@nokia.com>

Signed-off-by: Juha Yrjölä <juha.yrjola@nokia.com>

Avoid other SA_TRIGGER_* flags triggering BUG()

This implements a simple subsystem for the OMAP serial tracing interface,
as found in omap16xx and omap24xx.

There's a few things implemented in this patch:

        - STI console support
        - STI netlink support
        - STI RX FIFO support

In addition to this, we also provide a general tracing framework that can
be used by both the kernel and userspace (and imask control for allowing
DSP-side STI manipulation).

Since the IRQ is multiplexed, drivers register for the bits they're
interested in (the RX FIFO is an example of this).

The netlink interface exists for streaming data bi-directionally. This is
currently done using NETLINK_USERSOCK, which ends up being somewhat
limiting.

All of these things have been tested on both OMAP1 and OMAP2, and it
takes in to account some of the protocol differences.

New way to handle irq trigger mode is to pass it as flag to
request_irq()  instead of using special ARM function
set_irq_mode().

Signed-off-by: Dirk Behme <dirk.behme_at_gmail.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>

The new way to pass level detection is with the SA_TRIGGER_*
flags wit request_irq instead of set_irq_type().

As we may get other flags in the trigger, we must mask the flag
instead of comparing it directly.

Needs to be fixed.

Quick fix to make drivers compile and work again. Needs
to be verified.

Current implementation of omap_i2c_isr doesn't work on OMAP5910 (Too
much work in one IRQ). Interrupt service routine is broken in these
aspects:
* it tries to ack interrupt by writing to read-only status register.
* it doesn't ackowledge interrupt properly by reading interrupt vector
  register.
I'm assuming that driver works correctly on other OMAPs (right? ;-)), so
proposed patch adds interrupt service routine for 15xx cpus and deletes
rev1 stuff from omap_i2c_isr. Tested on OMAP5910 with DS1339 clock on
I2C bus.
Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
Signed-off-by: Tony Lindgren <tony@atomide.com>

omap_i2c_xfer is supposed to return number of messages successfuly
transfered. Remove bogus condition which causes it to fail when
transfering one message.
Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
Signed-off-by: Tony Lindgren <tony@atomide.com>