| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
WARNING: NOT FOR OMAP4430!
OMAP4460 apparently uses PL310 r3p1-50rel0, which according to the existing config docs and this link don't effect it: http://www.spinics.net/lists/arm-kernel/msg343612.html
The newly added ones do effect it.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
security/smc/tf_device.c:174: missing braces around initializer
security/smc/tf_device.c:174: (near initialization for 'g_tf_dev.kobj')
Change-Id: Ia8b3b9420ab3b860900d1db9fe0ed925b96fc200
Signed-off-by: Bryan Buckley <bryan.buckley@ti.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added get_resolution and get_fb_resolution function to HDMI
driver so that we can configure defaults via board files when
HDMI is default panel.
Change-Id: I36cafb4b0bd42c150c1c1a03be4607edec31b4db
Co-Author-by: Victor Kleinik <x0150886@ti.com>
Co-Author-by: Artem Rudenko <artemrudenko@ti.com>
Signed-off-by: Dandawate Saket <dsaket@ti.com>
Signed-off-by: Muralidhar Dixit <murali.dixit@ti.com>
|
|
|
|
|
|
|
|
|
| |
Issue with entering blaze to suspend state fixed.
Also fixed error during hdmi driver resume when actual
hdmi device was not connected.
Change-Id: Iffb151982f020afb40dc2b39b35aa80a03091b32
Signed-off-by: Andrii Guriev <x0160204@ti.com>
|
|
|
|
|
|
|
|
| |
Change-Id: I7564fb0c3eb617c1beba2dc0162db25b5799a8e5
Signed-off-by: Max Herman <mherman@fsisys.com>
Conflicts:
drivers/power/twl6030_bci_battery.c
|
|
|
|
|
|
|
|
|
|
|
| |
TWL6032 has 12-bit ADC, TWL6030 has 10-bit ADC, battery temperature
table is calculated for the TWL6030. So battery temperature measured
correctly only for OMAP4430 and OMAP4460. Patch rejects two lower
bits of ADC channel for TWL6032 and temperature measured correctly
for all OMAP controllers.
Change-Id: I88b6f2e6fbde11fa05642d1772c797b61b2fd1ce
Signed-off-by: Oleksandr Dmytryshyn <oleksandr.dmytryshyn@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Battery driver reads ADC channel 1 to wich NTC resistor
is connected to detect battery temperature.
There is a table that matches ADC value to temperature.
The driver, for looking corresponding temperature uses
ADC value converted to millivolts, instead of ADC value,
which is incorrect.
Use ADC value for temperature conversion.
Change-Id: I25812a4f3d94ce971475546145803513e346dd9a
Signed-off-by: Oleksandr Kozaruk <oleksandr.kozaruk@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously temperature of the battery was refreshed only if adc ch1 value
was in range from 100 to 950. Now the temperature of the battery measured
correctly. If the temperature is less then -2 degrees Celsius then
-2 degrees Celsius returned and if the temperature is more then +62 degrees
Celsius then +62 degrees Celsius returned.
Change-Id: I8f91b88e76fc3c00e0d7a22267de16f096584e13
Signed-off-by: Oleksandr Dmytryshyn <oleksandr.dmytryshyn@ti.com>
Conflicts:
drivers/power/twl6030_bci_battery.c
|
|
|
|
|
|
|
|
|
| |
If platform data does not pass down the nominal battery capacity,
then assume a sane default value.
Change-Id: Icba698fb0d2f14cc778740734ed8f2c573e67f0d
Signed-off-by: Sivakumar Pothireddy <sivakumar.pothireddy@ti.com>
Signed-off-by: Anand Gadiyar <gadiyar@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Pass the nominal battery capacity from the board file instead of
hardcoding it in the driver.
TODO: This needs to be done for the blaze as well, although it's
rarely run off the battery
Change-Id: I15cba65f062c70f3b1e26f3c03db59e3af0d6ea9
Signed-off-by: Sivakumar Pothireddy <sivakumar.pothireddy@ti.com>
Signed-off-by: Anand Gadiyar <gadiyar@ti.com>
Conflicts:
arch/arm/mach-omap2/board-44xx-power.c
|
|
|
|
|
|
|
|
|
|
|
| |
We now update capacity estimates using the gas gauge. No need to
schedule voltage-based estimates except when voltage is critically low.
(This reconciliation based on voltages will be done in a later patch).
So remove this code.
Change-Id: I46706c954e32667a84a4e64c9a0831a706755da8
Signed-off-by: Sivakumar Pothireddy <sivakumar.pothireddy@ti.com>
Signed-off-by: Anand Gadiyar <gadiyar@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use the gas gauge in twl6030 to estimate the remaining battery
capacity.
At bootup, we use an estimate of initial capacity using the measured
battery voltage at bootup. From that point on, all future battery
capacity estimations are done by using the gas gauge to measure
all addition/removal of charge from the battery.
Clamp battery value to 99% if the measured value exceeds 99%.
A later patch will add the code to update the initial estimate
once the battery is fully charged.
TODO: Minimum safe battery voltage reporting needs to be worked on
Change-Id: Iab157b559f9de432a93664e8d78c003af3c75b67
Signed-off-by: Sivakumar Pothireddy <sivakumar.pothireddy@ti.com>
Signed-off-by: Anand Gadiyar <gadiyar@ti.com>
|
|
|
|
|
|
|
|
|
| |
Otherwise previous register values (from bootloader, or warm reboot)
will distort our calculations.
Change-Id: I302eb3f05cacdc9136c937556dd5a9d5d8baf4d4
Signed-off-by: Sivakumar Pothireddy <sivakumar.pothireddy@ti.com>
Signed-off-by: Anand Gadiyar <gadiyar@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a lookup table for estimating battery capacity at bootup
using the battery voltage measrued at that time.
The table was constructed using actual measured values for Blaze
Tablets. The values don't correspond to the arbitrary values currently
used in the driver.
This table is something that a board file should pass to the
driver. This will be introduced in a later patch - for now, we
keep the values in the driver just like the current design.
Change-Id: I78b35b68c7a41b67d67925dae8015405efb44b0d
Signed-off-by: Sivakumar Pothireddy <sivakumar.pothireddy@ti.com>
Signed-off-by: Anand Gadiyar <gadiyar@ti.com>
|
|
|
|
|
|
|
|
|
| |
We need the gas gauge to continue measuring power drain in suspend.
Keep it always enabled.
Change-Id: I5b6dd4d8f63e3269dacf8d8dfb814670bfa8937a
Signed-off-by: Sivakumar Pothireddy <sivakumar.pothireddy@ti.com>
Signed-off-by: Anand Gadiyar <gadiyar@ti.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Capacity could be detected when it is not charging.
If charge status set to POWER_SUPPLY_STATUS_NOT_CHARGING
capacity detection path is omitted.
Add this state to let capacity detection happen.
Change-Id: I34a8295470457423d25cc2ec42e2498682339dcc
Signed-off-by: Oleksandr Kozaruk <oleksandr.kozaruk@ti.com>
|
|
|
|
|
|
|
|
|
| |
In latest TRMs for OMAP4 family LPDDR recommended
setting have been changed. This patch does
corresponding changes in the code.
Change-Id: Ibd81b8196db74df5a7c3e29788c72a7b3628a22c
Signed-off-by: Ruslan Bilovol <ruslan.bilovol@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A ZQ calibration long command is issued every time on exit
from active power-down and precharge power-down modes
when EMIF is configured to use Power-down mode
(EMIF_PWR_MGMT_CTRL.REG_LP_MODE=0x4).
Due to very short periods of power-down cycles, ZQ calibration
overhead creates bandwidth issues and increases overall system
power consumption.
As result, the guideline is to not allow Power-down mode and,
therefore, to not have set the
EMIF_PWR_MGMT_CTRL[10:8] REG_LP_MODE bit field to 0x4.
TI Errata i743; IMPACTED: OMAP4430/60 all revisions
Change-Id: Ib82f28e6e0c6c046ea277b90a78dc82c1ee82417
Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
Signed-off-by: Vitaly Chernooky <vitaly.chernooky@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Removed unused fields of emif_regs structure and
functions that initialize or change them.
Also changed few names of emif_regs members
to match register names.
This made the code easier to understand and read
as well as made it a little bit faster
Change-Id: I0485a01b7f03e922b5a2e69bfb03c2ed941fcf3b
Signed-off-by: Ruslan Bilovol <ruslan.bilovol@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The value from CM_SHADOW_FREQ_CONFIG2 can't be applied because
GPMC is always active and can't be entered in idle state.
The GPMC is always active because on OMAP4, CPU accesses on
unmapped addresses are redirected to GPMC by L3 interconnect.
CPU is speculative nature and such accesses are possible which
can lead to indirect access to GPMC and if it's clock is
not running, it can result in hang/abort on the platform.
See path d60565948468b for more information.
Change-Id: Ia62d8bf8c59ac3a06445b6f5f9e08ad0c9369c5b
Signed-off-by: Eugen Mandrenko <ievgen.mandrenko@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Errata ProDB00121179 says voltage overshoot may occur if
switch from DVS to non-DVS ranges on TWL6032.
- DVS range VSEL codes 0x01-0x39
- non-DVS range VSEL codes 0x3A-0x3E
Max_volt settings (1.418V) were converted to VSEL=0x3A.
This VSEL code is in non-DVS range while all other codes
are in DVS range. Thus using this code leads to voltage
overshoot due to errata.
Now max_volt 1.418V is converted to code VSEL=0x39
which corresponds to 1.417960V and is in the safe range.
The voltages higher than 1.418V aren't used for both 6030 and 6032.
Thus replacing VSEL code 0x3A by 0x39 does not impact performance.
If used SMPS_OFFSET=0 (default only for twl6030 es1.0 and
is not used on twl6032) the max voltage of 1.35V is
recalculated to VSEL=0x3A and is not affected by the patch.
Change-Id: I5e992be09899f520c1635fe3c268cbfdedc4caf4
Signed-off-by: Oleg_Kosheliev <oleg.kosheliev@ti.com>
|
|
|
|
|
|
|
|
|
|
|
| |
In order to disable the in-kernel version of the DDK
and be able to use it as a module we need to remove
this dependency.
No harm to DSSCOMP, it will just wait until a DDK
is installed to execute.
Change-Id: Ie1436a45fb20044d0121eb196c6155b50baa7915
Signed-off-by: Rogelio Garcia <rgarcia@ti.com>
|
|
|
|
|
|
|
|
|
| |
Add the panel file the tablet and the tablet2 displays.
Adding panel-tc35865
Change-Id: Ibaff9bdeae850d7c370e06c778d9dad3a1e05d32
Signed-off-by: Dan Murphy <dmurphy@ti.com>
|
|
|
|
|
| |
Change-Id: I68624e1604a30c854843f3a2206e70a516cc57a0
Signed-off-by: Craig Stout <craig.stout@ti.com>
|
|
|
|
|
| |
Change-Id: I0bbe26fd4dba445bd9b9c5135fe99bc8099626ff
Signed-off-by: Alexei Shlychkov <x0177296@ti.com>
|
|
|
|
|
| |
Change-Id: I137acb5efc00bc3ea2dbb9ad596234061cf78257
Signed-off-by: Alexei Shlychkov <x0177296@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use the destination format (RGB) for the temporary buffer
if destination angle is not 0 degree due to a hardware
limitation for 4:2:2 rotated destination.
Performance is optimized for temporary buffer by setting
proper buffer geomerty.
Change-Id: Ie53da18fe854adeaaf3d568605bb8630288aee5d
Signed-off-by: Alexei Shlychkov <x0177296@ti.com>
|
|
|
|
|
|
|
|
| |
This is primarily to fix YUV plane location
calculations, but RGB formats are affected as well.
Change-Id: I2877c3c0ec35c03425903c2df9de08ba201cf091
Signed-off-by: Alexei Shlychkov <x0177296@ti.com>
|
|
|
|
|
|
|
|
|
| |
Share the same setup routines for blitting and
scaling. Use old-style registers for source 0
in blit setup due to a hardware problem.
Change-Id: Ic9ed5c95d37833521f2eda21d818f8a8696bcd4c
Signed-off-by: Alexei Shlychkov <x0177296@ti.com>
|
|
|
|
|
|
|
| |
Packed YUV source rotation is enabled.
Change-Id: I0beaae011e576fcd8dd78e800cc5acde7de9311f
Signed-off-by: Alexei Shlychkov <x0177296@ti.com>
|
|
|
|
|
|
|
| |
Also fixed compiler warnings.
Change-Id: I254abc86fd08c1be1d2f904f0c10018bcbc5a8c6
Signed-off-by: Alexei Shlychkov <x0177296@ti.com>
|
|
|
|
|
| |
Change-Id: Ib08231c481533e349affd792ef944386dbcc0593
Signed-off-by: Alexei Shlychkov <x0177296@ti.com>
|
|
|
|
|
|
|
| |
Use GFP_ATOMIC instead of GFP_KERNEL to avoid potential blocking.
Change-Id: Id405a2aa609560b849adf0e096970d0251cfd140
Signed-off-by: Oleg Matcovschi <oleg.matcovschi@ti.com>
|
|
|
|
|
| |
Change-Id: I09b56c66bd594305557b226fb30e9d945657a799
Signed-off-by: Craig Stout <craig.stout@ti.com>
|
|
|
|
|
|
|
| |
Also debug logging improved.
Change-Id: I0fd42fc417080d163f55f1c58e12dd5713f3d8be
Signed-off-by: Alexei Shlychkov <x0177296@ti.com>
|
|
|
|
|
|
|
|
|
| |
If the thread has no work scheduled and is
kicked off by a soft trigger, it would start
looping until the next work gets scheduled.
Change-Id: Ia7256622c61f45c9483c722dd968a1dfec752f89
Signed-off-by: Alexei Shlychkov <x0177296@ti.com>
|
|
|
|
|
|
|
|
| |
An additional geometry check to prevent the user
from supplying invalid geometry and causing L3 errors.
Change-Id: I5c22dbc36ca1e4a64fa240aff0f052673b5a4116
Signed-off-by: Alexei Shlychkov <x0177296@ti.com>
|
|
|
|
|
|
|
|
|
| |
Added special handling for rotation.
Added bandwidth optimizations.
Bug fixes.
Change-Id: I5f188b46355b51444e18a29ebcf0f62a557924d0
Signed-off-by: Alexei Shlychkov <x0177296@ti.com>
|
|
|
|
|
| |
Change-Id: I2041fdc3092ab04337c24f6a70ed3711da96894a
Signed-off-by: Alexei Shlychkov <x0177296@ti.com>
|
|
|
|
|
| |
Change-Id: I57a8a6f49fdf6bbfa150c25c78057fec5f7892d0
Signed-off-by: Alexei Shlychkov <x0177296@ti.com>
|
|
|
|
|
|
|
|
|
|
| |
Separated common setup shared between all
operations from parameters that only apply
for bitblt. Scaler will have different setup
for those parameters (for ex. rotation).
Change-Id: Ib85e288dbc59aa5b86b6dc810d3eb8c78471d91d
Signed-off-by: Alexei Shlychkov <x0177296@ti.com>
|
|
|
|
|
| |
Change-Id: I3d19564422501dd76772760e5c2fdb152d031825
Signed-off-by: Alexei Shlychkov <x0177296@ti.com>
|
|
|
|
|
|
|
| |
RGB and YUV formats are now generically supported.
Change-Id: I9911119c6323ac91a63e1fb7d0a3012038985d8e
Signed-off-by: Alexei Shlychkov <x0177296@ti.com>
|
|
|
|
|
|
|
| |
Determines the current speed of GC320 in megahertz.
Change-Id: I0aadf024193d8c1d2aac7ef79604367249939831
Signed-off-by: Alexei Shlychkov <x0177296@ti.com>
|
|
|
|
|
|
|
|
|
| |
90/270 degree rotation is fixed by adjusting the uv plane
address to get the proper uvplane starting address after the
rotation.
Change-Id: I350b83a77bd80efef6d470a30a46386c53628082
Signed-off-by: Jack Yen <jyen@ti.com>
|
|
|
|
|
| |
Change-Id: I7302e6099f6fae8880e6f1406c040bfe56833439
Signed-off-by: Craig Stout <craig.stout@ti.com>
|
|
|
|
|
| |
Change-Id: I0e7172e2ddcf32571d745daed7b4e9e3bad1e0c6
Signed-off-by: Craig Stout <craig.stout@ti.com>
|