Age | Commit message (Collapse) | Author |
|
A malicious application can take advantage of the ION kmalloc heap
to create a specific memory chunk size to exercise a rowhammer
attack on the physical hardware.
The fix is designed to disable ION heap type.
CVE-2016-6728: A-30400942
Bug 1823317
Change-Id: I6b6d891a85da0c175f88cc1a3e48875796db80d4
Signed-off-by: Gagan Grover <ggrover@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1690291
GVS: Gerrit_Virtual_Submit
Reviewed-by: Bibek Basu <bbasu@nvidia.com>
Tested-by: Amulya Yarlagadda <ayarlagadda@nvidia.com>
Reviewed-by: Winnie Hsu <whsu@nvidia.com>
|
|
Using Tegra WDT to trigger FIQ when system is in soft lockup.
Bug 1581432
Change-Id: I853a88a3f6e9402c978db18c5a63e903c582040a
Signed-off-by: Renn Wu <rewu@nvidia.com>
Reviewed-on: http://git-master/r/265871
(cherry picked from commit f115f435d471af22ddec5e9d969662f79193f846)
Reviewed-on: http://git-master/r/680353
GVS: Gerrit_Virtual_Submit
Reviewed-by: Bibek Basu <bbasu@nvidia.com>
Reviewed-by: Winnie Hsu <whsu@nvidia.com>
|
|
Until now Android Sync framework was being used only in Android,
however, it can be used in Linux too as it provides a generic
synchronization framework. Hence removing Sync framework's dependency
on Android.
bug 1543760
bug 1601262
Change-Id: Ia3c21f0171d0147d0a035ff02c0673b63eced54e
Signed-off-by: Naveen Kumar S <nkumars@nvidia.com>
Reviewed-on: http://git-master/r/714736
Reviewed-by: Arto Merilainen <amerilainen@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: Bibek Basu <bbasu@nvidia.com>
Reviewed-by: Venkat Moganty <vmoganty@nvidia.com>
|
|
Implement Tegra WDT FIQ debug function.
Default is disabled.
Bug 1581432
Change-Id: Ic81ab4cd3285080016b37191e6e0fab18e330a30
Signed-off-by: Renn Wu <rewu@nvidia.com>
Reviewed-on: http://git-master/r/#/c/271988
Reviewed-on: http://git-master/r/662550
Reviewed-by: Bibek Basu <bbasu@nvidia.com>
Reviewed-by: Venkat Moganty <vmoganty@nvidia.com>
|
|
As CMA memory can only be used for Movable allocations,
Android lowmemkiller shouldn't consider this as free memory
for lowmem kill decisions. If it considered as free memory,
It can delay the killing of apps and lead to slowness of
system as memory allocations start waiting for kswap
daemon to free up the memory.
Bug 1550455
Change-Id: Ica8da48ef48912d89cde526f0ba3676df6ab10f1
Signed-off-by: Krishna Reddy <vdumpa@nvidia.com>
Reviewed-on: http://git-master/r/542209
(cherry picked from commit 24a7d99f9117e250dbf276d453c336b31dc2c127)
Reviewed-on: http://git-master/r/592901
GVS: Gerrit_Virtual_Submit
Reviewed-by: Matthew Pedro <mapedro@nvidia.com>
|
|
This reverts commit b0a90d9e2cbca96e755f7e385665f1be97fa9a69.
This patch causes slow responsiveness of apps as apps would start
waiting for kswap daemon to free memory when memory reaches
to critically low.
Change-Id: I9b6ed33d93a207c93560443152dfb0231215d31f
Signed-off-by: Krishna Reddy <vdumpa@nvidia.com>
Reviewed-on: http://git-master/r/552601
(cherry picked from commit 5c4229269e32b817feb906953ad2221f4aaa8ed1)
Reviewed-on: http://git-master/r/592899
GVS: Gerrit_Virtual_Submit
|
|
Power it on after initializatin in case current_threshold
is defined in device tree, or power it down.
Bug 200012361
Change-Id: Ic1b463af1812bf47b01ce04dc7714fb7965629e0
Signed-off-by: Roger Hsieh <rhsieh@nvidia.com>
Reviewed-on: http://git-master/r/434620
Reviewed-by: Timo Alho <talho@nvidia.com>
Reviewed-by: Deepak Nibade <dnibade@nvidia.com>
Reviewed-by: Jinyoung Park <jinyoungp@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
In case integration time for the sensor is not properly set,
User space may query the updated value of a sensor before an event
is generated from the sensor. Kernel driver should not send a stale or
invalid event in such cases, else it may impact performance and in some
cases, the user space application may behave in some undesirable way.
This change checks for such invalid events and makes sure such values
are not sent to user space.
Bug 1521699
Change-Id: I46f8d8defb2e63038f5c4947cbbe8e2b26c06f55
Signed-off-by: Sri Krishna chowdary <schowdary@nvidia.com>
Reviewed-on: http://git-master/r/425196
(cherry picked from commit 4611cda18bb67a3625c0dc802d666d801edb2ca4)
Reviewed-on: http://git-master/r/427686
Reviewed-by: Sachin Nikam <snikam@nvidia.com>
|
|
Currently, we print only syncpoint id and on sync timeout.
Also print syncpoint name in dump.
Bug 200007874
Change-Id: Ia28a5b12b037a0b718bd4e5727f20c19d8badd87
Reviewed-on: http://git-master/r/418926
(cherry picked from commit e79d93d205ca2daba2974745113088222fa90297)
Signed-off-by: Shridhar Rasal <srasal@nvidia.com>
Reviewed-on: http://git-master/r/426604
Reviewed-by: Terje Bergstrom <tbergstrom@nvidia.com>
|
|
Currently, we print only syncpoint id and thresh value on sync
timeout.
Also include current value in dump.
Bug 200007874
Change-Id: I6910e51aa10a5dc9f5d224b3251c3fb1ea6794d9
Reviewed-on: http://git-master/r/418136
(cherry picked from commit 41d63f2a1c48faeee4d9444818ada132968b7bc8)
Signed-off-by: Shridhar Rasal <srasal@nvidia.com>
Reviewed-on: http://git-master/r/418739
Reviewed-by: Terje Bergstrom <tbergstrom@nvidia.com>
|
|
Remove suspend and resume pm ops as sensorservice takes
care of activate/deactivate of sensor as required.
Also, put the device to standby mode if regulator is still enabled.
Change-Id: I5169409f679319fe42c89d7debd305c5c885fd15
Signed-off-by: Sri Krishna chowdary <schowdary@nvidia.com>
Reviewed-on: http://git-master/r/415042
Reviewed-by: Mandar Padmawar <mpadmawar@nvidia.com>
Tested-by: Mandar Padmawar <mpadmawar@nvidia.com>
|
|
On success, ina230_set_channel needs to return the number of
characters written.
Change-Id: I4ed249c0c4c86792b3b590eb4c1a532dcfd57f3a
Signed-off-by: Timo Alho <talho@nvidia.com>
Reviewed-on: http://git-master/r/422792
(cherry picked from commit 0ad59e7418ae0809354e5178ee641b69deda3ad0)
Reviewed-on: http://git-master/r/422799
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
|
|
- Any lingering workqueue must be cancelled
during the shutdown, to prevent them from running
during a shutdown
- In most cases, they are harmless, but they will
trigger a warning if the i2c bus is shutdown during the
shutdown as done on some platforms
Bug 1522172
Change-Id: I465e19ef793cf72f5f533b0e2c9e9f3e837c2133
Signed-off-by: Sang-Hun Lee <sanlee@nvidia.com>
Reviewed-on: http://git-master/r/421345
(cherry picked from commit b04ebe7fc2a77897b0020412f2a1ab0de94aa7c1)
Reviewed-on: http://git-master/r/422776
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Kerwin Wan <kerwinw@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
- Depending on the platform, i2c bus may be shutdown
as we shutdown the systme
- In such a case, any lingering workqueue would slowdown
the system, as the access will be made to the i2c bus
which has been shutdown
- To mitigate the above, cancel all workqueue jobs as we shutdown
Bug 1522172
Change-Id: Idebab822c0ef8ddad7352ef25a546acb3f3e5870
Signed-off-by: Sang-Hun Lee <sanlee@nvidia.com>
Reviewed-on: http://git-master/r/420889
(cherry picked from commit 8b39b8db93e5b34672b7cbcf9f6c5ec40398ca83)
Reviewed-on: http://git-master/r/422775
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Kerwin Wan <kerwinw@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
into promotion_build
Change-Id: I9418a05ad5c56b2e902249218bac2fa594d99f56
|
|
Added a debugfs for auto_conv value reading.
Bug 1514756
Signed-off-by: Jinyoung Park <jinyoungp@nvidia.com>
Reviewed-on: http://git-master/r/414751
(cherry picked from commit a7cc5553eb36afa799ae580d2e4c06f399e5bd8f)
Change-Id: Ia7fb91dab51972235885d7a087a84ce4aabd690b
Signed-off-by: Jinyoung Park <jinyoungp@nvidia.com>
Reviewed-on: http://git-master/r/418393
Reviewed-by: Diwakar Tundlam <dtundlam@nvidia.com>
|
|
Added current source initialization for CH0 and CH3 before
auto conversion configuration.
The current sources should be configured with preferred settings
before perform auto conversion to get expected result of auto conversion.
Bug 1514756
Signed-off-by: Jinyoung Park <jinyoungp@nvidia.com>
Reviewed-on: http://git-master/r/414750
(cherry picked from commit d22d48a2ea781aef641498e63c1bbb827a5b0a76)
Change-Id: I1c5440f8021a90f3eee4b80c3f70ab1956ac0cf5
Signed-off-by: Jinyoung Park <jinyoungp@nvidia.com>
Reviewed-on: http://git-master/r/418392
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Diwakar Tundlam <dtundlam@nvidia.com>
|
|
Bug 200004122
Conflicts:
drivers/cpufreq/cpufreq.c
drivers/regulator/core.c
sound/soc/codecs/max98090.c
Change-Id: I9418a05ad5c56b2e902249218bac2fa594d99f56
Signed-off-by: Ishan Mittal <imittal@nvidia.com>
|
|
Change default settings for proximity channel as below
Gain: x16, LED Current: 100mA, Duty Cycle: 100%, PMF: 30KHz
N_Pluse: 5, Measurement Repeat Rate: 100ms
This change also
- Enables saturation detection.
- replaces mdelay with msleep since all delays are >= 10 ms.
Bug 1496949
Bug 200003335
Bug 1510031
Change-Id: Id4bce839b10ab356141d5cbf28a31fa414fca768
Signed-off-by: wahsu <wahsu@nvidia.com>
Signed-off-by: Sri Krishna chowdary <schowdary@nvidia.com>
Reviewed-on: http://git-master/r/411380
(cherry picked from commit ebbd4163499e7cea62e967ec352cac07fcd53231)
Reviewed-on: http://git-master/r/416937
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Modify initialization sequence to let iqs253 sensor
tune itself to the environment. Once tuning is done
disable ATI, DYCAL, ACF, specify LTA Halt time as always and
keep the device in streaming mode as event mode can have issues.
With this, the delay to detect user proximity event reduced
from 20 secs to less then 1 secs. However, the very first time
after reboot when user stays in vicinity of device for around 30 secs,
detecting user away takes around 30 secs. After that this issue does not
occur.
Also, reduce the work queue delay to 1 sec.
Bug 1499925
Change-Id: I00b0d9a5381ec14b71eb6b5a76a651eb015969d5
Signed-off-by: Sri Krishna chowdary <schowdary@nvidia.com>
Reviewed-on: http://git-master/r/414867
(cherry picked from commit 4481221267b346d99ae02d122a4a8452776bf9b2)
Reviewed-on: http://git-master/r/416934
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
into promotion_build
|
|
Bug 200004122
Bug 1511804
This merge takes AOSP commits from android-3.10 branch
Change-Id: I07ec2468114db0366d63777142c9572bbfadbc45
Signed-off-by: Ishan Mittal <imittal@nvidia.com>
|
|
Add below optional value can be overrid by DT for project.
If no add in DT will load default value.
1)integration-time.
Default:"480000"
2)max-range.
Default:"78643.2"
3)resolution.
Default:"307"
4)power-consumed.
Default:"1670"
Bug 1496947
Change-Id: I8718bf5636042bc801574c8e4177a12e5a948540
Signed-off-by: steven <skao@nvidia.com>
Signed-off-by: Sri Krishna chowdary <schowdary@nvidia.com>
Reviewed-on: http://git-master/r/395755
Reviewed-on: http://git-master/r/411415
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Pritesh Raithatha <praithatha@nvidia.com>
Reviewed-by: Mitch Luban <mluban@nvidia.com>
|
|
mdelay for 10 msec causes applications to miss vsync.
change to usleep_range.
also, move sleep above read ATI status rather than below.
Bug 1510031
Change-Id: I5cab28ff985730e49772531b055ba4eb8107bb94
Signed-off-by: Brian Harris <brianh@nvidia.com>
Reviewed-on: http://git-master/r/405295
(cherry picked from commit 03a10728217b5637d8756540138a4bca949a24cd)
Signed-off-by: Sri Krishna chowdary <schowdary@nvidia.com>
Reviewed-on: http://git-master/r/415061
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Sachin Nikam <snikam@nvidia.com>
|
|
- Once the shutdown has been called, any access to
i2c needs to be disallowed to avoid a race
Bug 1510778
Change-Id: I93cc1ec4cdadfe2084b6aa5a8bc9d2b6cf56e879
Signed-off-by: Sang-Hun Lee <sanlee@nvidia.com>
Reviewed-on: http://git-master/r/411189
Reviewed-by: Riham Haidar <rhaidar@nvidia.com>
Tested-by: Riham Haidar <rhaidar@nvidia.com>
|
|
Currently we print only the fence memory address if the fence
times out. This is not enough for debugging *why* the fence timed
out.
This patch modifies timeout routine so that we print the syncpoints
that relate to the current fence.
Bug 200006324
Change-Id: Iae103d4a4ba65584333e46de72240190699a0cef
Signed-off-by: Arto Merilainen <amerilainen@nvidia.com>
Reviewed-on: http://git-master/r/413172
GVS: Gerrit_Virtual_Submit
Reviewed-by: Terje Bergstrom <tbergstrom@nvidia.com>
|
|
Change permissions of ui_input to read only by user and group.
Bug 1513829
Change-Id: I0b651ac75bbb5445a286882e8973b2fc05156dec
Signed-off-by: Timo Alho <talho@nvidia.com>
Reviewed-on: http://git-master/r/411363
(cherry picked from commit cf112731854b96393468c05e8c953a09f840903f)
Reviewed-on: http://git-master/r/412036
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Terje Bergstrom <tbergstrom@nvidia.com>
|
|
Fix a wrong return from palmas_gpadc_start_convertion
Bug 1512199
Change-Id: I7be181554288719550786b568088b1390fcce0c3
Signed-off-by: pchiang <pchiang@nvidia.com>
Reviewed-on: http://git-master/r/408117
Reviewed-by: Riham Haidar <rhaidar@nvidia.com>
Tested-by: Riham Haidar <rhaidar@nvidia.com>
|
|
Add ui_input node to allow simultaneously reading current and voltage
from one triggered conversion cycle. Reading from this node will
force the INA to operate on triggered mode for the duration of the
conversion.
Bug 1513829
Change-Id: I779e0d88340bc68bd161ddd00423be941559d5df
Signed-off-by: Timo Alho <talho@nvidia.com>
Reviewed-on: http://git-master/r/410119
(cherry picked from commit 52a570a11902ba9aac1fee4bbf8789c994f82dae)
Reviewed-on: http://git-master/r/410145
Reviewed-by: Juha Tukkinen <jtukkinen@nvidia.com>
|
|
ltr659 resume callback waits for 600 msec as ltr558 needed power on
delay. This affects device resume time as all devices use same
thread to resume.
Removing the delay for ltr659 could resolve this issue, but since
Sensorservice takes care of enabling/disabling the sensor device as
required, suspend/resume remain a overhead anyway. So, remove them.
Bug 200002359
Change-Id: Ib847cc015ae3169c45c25d252588e9439da9b1d3
Signed-off-by: Sri Krishna chowdary <schowdary@nvidia.com>
Reviewed-on: http://git-master/r/408755
(cherry picked from commit fb566c5ae4dd161db35463683b0fdefab04032c1)
Reviewed-on: http://git-master/r/410748
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Sachin Nikam <snikam@nvidia.com>
|
|
Modified the implementation according to Sri's comments, the previous
one is http://git-master/r/385968
1. removed shutdowm callback
2. unregister device before destroying workqueue
3. enable regulator before registering device
Bug 1469053
Change-Id: I39af182acacec8e4f62e1f4d2a3cf8210ee419c5
Signed-off-by: Louis Li <louli@nvidia.com>
Reviewed-on: http://git-master/r/408589
(cherry picked from commit d20b9aa96306d7019096a6f14b21c21c5f27f66d)
Reviewed-on: http://git-master/r/408581
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Sri Krishna Chowdary <schowdary@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: Sachin Nikam <snikam@nvidia.com>
|
|
Bug 1495051
Change-Id: I2bf7838dc79848017bf38affe6d61e4349fb3d49
Signed-off-by: Sri Krishna chowdary <schowdary@nvidia.com>
Reviewed-on: http://git-master/r/400089
(cherry picked from commit 4a556c1bf36e12034f653dc129084954c98a896b)
Reviewed-on: http://git-master/r/404970
(cherry picked from commit 050e92969edd6cd0e28542598a36eb1c50441edc)
Reviewed-on: http://git-master/r/408090
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Get proper device data from device pointer on different
platform driver callbacks.
bug 1493891
Change-Id: I4402e60590d4edf26d67360c97e2f8d163bdd4c8
Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-on: http://git-master/r/392295
Reviewed-on: http://git-master/r/406900
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
|
|
On device probe
workqueue should be created before registering device to avoid
scheduling workqueue on non existant workqueue.
On device remove
1. Regulator can still be in use till all pending works are
finished. Do not free them before ensuring no more access to
device will occur.
2. Remove sysfs to ensure no user access after destroying
the workqueue
Ideally we may want to regulator_put on device shutdown but
that step requires destroying the workqueue and unregistering sysfs.
Unregistering sysfs probably causes Bug 1463497 and hence taking the
safe option for now and removing device shutdown alogether.
Bug 1507601
Change-Id: I9e1a74dc1f4287c381812ee5a2a8a5e2eefe15dd
Signed-off-by: Sri Krishna chowdary <schowdary@nvidia.com>
Reviewed-on: http://git-master/r/404368
(cherry picked from commit c16e0090f23132b343083c51057b729f04809028)
Reviewed-on: http://git-master/r/405260
GVS: Gerrit_Virtual_Submit
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
|
|
checked against 0
commit f764cd68d9036498f08fe8834deb6a367b5c2542 upstream.
Zero-initializing ether_type masked that the ether type would never be
obtained for 8021x packets and the comparison against eapol_type
would always fail.
Reported-by: Jes Sorensen <Jes.Sorensen@redhat.com>
Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
|
commit abe5d64d1a74195a44cd14624f8178b9f48b7cc7 upstream.
This patch fixes the following sparse warning :
drivers/staging/serqt_usb2/serqt_usb2.c:727:40: warning: restricted __le16 degrades to integer
Signed-off-by: Himangi Saraogi <himangi774@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
|
Dumps registers and stacktrace into console-ramoops when called
from a watchdog fiq.
Change-Id: Ib6fab5a52f670db18e64214d5e4890e8292a749c
Signed-off-by: Arve Hjønnevåg <arve@android.com>
|
|
specific code
This allows the output from the register and stack trace code to be
sent elsewhere.
Change-Id: I41bb0d5a25e1b9ca55feef5dbd675818b2f832d5
Signed-off-by: Arve Hjønnevåg <arve@android.com>
|
|
commit 268d1e799663b795cba15c64f5d29407786a9dd4 upstream.
According to National Instruments' PCI-DIO-96/PXI-6508/PCI-6503 User
Manual, the physical address in PCI BAR1 needs to be OR'ed with 0x80 and
written to register offset 0xC0 in the "MITE" registers (BAR0). Do so
during initialization of the National Instruments boards handled by the
"8255_pci" driver. The boards were previously handled by the
"ni_pcidio" driver, where the initialization was done by `mite_setup()`
in the "mite" module. The "mite" module comes with too much extra
baggage for the "8255_pci" driver to deal with so use a local, simpler
initialization function.
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
|
Add fiq_debugger_arm64.c that implements the platform-specific
functions.
Change-Id: I4d8b96777bb8503a93d4eb47bbde8e018740a5bf
Signed-off-by: Colin Cross <ccross@android.com>
|
|
Split arm support into a separate .c file that is only built for
CONFIG_ARM.
Change-Id: Iba16f4d51608bf9c3e5c8acefefcd38fead9797c
Signed-off-by: Colin Cross <ccross@android.com>
|
|
IRQ mode already passes in a struct pt_regs from get_irq_regs().
FIQ mode passes in something similar but not identical to a
struct pt_regs - FIQ mode stores the spsr of the interrupted mode
in slot 17, while pt_regs expects orig_r0.
Replace the existing mixture of void *regs, unsigned *regs, and
struct pt_regs * const with const struct pt_regs *. Modify
dump_regs not to print the spsr since it won't be there in a
struct pt_regs anyways. Modify dump_allregs to highlight the
mode that was interrupted, making spsr easy to find there.
Change-Id: Ibfe1723d702306c7605fd071737d7be9ee9d8c12
Signed-off-by: Colin Cross <ccross@android.com>
|
|
Allow compiling fiq_debugger.c without CONFIG_FIQ_GLUE for
platforms that don't support FIQs.
Change-Id: Iabdfd790d24fa9d47b29d2f850c567af2dcad78f
Signed-off-by: Colin Cross <ccross@android.com>
|
|
Rename variables and functions in the global namespace to avoid
future collisions.
Change-Id: Ic23a304b0f794efc94cc6d086fddd63231d99c98
Signed-off-by: Colin Cross <ccross@android.com>
|
|
Move fiq_debugger into drivers/staging/android/fiq_debugger/ to
allow for sharing between ARM and ARM64.
Change-Id: I6ca5e8b7e3d000f57da3234260261c5592cef2a8
Signed-off-by: Colin Cross <ccross@android.com>
|
|
This patchs adds an explicit triggered mode into ina3221 driver. There
are now four modes of operation for ina3221 in the device driver
(1) FORCED_TRIGGERED
(2) FORCED_CONTINUOUS
(3) TRIGGERED
(4) CONTINUOUS
First two (1, 2) are selectable from user space. If mode is not forced
from user space, and critical or warning current limit has been
configured, driver automatically picks the mode from latter two (3, 4)
depending on the system activity.
Operation mode of ina3221 can be selected by writing into running_mode
sysfs entry.
* Writing >0 enables FORCED_CONTINUOUS mode
* Writing 0 enables FORCED_TRIGGERED mode
* Writing <0 enables automatic mode selection of the driver
Change-Id: I935e9be3280b46b5ee3dd83f50e4845ae2eafe0b
Signed-off-by: Timo Alho <talho@nvidia.com>
Reviewed-on: http://git-master/r/392886
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
|
|
This reverts commit 12eee98b377abc0c061ad820aa4cc8d1d95a15d3.
Bringing back the Dt upport for autoconversion parameter configuration
on plamas ADC.
Change-Id: Ibaf912945653c3569ad6886f7a7dac4495c32831
Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-on: http://git-master/r/392652
|
|
This reverts commit cc243afc6ecf4b49d2193605c37c6cc61aff6ae9.
Change-Id: I63e08fdbe94c9061e6addfc42b5ffaab5f9a6b0d
Signed-off-by: Alex Van Brunt <avanbrunt@nvidia.com>
Reviewed-on: http://git-master/r/392611
GVS: Gerrit_Virtual_Submit
Reviewed-by: Sridhar Lavu <slavu@nvidia.com>
Tested-by: Sridhar Lavu <slavu@nvidia.com>
|
|
Add DT parsing for auto conversion configurations on palmas-adc.
The autoconversion subnode is require as
gpadc {
::::
auto_conv0 {
// Auto-conversion 0 parameters
};
auto_conv1 {
// Auto-conversion 1 parameters
};
::::::::
};
Change-Id: Id730213f6d5c685efef65cee9c74c4e33c81c66c
Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-on: http://git-master/r/392401
|
|
sar work function uses sar_wq and not wq. Fix it.
Bug 1490840
Change-Id: I28b1575648c6aed77243a0d8fde84844ff69a09c
Signed-off-by: Sri Krishna chowdary <schowdary@nvidia.com>
Reviewed-on: http://git-master/r/390213
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Tested-by: Daniel Fu <danifu@nvidia.com>
Reviewed-by: Mitch Luban <mluban@nvidia.com>
|