linux-toradex.git/drivers/mfd, branch 3.0-pcl052-ts1.2 Linux kernel for Apalis and Colibri modules ENGR00175219-3 wm8958: add audio codec support 2012-02-28T06:51:40+00:00 Gary Zhang b13634@freescale.com 2012-02-28T06:51:40+00:00 abe61794752a36daafe9dd3839f1e3f445470b86 add wm8958 audio codec support Signed-off-by: Gary Zhang <b13634@freescale.com> 
add wm8958 audio codec support

Signed-off-by: Gary Zhang <b13634@freescale.com>
ENGR00173964 make hdmi audio init dependent on hdmi video init 2012-02-17T19:45:10+00:00 Alan Tull r80115@freescale.com 2012-02-17T19:34:53+00:00 6b063b2e6f2b5a258f2b3bcc92f81810af77a825 Don't show hdmi as an audio playback device if hdmi isn't configured on the command line. Signed-off-by: Alan Tull <r80115@freescale.com> 
Don't show hdmi as an audio playback device if hdmi isn't
configured on the command line.

Signed-off-by: Alan Tull <r80115@freescale.com>
ENGR00172342-2 EDID parse audio data blocks 2012-02-08T22:57:31+00:00 Alan Tull r80115@freescale.com 2012-02-08T22:40:31+00:00 4aa05d7e99875b882295baebdc6669e581b36e9f Add functionality to parse Audio Data Blocks from EDID data to find out what modes of LPCM are suppored by the HDMI sink device. The parsed settings are saved in the hdmi mfd. The HDMI audio driver will check the settings when the audio stream is opened and will then apply appropriate constraints. If we are unable to read from the EDID, then we default to supporting Basic Audio as defined by the HDMI specification (stereo, 16 bit, 32KHz, 44.1KHz, 48KHz PCM). Signed-off-by: Alan Tull <r80115@freescale.com> 
Add functionality to parse Audio Data Blocks from EDID data to
find out what modes of LPCM are suppored by the HDMI sink device.

The parsed settings are saved in the hdmi mfd.  The HDMI audio driver
will check the settings when the audio stream is opened and will
then apply appropriate constraints.

If we are unable to read from the EDID, then we default to supporting
Basic Audio as defined by the HDMI specification (stereo, 16 bit,
32KHz, 44.1KHz, 48KHz PCM).

Signed-off-by: Alan Tull <r80115@freescale.com>
ENGR00172752-2 Remove usless code in pfuze100 regulator driver 2012-01-25T15:01:36+00:00 Nancy Chen Nancy.Chen@freescale.com 2012-01-25T15:01:36+00:00 6d6f61d40b4d0e4fc23682bad53e43ae4d397b15 Remove usless code in pfuze100 regulator driver Signed-off-by: Robin Gong <b38343@freescale.com> Signed-off-by: Nancy Chen <Nancy.Chen@freescale.com> 
Remove usless code in pfuze100 regulator driver

Signed-off-by: Robin Gong <b38343@freescale.com>
Signed-off-by: Nancy Chen <Nancy.Chen@freescale.com>
ENGR00172374-2: pfuze: use pdata_size from mfd_cell struct 2012-01-19T07:26:49+00:00 Jason Liu r64343@freescale.com 2012-01-19T05:52:13+00:00 5aa089288a7cc7c3e48c39f4527d74badad80da1 fix the building errors when upgrade to v3.0 we use data_size from mfd_cell struct on 2.6.38, but after that there are some changes for this field of mfd_cell struct, see: commit 40e03f571b2e63827f2afb90ea9aa459612c29e3 Author: Andres Salomon <dilinger@queued.net> Date: Thu Feb 17 19:07:24 2011 -0800 mfd: Drop data_size from mfd_cell struct Now that there are no more users of this, drop it. Signed-off-by: Andres Salomon <dilinger@queued.net> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> and this: commit eb8956074e7652e802be5f078080c704c2c87104 Author: Samuel Ortiz <sameo@linux.intel.com> Date: Wed Apr 6 16:52:52 2011 +0200 mfd: Add platform data pointer back Now that we have a way to pass MFD cells down to the sub drivers, we can gradually get rid of mfd_data by putting the platform pointer back in place. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> But the above commit also change the name from data_size to pdata_size, This patch just give one fix for the pfuze driver to use pdata_size field. Signed-off-by: Jason Liu <r64343@freescale.com> 
fix the building errors when upgrade to v3.0

