blaze_tablet: fix fastboot assumption on relative directory

Rather than use a relative directory, use Android build variables
to pick up the fastboot binary location and location of the AFS
images.

Also pick up on whether we're in a Android FS and assume
that we're in a daily build tar ball and use the current directory
as the location for fastboot and the location of the AFS images.

Change-Id: I8b5a4d528d7b1394f77aea3415db1d5cc22602cb
Signed-off-by: Tony Lofthouse <a0741364@ti.com>
blaze_tablet: enable wifi direct

Enable wifi direct by copying android.hardware.wifi.direct.xml file to target

Change-Id: I1efed6c870adfdd25bf6adccbc39a68d73e7b604
Signed-off-by: Vishal Mahaveer <vishalm@ti.com>
blaze_tablet: reduce wlan logging

Debug logs can be turned on when needed via
echo DEBUG_LEVEL_MASK > /sys/module/wl12xx/parameters/debug_level

Change-Id: I1d771d1fdb8b5d9f0ec3d5a90a2dc5f0fba92f6b
Signed-off-by: Vishal Mahaveer <vishalm@ti.com>
Blaze Tablet: Enable S3D feature

Enable OMAP_ENHANCEMENT_S3D flag and also
include s3d-products.mk in build

Change-Id: I2fc843aa1e36c1551dea1790e376ba3d5be3fd07
Signed-off-by: Devaraj Rangasamy <dev@ti.com>
Merge "blaze_tablet: fix fastboot assumption on relative directory" into jb-release
Merge "Blaze Tablet: Enable S3D feature" into jb-release
blaze_tablet: switch to TI wpa_supplicant

Update WPA_SUPPLICANT_VERSION to point to TI wpa_supplicant tree.
Also TI tree does not need private libraries.

If we want to switch back to Google wpa_supplicant, then we need
to define BOARD_WPA_SUPPLICANT_PRIVATE_LIB and BOARD_HOSTAPD_PRIVATE_LIB

Change-Id: Id5c343d503d1cd9cffff7a38632ddc295af1c583
Signed-off-by: Vishal Mahaveer <vishalm@ti.com>
Merge "blaze_tablet: reduce wlan logging" into jb-release
Merge "blaze_tablet: switch to TI wpa_supplicant" into jb-release
blaze_tablet: lights: avoid double setting same value

Avoid setting same value of brightness twice in a row.
This is a T2 specific issue. If we set brightness to 0 twice in a row
then LCD is disable too. Brightness animation that comes from userspace
use zero value as end of fade animation as well as start value of rising
up one. So actually rasing up animation disable LCD and then increase
brightness of LED. Fix this.

Change-Id: Id47e6d8b1eb4f416ea430e12b1eec30fe3c1bef2
Signed-off-by: Andrii Beregovenko <a.beregovenko@ti.com>
Fix failures in android.app.cts.SystemFeaturesTest

The following tests of android.app.cts.SystemFeaturesTest
are passed successfully after applying this change:
   * testLiveWallpaperFeature
   * testScreenFeatures
   * testSensorFeatures
   * testTelephonyFeatures
   * testUsbAccessory

Change-Id: Ib53ecda7c188dad95261783f064e31e3a2f673be
Signed-off-by: Yuriy Zabroda <yuriy.zabroda@ti.com>
blaze_tablet: add eng build to lunch menu

Change-Id: Ib1c460ad5eb70c8e72426a1632245ce32fbf0772
Signed-off-by: Tony Lofthouse <a0741364@ti.com>
Merge "blaze_tablet: lights: avoid double setting same value" into jb-release
Merge "blaze_tablet: add eng build to lunch menu" into jb-release
PowerHAL: Rename functions and variables to blaze_tablet

Blaze Tablet PowerHAL is copied from Tuna's PowerHAL
with the Tuna's functions and variables names.

The patch basically does s/tuna/blaze_tablet/
Also it replaces a few tab indentations by spaces.

Change-Id: I23ea42621d704c4557c1bc5e12294b129204d19c
Signed-off-by: Taras Kondratiuk <taras@ti.com>
PowerHAL: Change obsolete designated initializers syntax

Designated initializers syntax which is used to initialize
HAL_MODULE_INFO_SYM is obsolete since GCC 2.5:
http://gcc.gnu.org/onlinedocs/gcc/Designated-Inits.html

This patch changes syntax to usual one.

Change-Id: Idcf4175148bd4e3f32fe75c5488e64b3880f832e
Signed-off-by: Taras Kondratiuk <taras@ti.com>
PowerHAL: Define constants for CPUfreq paths

Same CPUfreq paths are used many times in the code.
This patch defines constants for them.

Change-Id: I5f5610813c5032254313209dd4d382535690556f
Signed-off-by: Taras Kondratiuk <taras@ti.com>
PowerHAL: Check that PowerHAL is successfully initialized

It doesn't make any sense to do something if PowerHAL
couldn't setup initial parameters successfully.

Change-Id: I5fdf70ddcc88b7ba073189b18e46de2693fa648f
Signed-off-by: Taras Kondratiuk <taras@ti.com>
PowerHAL: Read available scaling frequencies from sysfs

Blaze Tablet board can have any type of OMAP44xx mounted.
Each OMAP has its own set of scaling frequencies,
so this patch read available frequencies from sysfs on init
and store them into freq_list[] for future use.

Change-Id: Iab1936c70ebcd43d7cc3ffd983705295cc2be2dd
Signed-off-by: Taras Kondratiuk <taras@ti.com>
PowerHAL: Use correct scaling frequencies

Currently PowerHAL uses hardcoded frequencies for OMAP4460 1.2GHz.
It doesn't work well, because Blaze Tablet can have any type
of OMAP44xx mounted.

This patch uses correct scaling frequencies stored in freq_list[].

Change-Id: I6883818d6f2d9bb052d7602404d5e323505fffe3
Signed-off-by: Taras Kondratiuk <taras@ti.com>