Age | Commit message (Collapse) | Author |
|
Change-Id: Ic50e6261e34caa3851ef68a6e2a6cbbd600a13d6
Reviewed-on: http://git-master/r/30929
Reviewed-by: Aleksandr Frid <afrid@nvidia.com>
Tested-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
Reviewed-by: Diwakar Tundlam <dtundlam@nvidia.com>
Tested-by: Diwakar Tundlam <dtundlam@nvidia.com>
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
|
|
For different Tegra3 process corners/skus/revisions/boards set nominal
voltages for CPU and core rails as well as adjust maximum clock rates
as follows.
- VDD_CORE rail nominal voltage: default value is indexed by speedo_id
of the chip (speedo_id is determined by chip sku and revision). Minimum
of the default and board specific electrical design voltage is rounded
down against core dvfs voltage ladder. The result is set as nominal
core voltage (edp voltage API is not implemented, yet).
- VDD_CPU rail nominal voltage: default value is indexed by speedo_id
of the chip. If too high, it is lowered to core nominal voltage so that
core_on_cpu dependency is resolved at nominal core level. The result is
compared with voltage required to reach CPU maximum rate as specified
in the dvfs table for the particular process corner. Again, the minimal
level is selected, and finally set as CPU nominal voltage.
After nominal voltages are determined, maximum rate for each dvfs clock
is adjusted accordingly, so that it does not exceed the rate specified
in the respective DVFS table at nominal level.
Change-Id: Ia6c1c5c853f98ab185f42bf1cfd7a1d7d54d10c3
Reviewed-on: http://git-master/r/30928
Reviewed-by: Aleksandr Frid <afrid@nvidia.com>
Tested-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
Reviewed-by: Diwakar Tundlam <dtundlam@nvidia.com>
Tested-by: Diwakar Tundlam <dtundlam@nvidia.com>
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
|
|
after enabling any LDO/SM, there is a specific amount of delay
required before the regulator becomes stable.
Change-Id: I7cce3d8aad8859af0cbda7e114850fc95fe34eea
Reviewed-on: http://git-master/r/30862
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-by: Pritesh Raithatha <praithatha@nvidia.com>
Tested-by: Pritesh Raithatha <praithatha@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Mayuresh Kulkarni <mkulkarni@nvidia.com>
|
|
Enterprise board uses SDMMC3 slot for External SD and SDMMC1 slot
for WiFi.
Bug 822432
Change-Id: Ifa13d69fa65f974c8457b9ffec231579b356a810
Reviewed-on: http://git-master/r/30514
Reviewed-by: Daniel Willemsen <dwillemsen@nvidia.com>
Tested-by: Daniel Willemsen <dwillemsen@nvidia.com>
|
|
Calling device_add causes an inital uevent to be generated.
The power_supply uevent function calls the drivers get_property function,
which causes the driver to update its state, which again
causes the driver to call power_supply_changed().
Since the power_supplys changed_work has not been initialized at this
point the behavior is undefined.This patch fixes the issue by
initializing the power_supplys changed_work prior to adding
the power_supplys device to the device tree.
(cherry picked from commit 97774672573ac4355bd12cf84b202555c1131b69
of http://git.infradead.org/battery-2.6.git/commit/
97774672573ac4355bd12cf84b202555c1131b69)
Change-Id: I7256b91144ce7de93bc63844bfa0b55433a9a7d0
Reviewed-on: http://git-master/r/30484
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-by: Varun Wadekar <vwadekar@nvidia.com>
Tested-by: Syed Rafiuddin <srafiuddin@nvidia.com>
Reviewed-by: Pritesh Raithatha <praithatha@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
Reviewed-by: Mayuresh Kulkarni <mkulkarni@nvidia.com>
|
|
Exposed the baseband i2s port for cardhu.
Added separate audio init function.
Change-Id: I9ff38f101c5540ad6e2365ed93a8c88373164ea3
Reviewed-on: http://git-master/r/30087
Reviewed-by: Vinod Gopalakrishnakurup <vinodg@nvidia.com>
Reviewed-by: Scott Peterson <speterson@nvidia.com>
Tested-by: Vinod Gopalakrishnakurup <vinodg@nvidia.com>
|
|
Creates /d/tracing/events/nvhost. Logs channel opens, closes,
writes and flushes. For writes, logs number, size and address
of cmdbufs and number of relocs.
Change-Id: I5bdadcb40c31e3f057eb8c4579b95e235d860e39
Signed-off-by: Terje Bergstrom <tbergstrom@nvidia.com>
Reviewed-on: http://git-master/r/29770
Reviewed-by: Andrew Howe <ahowe@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
Reviewed-by: Mayuresh Kulkarni <mkulkarni@nvidia.com>
|
|
Following are the changes:
- Added a mechanism to handle synchronization between caller thread
and isr so that isr should not get called when clock is disable or
controller is in reset state.
- Handling tx fifo overflow error.
- Added delay before resetting the controller which is required if
there is any error in previous transaction so proper stop signal
will be generated.
Change-Id: I7ac121e056193cd4601f032cdabab59e7e0946ea
Reviewed-on: http://git-master/r/30457
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-by: Alok Chauhan <alokc@nvidia.com>
Tested-by: Alok Chauhan <alokc@nvidia.com>
Tested-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-by: Danielle Sun <dsun@nvidia.com>
Tested-by: Danielle Sun <dsun@nvidia.com>
Reviewed-by: Bo Yan <byan@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
|
|
|
|
Includes:
1.) Added basic DC sysfs objects.
2.) Sysfs objects and functions for smartdimmer settings.
3.) Register dump access for smartdimmer.
4.) Improvements to the behavior of smartdimmer (now updates
at the end of vblank instead of the beginning).
5.) Rename v_blank_complete to vblank_complete to keep in
same effective style as the rest of the code.
Change-Id: I59addcc479880322d49b24d1206009def3c4b392
Reviewed-on: http://git-master/r/29893
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
Change-Id: Ie46f78c54ea8f7bf04fa33c368123e760c072999
Reviewed-on: http://git-master/r/30751
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
Removing unused variable.
Change-Id: Idf5fd40c7a953505c08872023b3d55296237ec49
Reviewed-on: http://git-master/r/30690
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
Adding the board init and deinint function to power on/off
rails for the sh532u autofocus driver.
This function is passed as platform data to the driver.
bug 802264
Change-Id: Ib7ef55898dce5f6ae458c922e6b5cbce64740cd0
Reviewed-on: http://git-master/r/30171
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
Bug 814805, 767218
Change-Id: I818ebde2f7fd45152d1229ec257aa5f177d5253f
Reviewed-on: http://git-master/r/30108
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
Enable UVC driver to support the UVC usb camera.
Disable usb suspend because if we enable it if fails
to detect the usb camera sometimes.
Bug 801763
Change-Id: I790739362a89ad04dbd356550a11a3920af12fde
Reviewed-on: http://git-master/r/30025
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
Adding the camera autofocus power rail infomration.
Removing non-existant peripheral entry from i2c4 bus.
Adding deselect mux option after each i2c transfer
through mux i2c.
bug 802264
Change-Id: Id87178666e4d8c4c5db3f8be708fc5fc85b3e2e4
Reviewed-on: http://git-master/r/29998
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
Removing the HDMI pinmux from pingroups LCD_SCK and LCD_PWR0
as per TRM document.
Change-Id: I85e3a5fb3af1cecbe6eb83d47e811362cd4ee629
Reviewed-on: http://git-master/r/29970
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
cause data corruption.
PL310 implements the Clean & Invalidate by Way L2 cache maintenance operation
(offset 0x7FC). This operation runs in background so that PL310 can handle
normal accesses while it is in progress. Under very rare circumstances,
due to this erratum, write data can be lost when PL310 treats a cacheable
write transaction during a Clean & Invalidate by Way operation.
This fix is to replace the background Clean & Invalby Way operation
by a software loop on all sets/ways. This works for r2p0 and r3p0 as well.
Change-Id: I45e841d8049a18f2dd36ce13e8ef15322f14c5d5
Reviewed-on: http://git-master/r/29690
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
Enabled TPS6591x PMU RTC & disabled Tegra internal RTC
Change-Id: I480ad99646b8eb57928a0b9c4d17fa0d6ed81d40
Reviewed-on: http://git-master/r/29636
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
At the time of reboot, all rails need to be set to nominal to ensure
the success of subsequent boot.
bug 821969 bug 797082
Change-Id: Iee635c222619dfcb3e98f13e665ea2bd04e94245
Reviewed-on: http://git-master/r/30086
Reviewed-by: Bo Yan <byan@nvidia.com>
Tested-by: Bo Yan <byan@nvidia.com>
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
On ventana, pca9546 is used as a mux for 0v2710/ov5650 camera
sensors. With UJA0H14 version of ov5650 sensor, it is observed
that pca9546 driver incorrectly caches last channel when VDDIO_CAM
is toggled while enabling/disabling tegra camera. Deselect i2c
mux channel on exit so that i2c mux is correctly configured with
new mux channel.
BUG 812134
(cherry picked from commit 2d62e589c0bd933db846d4b8f9fe4f2116bef8ad)
Reviewed-on: http://git-master/r/29811
(cherry picked from commit c53b7eb26bee96fd7927e94848055af94baa831b)
Change-Id: Ic41a952d05b610e569e37802cf05552af9d93e13
Reviewed-on: http://git-master/r/30975
Reviewed-by: Pritesh Raithatha <praithatha@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Selecting the core EDP voltage and panel type from the kernel commands.
The bootloader pass this information through kernel command.
Board will select the default configuration if there is no command option
for these parameters.
bug 822053
Change-Id: Id7909d70b599c4a313d60d3ba2a9cf5b9eb7f2c3
Reviewed-on: http://git-master/r/30853
Tested-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Jonathan Mayo <jmayo@nvidia.com>
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
|
|
Add RAW-IP network driver for use with modems such as XMM6260.
Change-Id: Ifc863c50fd918eccec63895c82f10fc32f6b8b6f
Reviewed-on: http://git-master/r/30640
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Prevent CDC-ACM driver from creating tty devices for each USB
interface on supported modem. Only create one tty device, leaving
other USB interfaces available for other uses (such as RAW-IP).
Change-Id: I457659783c61f3f76e8026683dbbf2ddb3098ba2
Reviewed-on: http://git-master/r/30599
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Change-Id: I7b267a813a2db39704ea8632d3b9c93df6a51379
Reviewed-on: http://git-master/r/30558
Reviewed-by: Vinod Gopalakrishnakurup <vinodg@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
Tested-by: Scott Williams <scwilliams@nvidia.com>
|
|
Updated Tegra3 core DVFS tables with characterization results.
Changed default maximum limits for: sdmmc2/4 to 104MHz, vi to
300MHz, and hdmi to 148.5MHz.
Change-Id: Icd07d933d7d2f8c77d6e023b19b62e7ee3fc775a
Reviewed-on: http://git-master/r/30551
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
Reviewed-by: Aleksandr Frid <afrid@nvidia.com>
Tested-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Diwakar Tundlam <dtundlam@nvidia.com>
Tested-by: Diwakar Tundlam <dtundlam@nvidia.com>
|
|
The get_voltage should return voltage in unit of microvolts.
bug 823828
Change-Id: I41d168f2845947cab0b076b0d3f0b70305af240b
Reviewed-on: http://git-master/r/30488
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
Tested-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-by: Peter De Schrijver <pdeschrijver@nvidia.com>
Tested-by: Peter De Schrijver <pdeschrijver@nvidia.com>
Reviewed-by: Diwakar Tundlam <dtundlam@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
|
|
some testing revealed certain loopholes in the
code. also the way the shell sends data down to
the sysfs handlers changed which warranted the
change in the handlers.
Original change: http://git-master/r/#change,30134
(cherry picked from commit 64671e8dd11779b04e71048551cabfa8b04e3bb9)
Change-Id: Iccd02bd5a257312fd8ef764980005edaf28db0a7
Signed-off-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-on: http://git-master/r/30454
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Bug 804805
Change-Id: I040ae5888a8e013d8e57bfdd56f59af25607c77c
Reviewed-on: http://git-master/r/30413
Reviewed-by: Krishna Reddy <vdumpa@nvidia.com>
Tested-by: Krishna Reddy <vdumpa@nvidia.com>
Reviewed-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
|
|
Change-Id: If6ae23251aa615a678c8edb76d3c1e6463d86f2e
Signed-off-by: Peter De Schrijver <pdeschrijver@nvidia.com>
Change-Id: I50ffa54eacaf5b3973fcd6cb94eee56e46ec81bf
Reviewed-on: http://git-master/r/30384
Reviewed-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
|
|
This patch adds new generic events for dynamic power management
tracing:
- clock events class: used for clock enable/disable and for
clock rate change,
- power_domain events class: used for power domains transitions.
The OMAP architecture will be using the new events for PM debugging,
however the new events are made generic enough to be used by all
platforms.
Signed-off-by: Jean Pihet <j-pihet@ti.com>
Acked-by: Thomas Renninger <trenn@suse.de>
Cc: discuss@lesswatts.org
Cc: linux-pm@lists.linux-foundation.org
Cc: Thomas Renninger <trenn@suse.de>
Cc: Arjan van de Ven <arjan@linux.intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Len Brown <len.brown@intel.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>
LKML-Reference: <AANLkTinUmbSUUuxUzc8++pcb9gd1CZFdyTQFrveTBXyV@mail.gmail.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Change-Id: I7e1d1425214f5a90672f423ce882e4337f2d0114
Reviewed-on: http://git-master/r/30383
Reviewed-by: Daniel Willemsen <dwillemsen@nvidia.com>
Reviewed-by: Peter De Schrijver <pdeschrijver@nvidia.com>
Tested-by: Peter De Schrijver <pdeschrijver@nvidia.com>
Reviewed-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
|
|
Provide some basic trace facilities to the regulator API. We generate
events on regulator enable, disable and voltage setting over the actual
hardware operations (which are assumed to be the expensive ones which
require interaction with the actual device). This is intended to facilitate
debug of the performance and behaviour with consumers allowing unified
traces to be generated including the regulator operations within the
context of the other components of the system.
For enable we log the explicit delay for the voltage ramp separately to
the interaction with the hardware to highlight the time consumed in I/O.
We should add a similar delay for voltage changes, though there the
relatively small magnitude of the changes in the context of the I/O
costs makes it much less critical for most regulators.
Only hardware interactions are currently traced as the primary focus is
on the performance and synchronisation of actual hardware interactions.
Additional tracepoints for debugging of the logical operations can be
added later if required.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: Liam Girdwood <lrg@slimlogic.co.uk>
Change-Id: I351d02094bad5cfc5454b3b6c90853b714bee182
Reviewed-on: http://git-master/r/30382
Reviewed-by: Daniel Willemsen <dwillemsen@nvidia.com>
Reviewed-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Reviewed-by: Peter De Schrijver <pdeschrijver@nvidia.com>
Tested-by: Peter De Schrijver <pdeschrijver@nvidia.com>
Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com>
|
|
Made sure default DDR3 EMC DFS table is not applied to cardhu
processor board with LPDDR2.
Change-Id: I78bb2a4f80a5db00e04cb82c530924219e6baa78
Reviewed-on: http://git-master/r/30311
Tested-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Diwakar Tundlam <dtundlam@nvidia.com>
Tested-by: Diwakar Tundlam <dtundlam@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
Reviewed-by: Raymond Poudrier <rapoudrier@nvidia.com>
Tested-by: Raymond Poudrier <rapoudrier@nvidia.com>
|
|
When device sh532u is open, it calls board related initialization
and de- initialization function.
In the board related functions, the client can initialize the required
signal, power on/off the device etc.
bug 802264
Change-Id: Ie69a6e70c5d104489d248bef538e89263208ee54
Reviewed-on: http://git-master/r/30169
Tested-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-by: Danielle Sun <dsun@nvidia.com>
Tested-by: Danielle Sun <dsun@nvidia.com>
Reviewed-by: Prayas Mohanty <pmohanty@nvidia.com>
|
|
Per Tegra3 characterization results, do not use fractional ratios
for dividing host1x/3d/2d/epp/mpe/vi/vde/se clocks. Also prevent
using 1:1.5 ratio by system clock dividers (other fractional ratios
are still allowed for sclk). Change sclk rounding algorithm to round
up divider ladder, since sclk shared bus clock should honor maximum
shared user request.
Bug 803144
Change-Id: I7b4bb1bb21a4ce4bbfb958c9a603a868dc3c05b4
Reviewed-on: http://git-master/r/29937
Tested-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Bo Yan <byan@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
Reviewed-by: Diwakar Tundlam <dtundlam@nvidia.com>
Tested-by: Diwakar Tundlam <dtundlam@nvidia.com>
|
|
On Tegra3 VDD_CPU must be within [VDD_CORE - 300, VDD_CORE] range.
Updated tegra dvfs accordingly, and resolved circular dependencies
between CPU and CORE rails created by this requirement.
Change-Id: I9c332ca2b4f4ed1599cb0712eb3eca55a1fa1539
Reviewed-on: http://git-master/r/29935
Reviewed-by: Aleksandr Frid <afrid@nvidia.com>
Tested-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
Reviewed-by: Diwakar Tundlam <dtundlam@nvidia.com>
Tested-by: Diwakar Tundlam <dtundlam@nvidia.com>
|
|
Now that we have sysfs objects for smartdimmer, set our
default to disable for this feature.
Change-Id: Ie5a6755ff159496fe0e02a3f164325672954712d
Reviewed-on: http://git-master/r/29892
Reviewed-by: Laurence Harrison <lharrison@nvidia.com>
Tested-by: Laurence Harrison <lharrison@nvidia.com>
Reviewed-by: Jonathan Mayo <jmayo@nvidia.com>
Reviewed-by: Matthew Longnecker <mlongnecker@nvidia.com>
Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com>
|
|
Change-Id: If206f26e0f10f666fd7839c1ebb839eeb4899e21
Reviewed-on: http://git-master/r/29879
Reviewed-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Diwakar Tundlam <dtundlam@nvidia.com>
Tested-by: Diwakar Tundlam <dtundlam@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
|
|
Configuring the pins which are belonging to vddio_gmi to recommended state
to consume low power.
bug 807813
Change-Id: I18b67688b0e45ccd5f16ac3f1f8a7f4db3142bae
Reviewed-on: http://git-master/r/29628
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
Tested-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
|
|
Build Fix.
Bug 822432
Change-Id: Ia9d2d3ddc9aa9b2c00761ceb30a2bdcda8d261cf
Reviewed-on: http://git-master/r/30718
Reviewed-by: Pradeep Goudagunta <pgoudagunta@nvidia.com>
Tested-by: Pradeep Goudagunta <pgoudagunta@nvidia.com>
Reviewed-by: Pavan Kunapuli <pkunapuli@nvidia.com>
Reviewed-by: Daniel Willemsen <dwillemsen@nvidia.com>
|
|
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
Change-Id: Ia7155f3e94c127b18f2909f9f80583e5f74b8483
|
|
Conflicts:
arch/arm/mach-tegra/usb_phy.c
drivers/usb/gadget/fsl_tegra_udc.c
drivers/usb/host/ehci-tegra.c
drivers/video/tegra/dc/dc.c
Change-Id: I62d72b8b96d4039bd0d253583c415ae714fb2693
|
|
|
|
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
Original change breaks LP1 on t30.
This reverts commit 522f94b14b99c47322a72012fb5ce9a59c145630.
Change-Id: Ia3aacc5924987828aa0fd1e2c6ccc3c990b871c0
Reviewed-on: http://git-master/r/31023
Tested-by: Jin Qian <jqian@nvidia.com>
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Tested-by: Narendra Damahe <ndamahe@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
|
|
Original change breaks LP1 on t30.
This reverts commit b7e127ac1a4dbfd1fd66f02f8e0c7ac40e732674.
Change-Id: I337c03a7f927a54f96b502beebd1a580e469624d
Reviewed-on: http://git-master/r/31022
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Tested-by: Narendra Damahe <ndamahe@nvidia.com>
Tested-by: Jin Qian <jqian@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
|
|
Change-Id: I782ca4ffc94175e5e73535fbb0309173a72a83d5
Reviewed-on: http://git-master/r/30582
Tested-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Jin Qian <jqian@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
|
|
Change-Id: Ic30a091dd634b1857cdbfc5a0c47d34bc496b04f
Reviewed-on: http://git-master/r/29884
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
Setting CORE_PWR_REQ to high.
This is require to enable tracking regulator to supply more than
2A current for cardhu A03 board.
bug 805454
Change-Id: I4ff9d4d2bf106dc0d3d708fe9e1a7f7158dce27e
Reviewed-on: http://git-master/r/29623
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|