we use data_size from mfd_cell struct on 2.6.38, but after that
there are some changes for this field of mfd_cell struct, see:

commit 40e03f571b2e63827f2afb90ea9aa459612c29e3
Author: Andres Salomon <dilinger@queued.net>
Date:   Thu Feb 17 19:07:24 2011 -0800

    mfd: Drop data_size from mfd_cell struct

    Now that there are no more users of this, drop it.

    Signed-off-by: Andres Salomon <dilinger@queued.net>
    Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>

and this:

commit eb8956074e7652e802be5f078080c704c2c87104
Author: Samuel Ortiz <sameo@linux.intel.com>
Date:   Wed Apr 6 16:52:52 2011 +0200

    mfd: Add platform data pointer back

    Now that we have a way to pass MFD cells down to the sub drivers,
    we can gradually get rid of mfd_data by putting the platform pointer
    back in place.

    Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>

But the above commit also change the name from data_size to pdata_size,
This patch just give one fix for the pfuze driver to use pdata_size field.

Signed-off-by: Jason Liu <r64343@freescale.com>
ENGR00171001-2 MX6Q PFUZE100: fix build warnings 2012-01-09T13:13:18+00:00 Robin Gong B38343@freescale.com 2011-12-28T03:43:08+00:00 521400e4b1b6adb52259345c9a35facaea6911c6 fix build warnings on pfuze driver: arch/arm/mach-mx6/mx6q_sabreauto_pmic_pfuze100.c:388: warning: initialization from incompatible pointer type drivers/mfd/pfuze-core.c:523: warning: initialization from incompatible pointer type drivers/mfd/pfuze-core.c:412: warning: 'pfuze_add_subdevice' defined but not used Signed-off-by: Robin Gong <B38343@freescale.com> 
fix build warnings on pfuze driver:

arch/arm/mach-mx6/mx6q_sabreauto_pmic_pfuze100.c:388:
  warning: initialization from incompatible pointer type
drivers/mfd/pfuze-core.c:523:
  warning: initialization from incompatible pointer type
drivers/mfd/pfuze-core.c:412:
  warning: 'pfuze_add_subdevice' defined but not used

Signed-off-by: Robin Gong <B38343@freescale.com>
ENGR00170255-2 MX6Q PFUZE100: add pfuze100 driver 2012-01-09T13:12:07+00:00 Robin Gong B38343@freescale.com 2011-12-19T10:04:47+00:00 9b1c100011041c9d3889334a5c339cdb7bd0fb3c add pfuze core driver for mx6 Signed-off-by: Robin Gong <B38343@freescale.com> 
add pfuze core  driver for mx6
Signed-off-by: Robin Gong <B38343@freescale.com>
ENGR00169872-2 rework hdmi initialization and hotplug sequence 2012-01-09T13:11:36+00:00 Alan Tull alan.tull@freescale.com 2011-12-08T19:43:42+00:00 ec1f85521053f7dde403b114d3b57dbd03502612 This commit intends to implement the flowchart and details documented in the HDMI Transmitter Controller User Guide section entitled "Programming Model". Some input is also from the Synopsys API code. The HDMI specification requires HDMI to set itself to VGA DVI mode before reading the EDID. So follow this sequence when HDMI is hotplugged: 1. Hdmi connector is plugged in, HDMI video gets an interrupt. 2. Clear out video mode list. Add only VGA DVI mode to list. 3. Request VGA DVI mode (call fb_set_var()) 4. HDMI video driver will get FB_EVENT_MODE_CHANGE callback and call mxc_hdmi_setup() to set up HDMI. 5. Read the edid and add video modes from edid. Select the video mode that is similar to the command line default. 6. Request VGA DVI mode (call fb_set_var()) 7. HDMI video driver will get FB_EVENT_MODE_CHANGE callback and do mxc_hdmi_setup(). Also included is a workaround for an overflow condition in the HDMI. The frame composer has an arithmetic unit that gets updated every time we write to one of the FC registers. But sometimes, depending on the relation between the tmds and sfr clocks, it may happen that this unit doesn't get updated, even though the registers are holding correct values. The workaround for this is, after completing the controller configuration, to rewrite one of the FC registers (i.e. FC_INVIDCONF) three or four times with the same value, and then follow it up by a SW reset to the TMDS clock domain (MC_SWRSTZ). We clear the overflow condition as described above every time we change video mode. Also an overflow interupt handler will clear the overflow condition if it happens again. This overflow condition is expected (and not a problem) when we are in DVI (non-HDMI) mode, so we do not worry about it in that case. Signed-off-by: Alan Tull <alan.tull@freescale.com> 
This commit intends to implement the flowchart and details
documented in the HDMI Transmitter Controller User Guide
section entitled "Programming Model".

