BAM DMUX driver gives the data to the USB in work context and USB
is once again scheduling work for sending the data to the host.
This change avoid's the double work queue scheduling for the data
received from BAM DMUX, which might reduce the cpu usage and improve
the throughputs.
Change-Id: Ib66bc7f46f9436704e0d28b72771de50462ddf4b
Signed-off-by: Chiranjeevi Velempati <cvelempa@codeaurora.org>
* changes:
Input: atmel_mxt_ts: Add a debugfs attribute to show all objects
board: 8960: Add config data for mXT1386E touch controller
input: atmel_mxt_ts: Add support for object PROCI_SHIELDLESS_T56
input: atmel_mxt_ts: Support runtime selection of config data
-FTM PCM loopback intended for right speaker also
plays on the left speaker.
-The device profile used will enable both left and right
speaker path, use the correct device profile.
CRs-Fixed: 332162
Change-Id: Iead92c01a1c700f6e2f264cf3af4b9dc561e30f6
Signed-off-by: Laxminath Kasam <lkasam@codeaurora.org>
The sysfs attribute show method (mxt_object_show) is limited to show
object information up to (PAGE_SIZE - 1) bytes. We need a way to get
the complete information of all objects. The object information can
be obtained from <debugfs-mount>/atmel_mxt_ts/object.
Change-Id: I92fff75b37ba0cba19b137460c2144fe847c6343
Signed-off-by: Jing Lin <jinglin@codeaurora.org>
When the touch controller firmware for mxt1386E is upgraded from V1.0
to V2.1, the object size for T43 and T56 changes. In order to support
devices with either version of firmware, two sets of config data are
provided. The driver selects the right config data based on firmware
version and other identifiers.
Change-Id: I9d7e536ff3a9239f31115474782ba0bc503e5019
Signed-off-by: Jing Lin <jinglin@codeaurora.org>
The mXT1386E touch controller supports a new signal processing object
PROCI_SHIELDLESS_T56. This object is both readable and writable.
Change-Id: I418df8c3f05dc5265a1e7581d9c7e654a9fd3c4c
Signed-off-by: Jing Lin <jinglin@codeaurora.org>
Add support for dynamic configuration data update if the target can
support more than one Atmel chip. Platform data contains an array of
supported config data along with family ID, variant ID and firmware
version. Driver searches for matching family ID, variant ID and
firmware version, and uses the corresponding config data to program.
Change-Id: I684da4bdef56a3445acab3bb8fe47dd5279bebe5
Signed-off-by: Jing Lin <jinglin@codeaurora.org>
Create a board file for 8064 display. Allocate framebuffer memory and
add board initialization information for msm_fb, mdp, lvds and rotator
devices.
Change-Id: Id2323c169f04f8a2a6d753ccdd9899ed3ecbd533
Signed-off-by: Huaibin Yang <huaibiny@codeaurora.org>
For funcationality of volume up/down and camera
snapshot/focus keys.
Change-Id: I93ce7dbf5c4b1928fd73a0f0061cbfdabd30605f
Signed-off-by: Anirudh Ghayal <aghayal@codeaurora.org>
The 16-bit fractional dividers used for these clocks should have
a clock rate no greater than 300MHz applied to their inputs when
running in low voltage mode. Increase the pre-dividers for rates
that previously violated this rule.
Change-Id: Ia7177c8643f8c8051ec9cef6cedcb2a7051d936c
Signed-off-by: Matt Wagantall <mattw@codeaurora.org>
The memory where the sysfs attribute is stored on
initialization gets overwritten causing invalid length
on the vbatt sysfs reading. Fix it by removing the
dynamic memory allocation for BTM parameters.
Change-Id: If8b88c9460b0018a159688b5ba28798d97e0b0b6
Signed-off-by: Siddartha Mohanadoss <smohanad@codeaurora.org>
The timestamp would be used by applications for AVSYNC purpose.
Change-Id: I416c38e82fbd51b58df119c0122bcd629ccd88fd
Signed-off-by: Asish Bhattacharya <asishb@codeaurora.org>
TSENS temperature is required to be read during early
initialization by kernel thermal module. Move the TSENS
driver from platform device and initialize the TSENS
HW routine during early init.
Change-Id: Ieb929e6767603a584a996c257cadc77532b4e6cb
Signed-off-by: Praveen Chidambaram <pchidamb@codeaurora.org>
Signed-off-by: Siddartha Mohanadoss <smohanad@codeaurora.org>
An invalid value in the kernel address variable causes an
ion unmap error when attempting to clean up after a failure
occurs when importing the ion fd in the function
vidc_insert_addr_table().
When an ion import fd failure occurs, cleanup is not required.
During failure we now go directly to bail out and the cleanup
code is skipped.
CRs-Fixed: 332841
Change-Id: I3aa99a278806b8f8031c1618ab067391909105c7
Signed-off-by: Luis GarciaCalderon <luisgc@codeaurora.org>
The current code assumes that the cool or warm battery temperature
can only be +ve numbers. Remove this restriction by allowing -ve
temperature settings.
Change-Id: I3c54b854a8fdf934efcf1ff21b36c7a0f763692a
CRs-Fixed: 320660
Signed-off-by: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
Currently during boot, and every suspend and resume, we call
regulator_set_optimum_mode on every touchscreen regulator. However,
some regulators don't support this function, and this will cause
set_optimum_mode to print an error when this occurs. Correct this by
checking if it is valid to call set_optimum_mode on a given regulator
before doing so.
Change-Id: I71f0f14b16d9f333bd409d9d5150f11a7ccd8fdf
Signed-off-by: Jeff Ohlstein <johlstei@codeaurora.org>