Some input is also from the Synopsys API code.

The HDMI specification requires HDMI to set itself to VGA DVI mode
before reading the EDID.

So follow this sequence when HDMI is hotplugged:
1.  Hdmi connector is plugged in, HDMI video gets an interrupt.
2.  Clear out video mode list.  Add only VGA DVI mode to list.
3.  Request VGA DVI mode (call fb_set_var())
4.  HDMI video driver will get FB_EVENT_MODE_CHANGE callback and
    call mxc_hdmi_setup() to set up HDMI.
5.  Read the edid and add video modes from edid.  Select the video
    mode that is similar to the command line default.
6.  Request VGA DVI mode (call fb_set_var())
7.  HDMI video driver will get FB_EVENT_MODE_CHANGE callback and
    do mxc_hdmi_setup().

Also included is a workaround for an overflow condition in the HDMI.

The frame composer has an arithmetic unit that gets updated every time
we write to one of the FC registers. But sometimes, depending on the
relation between the tmds and sfr clocks, it may happen that this unit
doesn't get updated, even though the registers are holding correct
values. The workaround for this is, after completing the controller
configuration, to rewrite one of the FC registers (i.e. FC_INVIDCONF)
three or four times with the same value, and then follow it up by a SW
reset to the TMDS clock domain (MC_SWRSTZ).

We clear the overflow condition as described above every time we
change video mode.  Also an overflow interupt handler will clear the
overflow condition if it happens again.  This overflow condition is
expected (and not a problem) when we are in DVI (non-HDMI) mode, so
we do not worry about it in that case.

Signed-off-by: Alan Tull <alan.tull@freescale.com>
ENGR00143921-1 - EPDC/MAX17135: Add controls for V3P3 regulator 2012-01-09T13:06:15+00:00 Danny Nold dannynold@freescale.com 2011-11-03T18:05:36+00:00 2e5731626d19f95480ad0a368fbd68d2b3f3ebca - Added V3P3 regulator to max17135 - Added calls to enable/disable V3P3 regulator from EPDC driver - Improved Kconfig detail for max17135 MFD and HWMON entries Signed-off-by: Danny Nold <dannynold@freescale.com> 
- Added V3P3 regulator to max17135
- Added calls to enable/disable V3P3 regulator from EPDC driver
- Improved Kconfig detail for max17135 MFD and HWMON entries

Signed-off-by: Danny Nold <dannynold@freescale.com>
ENGR00160860-2 hdmi audio driver 2012-01-09T13:03:17+00:00 Alan Tull alan.tull@freescale.com 2011-10-25T20:41:55+00:00 809c22138d11d04398c3a34887828217d0495791 Audio driver for i.Mx built-in HDMI Transmitter. * Uses HDMI Transmitter's built-in DMA. * Adds IEC958-style digital audio header info to the raw audio. * Gets pixel clock from the IPU driver and calculates clock regenerator values (cts and N). * Move ipu_id, and disp_id from the HDMI's platform data to the HDMI mfd's platform data. Saves them in the hdmi mfd. * Add mfd functionality to update the clock regenerator values when the hdmi changes the pixel clock rate or when requested from the audio driver with a new audio sample rate. Signed-off-by: Alan Tull <alan.tull@freescale.com> 
Audio driver for i.Mx built-in HDMI Transmitter.

* Uses HDMI Transmitter's built-in DMA.
* Adds IEC958-style digital audio header info to the raw audio.
* Gets pixel clock from the IPU driver and calculates clock
  regenerator values (cts and N).
* Move ipu_id, and disp_id from the HDMI's platform data to the
  HDMI mfd's platform data. Saves them in the hdmi mfd.
* Add mfd functionality to update the clock regenerator values
  when the hdmi changes the pixel clock rate or when requested
  from the audio driver with a new audio sample rate.

Signed-off-by: Alan Tull <alan.tull@freescale.com>