summaryrefslogtreecommitdiff
path: root/drivers/base
AgeCommit message (Collapse)Author
2017-10-06mfd: apalis-tk1-k20: clean-up and fix support for 0.10 k20 fwApalis-TK1_LXDE-Image_2.7b4-20171007Dominik Sliwa
Signed-off-by: Dominik Sliwa <dominik.sliwa@toradex.com> Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
2017-04-04regmap: irq: dispose all virtual irq before removing domainLaxman Dewangan
It is require to dispose all virtual irq of hwirq on chip created on given irq domain before removing this irq domain. Hence dispose all mapped irqs before deleting the irq domains in regmap_del_irq_chip(); Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com> Reviewed-by: Javier Martinez Canillas <javier@osg.samsung.com> Tested-by: Javier Martinez Canillas <javier@osg.samsung.com> Signed-off-by: Mark Brown <broonie@kernel.org>
2017-04-04regmap: irq: Remove domain on exitMark Brown
irqdomain now supports removal of domains on exit so we can properly clean up on deletion of a regmap irqchip. Signed-off-by: Mark Brown <broonie@linaro.org>
2017-04-04regmap-irq: set IRQF_ONESHOT flag to ensure IRQ requestValentin Rothberg
Since commit 1c6c69525b40eb76de8adf039409722015927dc3 ("genirq: Reject bogus threaded irq requests") threaded IRQs without a primary handler need to be requested with IRQF_ONESHOT, otherwise the request will fail. The %irq_flags flag is used to request the threaded IRQ and is also a parameter of the caller. Hence, we cannot be sure that IRQF_ONESHOT is set. This change avoids the potentially missing flag by setting IRQF_ONESHOT when requesting the threaded IRQ. Generated by: scripts/coccinelle/misc/irqf_oneshot.cocci Signed-off-by: Valentin Rothberg <Valentin.Rothberg@lip6.fr> Signed-off-by: Mark Brown <broonie@kernel.org>
2015-01-06firmware: avoid firmware-loading console log spewRajkumar Kasirajan
Disabled default printing of falcon firmware direct loading to avoid console log spew. Bug 200048667 Change-Id: I34b34864f64d44ef009586e7e847041b10b06d67 Signed-off-by: Rajkumar Kasirajan <rkasirajan@nvidia.com> Reviewed-on: http://git-master/r/660016 GVS: Gerrit_Virtual_Submit Reviewed-by: Bibek Basu <bbasu@nvidia.com> Reviewed-by: Venkat Moganty <vmoganty@nvidia.com> Reviewed-by: Matthew Pedro <mapedro@nvidia.com>
2014-10-02firmware: enable default printing of direct loadingBibek Basu
Move pr_dbg to pr_info for direct firmware loading. Bug 200026940 Change-Id: I617fde8aac85be01857b963c0e18ae6cf22aa444 Signed-off-by: Bibek Basu <bbasu@nvidia.com> Reviewed-on: http://git-master/r/542581 GVS: Gerrit_Virtual_Submit Reviewed-by: Venkat Moganty <vmoganty@nvidia.com>
2014-08-26dma:coherent: manage resizable memory with single deviceKrishna Reddy
This is necessary to avoid unusable memory between device nodes. Bug 1517584 Change-Id: I37ac104fa5e512758a4df299424fa0456f368bb6 Signed-off-by: Krishna Reddy <vdumpa@nvidia.com> Reviewed-on: http://git-master/r/486855 (cherry picked from commit 5c76b9162730826191c71fcf082d3457e5496bc0) Reviewed-on: http://git-master/r/488266 GVS: Gerrit_Virtual_Submit Reviewed-by: Matthew Pedro <mapedro@nvidia.com>
2014-06-30dma: coherent: fix resizable carveout issuesKrishna Reddy
Fix races with dev_start and dev_end. Flush cache during heap grow. Fix incorrect return code for heap allocations. Bug 200016405 Change-Id: I77f8016c9833e9615eab4d9cf66acaf3da1cefed Signed-off-by: Krishna Reddy <vdumpa@nvidia.com> Reviewed-on: http://git-master/r/431950 GVS: Gerrit_Virtual_Submit
2014-06-30base: dma-contiguous: add API to specify the start of allocationKrishna Reddy
Add API dma_alloc_at_from_contiguous to support allocations at specific phys address. Bug 200016405 Change-Id: I425a25af3163c391e6b7d9b8bc3299f3ffc7c7c8 Signed-off-by: Krishna Reddy <vdumpa@nvidia.com> Reviewed-on: http://git-master/r/431949 GVS: Gerrit_Virtual_Submit
2014-06-20dma: coherent: error handling on heap resize failureDeepak Nibade
- Update memory resize callbacks to return error codes - error handling on heap resize update failure Bug 1487804 Bug 1517584 Change-Id: I5ac044677e883fbecf6d04a8c1e83794325703f3 Signed-off-by: Deepak Nibade <dnibade@nvidia.com> Signed-off-by: Vandana Salve <vsalve@nvidia.com> Reviewed-on: http://git-master/r/423748 Reviewed-by: Krishna Reddy <vdumpa@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
2014-06-18PM / Runtime: Fix error path for prepareUlf Hansson
If a device prepare callback for some reason would fail, the PM core prevented the device from going inactive forever. In this case, to reverse the pm_runtime_get_noresume() we invokes the asyncronous pm_runtime_put(), thus restoring the usage count. bug 1518244 Change-Id: Ia4984630e71abeb55ef90a19799d1fea700b2148 Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> (cherry picked from commit aa1b9f13b3346352455bfdc343ecff7667b84ff5) Signed-off-by: Allen Yu <alleny@nvidia.com> Reviewed-on: http://git-master/r/423999 Reviewed-on: http://git-master/r/424177 Reviewed-by: Shridhar Rasal <srasal@nvidia.com> GVS: Gerrit_Virtual_Submit Reviewed-by: Mitch Luban <mluban@nvidia.com>
2014-05-27PM/Domain: cancel workqueue upon power offSang-Hun Lee
- If there is any workqueue power_off_delayed_work pending when calling pm_genpd_suspend or its variants, the workqueue will trigger post pm_genpd_suspend operation, causing a double shutdown - This is fixing a bug from 3f4475eade08af799d3e1a100e24e1b418abbba5 Bug 1510778 Change-Id: I7569a8712638a231a6f91199f10a75654bde7bf9 Signed-off-by: Sang-Hun Lee <sanlee@nvidia.com> Reviewed-on: http://git-master/r/411675 Reviewed-by: Mitch Luban <mluban@nvidia.com>
2014-04-23regmap: irq: print wakeup sub-irq on system resumeLaxman Dewangan
If system is resumed by the device whose interrupt is handled by regmap-irq then prints the sub-irq of device which actually cause the wakeup of system. This helps on finding the submodule which cause system resume. Change-Id: I85838b2551d69ac42863300b3a8ddd0722ec2585 Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com> Reviewed-on: http://git-master/r/395692
2014-04-11PM/Domains: Export always-on governorArto Merilainen
Some drivers that are compiled as modules may need to access always-on governor structure, however, this structure is not yet exported. This patch adds necessary exports. Bug 1476801 Change-Id: I22adfb672ce79f364b203def782e088ebbbb3e19 Signed-off-by: Arto Merilainen <amerilainen@nvidia.com>
2014-04-10PM/Domain: Export pm_genpd symbolsArto Merilainen
Drivers compiled as modules may need to access some genpd functions directly. This patch adds few new bindings that have been found useful. Bug 1476801 Change-Id: I19807977147d334f88be6b582e1cd0eb06854f12 Signed-off-by: Arto Merilainen <amerilainen@nvidia.com> Reviewed-on: http://git-master/r/387607 GVS: Gerrit_Virtual_Submit Reviewed-by: Prashant Gaikwad <pgaikwad@nvidia.com> Reviewed-by: Terje Bergstrom <tbergstrom@nvidia.com>
2014-03-28regmap: add support for mask all interrupts on shutdownLaxman Dewangan
Add API to implement the mask of all interrupt which can be called during shutdown process. This will make sure that no interrupt get generated during shutdown. Change-Id: I69d6a9b1e6323b1a1ec722d23e52360949448ff7 Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com> Reviewed-on: http://git-master/r/387781
2014-03-27dma: coherent: support residual memory chunkVandana Salve
Add support to handle alloc/release of residual memory chunk which is not multiple of cma_chunk_size bug 1473619 Change-Id: I9d5c777e376526b4a7944d5b8cd54785d631f031 Signed-off-by: Vandana Salve <vsalve@nvidia.com> Reviewed-on: http://git-master/r/385777 Reviewed-by: Krishna Reddy <vdumpa@nvidia.com>
2014-03-11dma: coherent: Handle resizable coherent memoryVandana Salve
Support to handle resizable/fixed size coherent memory Add debugfs support bug 1445123 Change-Id: I77c250ddfe95609a5e7edb9093b8f1c23652a0b4 Signed-off-by: Vandana Salve <vsalve@nvidia.com> Reviewed-on: http://git-master/r/362440 Reviewed-by: Krishna Reddy <vdumpa@nvidia.com>
2014-02-26dmabuf: Support driver dataArto Merilainen
Occassionally we need to store driver/device specific data of a device that survives over attach/detach sequence. This patch adds support for defining drvdata inside dmabuf. Bug 1450489 Change-Id: I840d415657a07ef86476e32bcac4e13a8706ece4 Signed-off-by: Arto Merilainen <amerilainen@nvidia.com> Reviewed-on: http://git-master/r/368139 Reviewed-by: Krishna Reddy <vdumpa@nvidia.com> Reviewed-by: Terje Bergstrom <tbergstrom@nvidia.com>
2014-02-24base: dma-coherent: Add maximum alignment orderVandana Salve
Alignment order for coherent dma buffer is set by buffer size. For large buffer, it is a waste of address space. So using ARM_DMA_IOMMU_ALIGNMENT configurable parameter to limit maximum alignment order to reduce the waste during coherent memory allocation. This fixes alignment issue seen by gk20a Change-Id: I7197f66fe67161137269ce64fdada8295bfc1686 Signed-off-by: Vandana Salve <vsalve@nvidia.com> Reviewed-on: http://git-master/r/356347 GVS: Gerrit_Virtual_Submit Reviewed-by: Krishna Reddy <vdumpa@nvidia.com>
2014-02-13regmap: cache: Add interface to change volatile attributeAlex Frid
Defined regmap driver callback to set access attribute for the single register as either volatile or cached. Provided the respective public interface for changing access attribute on top of the callback. Cleared cache present bit to invalidate register cache whenever access is actually changed. Bug 1454969 Change-Id: If4e29ccc4c67892974ab6095f9d82e001198d19d Signed-off-by: Alex Frid <afrid@nvidia.com> Reviewed-on: http://git-master/r/365704 Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
2014-02-10PM / QoS: check NULL and ENODEV on power.qospchiang
fix kernel panic when qos is not null Bug 1442069 Bug 1430231 Change-Id: I8810009e8f2a72730cfb253b245434d9e0806b9c Signed-off-by: pchiang <pchiang@nvidia.com> Reviewed-on: http://git-master/r/357069 Reviewed-by: Terje Bergstrom <tbergstrom@nvidia.com> Reviewed-on: http://git-master/r/360175 GVS: Gerrit_Virtual_Submit
2014-02-06Add firmware path to the firmware search paths.Neil Gabriel
If the kernel is able to find firmware in the kernel firmware search path (when requested through request_firmware()) it will load it directly without the involvement of the usermodehelper/ udev process (which is not always available). Bug 1403956 Change-Id: Ic66b6dc306002c7baac541cf94ad89d29c1d397d Signed-off-by: Neil Gabriel <ngabriel@nvidia.com> Reviewed-on: http://git-master/r/360474 Reviewed-by: Mitch Luban <mluban@nvidia.com> Reviewed-on: http://git-master/r/362435
2014-02-06Attempt kernel firmware load before going to udev.Neil Gabriel
request_firmware() should fall back to usermodehelper routines to load firmware only after a failed attempt to load it directly. Prior to this change, the code will attempt to lock the usermodehelper state before attempting to load the firmware directly. If the usermodehelper is disabled, the lock attempts will fail and request_firmware() will exit without even attempting a direct load. Bug 1403956 Change-Id: I26c502d30657eab3d382d139618f9daa366068cf Signed-off-by: Neil Gabriel <ngabriel@nvidia.com> Reviewed-on: http://git-master/r/358303 Reviewed-by: Mitch Luban <mluban@nvidia.com> Reviewed-on: http://git-master/r/362065
2014-02-06PM/Domain: Propagate restore_state error to callerTerje Bergstrom
genpd_restore_dev() might fail. Propagate the failure to caller of pm_genpd_runtime_resume(). Change-Id: Ie20187ecc90a69d989a531db776d52c81956b899 Signed-off-by: Terje Bergstrom <tbergstrom@nvidia.com> Reviewed-on: http://git-master/r/363858 Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
2014-01-16PM/Domain: fix delayed power-off raceAndrew Bresticker
Commit 5ffea6f ["CHROMIUM: PM/domains: add delayed power off capability"] introduced the ability to defer the power-off of a power domain and used a PM notifier to flush any delayed power-off work for a power domain. The PM notifiers, however, run before tasks are frozen and outstanding runtime PM requests are flushed. A runtime resume may run during this time scheduling a delayed power-off which may not run until after pm_genpd_prepare(), where the state of the domain at suspend is recorded. As a result, a device which expected to be powered off across suspend may be powered up unexpectedly during resume because pm_genpd_prepare() recorded the state of the device as on at suspend. Fix this race by flushing delayed power-off work in pm_genpd_prepare() instead. Change-Id: Ia3f83304eaa5eb8a6396175eaa98192a392692ad Signed-off-by: Andrew Bresticker <abrestic@chromium.org> Signed-off-by: Mark Zhang <markz@nvidia.com> Reviewed-on: http://git-master/r/355390 Reviewed-by: Shridhar Rasal <srasal@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
2013-12-30PM / QoS: cleanup FLAGS notifiers during removingBryan Wu
DEV_PM_QOS_FLAGS was introduced in commit c92b96f94cdc26e33ea490a9a0e02c16988a6dd6, but it was forgot to remove in dev_pm_qos_remove_notifier(). So without this patch, kernel will enter an endless loop in notifier_chain_register() when reloading a module multiple times. Bug 1421146 Change-Id: I6b98fe57a70f172d110cc5f257ce4f853a447802 Signed-off-by: Bryan Wu <pengw@nvidia.com> Reviewed-on: http://git-master/r/347823 Reviewed-by: Terje Bergstrom <tbergstrom@nvidia.com>
2013-12-25PM/ runtime : Add WARN_ON for usage_cnt decShridhar Rasal
- Added WARN_ON for usage count decrement when it is already zero. bug 1410313 Change-Id: I6ea8a1760d188b09c295eac6d8a63f74e2132ed8 Signed-off-by: Shridhar Rasal <srasal@nvidia.com> Reviewed-on: http://git-master/r/332797 Reviewed-by: Sachin Nikam <snikam@nvidia.com>
2013-12-16Merge tag 'v3.10.24' into HEADAjay Nandakumar
This is the 3.10.24 stable release Change-Id: Ibd2734f93d44385ab86867272a1359158635133b
2013-12-08PM: move device_pm_remove call before the calling bus_remove_deviceR Raj Kumar
We hit an hang issue when removing a sd device during suspend mode. This is may due to improper handling of acquired resources of device. By moving the device_pm_remove call in the device_del before calling bus_remove_device, fixed the hang issue. Bug 1393856 Change-Id: Ice8e8e62f96631166dfe630f2571817a6dd3308c Signed-off-by: R Raj Kumar <rrajk@nvidia.com> Reviewed-on: http://git-master/r/338118 Reviewed-by: Venu Byravarasu <vbyravarasu@nvidia.com>
2013-12-08devres: release resources on device_del()R Raj Kumar
Some platform devices are driven without driver attached, so managed resources can be acquired without driver attached. Make sure such resources are released by calling devres_release_all() in device_del(). Bug 1393856 Change-Id: I1e43647e143bdb363b939b97c77b4a508f281e7c Signed-off-by: Tejun Heo <htejun@gmail.com> Signed-off-by: Jeff Garzik <jeff@garzik.org> Signed-off-by: R Raj Kumar <rrajk@nvidia.com> Reviewed-on: http://git-master/r/338117 Reviewed-by: Venu Byravarasu <vbyravarasu@nvidia.com> GVS: Gerrit_Virtual_Submit
2013-12-04PM / runtime: Use pm_runtime_put_sync() in __device_release_driver()Rafael J. Wysocki
commit baab52ded242c35a2290e1fa82e0cc147d0d8c1a upstream. Commit fa180eb448fa (PM / Runtime: Idle devices asynchronously after probe|release) modified __device_release_driver() to call pm_runtime_put(dev) instead of pm_runtime_put_sync(dev) before detaching the driver from the device. However, that was a mistake, because pm_runtime_put(dev) causes rpm_idle() to be queued up and the driver may be gone already when that function is executed. That breaks the assumptions the drivers have the right to make about the core's behavior on the basis of the existing documentation and actually causes problems to happen, so revert that part of commit fa180eb448fa and restore the previous behavior of __device_release_driver(). Reported-by: Tomi Valkeinen <tomi.valkeinen@ti.com> Fixes: fa180eb448fa (PM / Runtime: Idle devices asynchronously after probe|release) Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Acked-by: Kevin Hilman <khilman@linaro.org> Acked-by: Ulf Hansson <ulf.hansson@linaro.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2013-11-28base: dma-coherent: add dma exact size alloc/release functionsVandana Salve
Add functions dma_alloc_from_coherent_attr and dma_release_from_coherent_attr. use attribute DMA_ATTR_ALLOC_EXACT_SIZE to allocate/release memory of exact size rather than order of 2^pages to reduce internal fragmentation bug 1380639 Change-Id: Ia7f560bf94960dfa9570f5be597f7f25b49150e1 Signed-off-by: Vandana Salve <vsalve@nvidia.com> Reviewed-on: http://git-master/r/333986 Reviewed-by: Hiroshi Doyu <hdoyu@nvidia.com> Tested-by: Hiroshi Doyu <hdoyu@nvidia.com>
2013-11-19PM / Domains: skip start/stop device in noirqPrashant Gaikwad
Bug 1401451 Change-Id: Ia7e907249223b20a6f2dea3c80207eb01163961d Signed-off-by: Prashant Gaikwad <pgaikwad@nvidia.com> Reviewed-on: http://git-master/r/332330 GVS: Gerrit_Virtual_Submit Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
2013-11-19PM / Domains: add flag to indicate if device need to savePrashant Gaikwad
Some devices are part of PM domain but do not need to save state when turning off power domain. If this flag is not used then it unnecessarily starts and stops device when turning off power domain. Bug 1401451 Change-Id: I05b2a0c3decb6396ac59e6d81b55fa43fce9c1dd Signed-off-by: Prashant Gaikwad <pgaikwad@nvidia.com> Reviewed-on: http://git-master/r/331190 Reviewed-by: Shridhar Rasal <srasal@nvidia.com> GVS: Gerrit_Virtual_Submit Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
2013-11-13drivers: cma: add dma_contiguous_stats()Vandana Salve
Added the dma_contiguous_stats() to get CMA stats such as base and size from the given dev bug 1279160 Change-Id: I066e35e7fda140f8613a3d4364464587d3bd251d Signed-off-by: Vandana Salve <vsalve@nvidia.com> Reviewed-on: http://git-master/r/328412 GVS: Gerrit_Virtual_Submit Reviewed-by: Krishna Reddy <vdumpa@nvidia.com> Tested-by: Krishna Reddy <vdumpa@nvidia.com>
2013-11-11PM/domain: Change print type for "latency exceeded" printBharat Nihalani
The print "Power-off latency exceeded" keeps coming in on a regular interval for various modules; don't see this to be valuable. Hence change the print type from pr_warning to pr_debug. Commit fd5dbe49ebb4ad600f22bfeb5b3bb0a33a651fed did the same for "Power-on latency exceeded". Missed to make the change for "Power-off latency exceeded" at that point; hence doing that now. Change-Id: I1bbbae00465855c6a20bdb9bb6c1a1a4346e1484 Signed-off-by: Bharat Nihalani <bnihalani@nvidia.com> Reviewed-on: http://git-master/r/328785
2013-11-07PM/domain: Change print type for "latency exceeded" printBharat Nihalani
The print "Power-on latency exceeded" keeps coming in on a regular interval for various modules; don't see this to be valuable. Hence change the print type from pr_warning to pr_debug. Change-Id: I544bb09993b6c13f5bd505f8580644d6e3002254 Signed-off-by: Bharat Nihalani <bnihalani@nvidia.com> Reviewed-on: http://git-master/r/327487 Reviewed-by: Prashant Gaikwad <pgaikwad@nvidia.com>
2013-10-31Merge tag 'v3.10.17' into dev-kernel-3.10Ajay Nandakumar
This is the 3.10.17 stable release Conflicts: drivers/usb/host/xhci.c Change-Id: I6bd3b15ff92a0b94568b9d02e9bb1036becfca20
2013-10-29PM / Domains: fix device runtime status printPrashant Gaikwad
Device runtime status is valid only if runtime PM is enabled or there is no error. Change-Id: Ie1175aaa54069ec655d669b83f5252f5d92c55b1 Signed-off-by: Prashant Gaikwad <pgaikwad@nvidia.com> Reviewed-on: http://git-master/r/304759 Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
2013-10-28PM / Domains: add accounting for power domainPrashant Gaikwad
Add accounting for generic power domain power on and power off time. It can get used by test applications to measure the power. Also, add debug fs to read these timestamps and domain status. /sys/kernel/debug/<domain_name>/status /sys/kernel/debug/<domain_name>/power_on_time /sys/kernel/debug/<domain_name>/power_off_time Bug 1254633 Change-Id: Id2f563bd08e1f6536ddfce429fd0131932b2b831 Signed-off-by: Prashant Gaikwad <pgaikwad@nvidia.com> Reviewed-on: http://git-master/r/304205 Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
2013-10-27base: power: reduce the default logs with wakeup_sourcesBharat Nihalani
/sys/kernel/debug/wakeup_sources by default gives information about various fields. This causes the logs to be cluttered and un-readable. Hence reduce the number of fields that get printed by default. Change-Id: Id0ffa19a4060b9aa7afce33250ad687e0774f24d Signed-off-by: Bharat Nihalani <bnihalani@nvidia.com> Reviewed-on: http://git-master/r/303876 Reviewed-by: Shridhar Rasal <srasal@nvidia.com> Reviewed-by: Sang-Hun Lee <sanlee@nvidia.com> Reviewed-by: Deepak Nibade <dnibade@nvidia.com> GVS: Gerrit_Virtual_Submit
2013-10-21PM / Domains: Check if device wants to wake upTerje Bergstrom
If a a define is marked as "NO_POWER_OFF", and it's suspended, wake it up. Bug 1364240 Change-Id: Ic51e69db01a88e2deefa4c3c0884d14ccc29272b Signed-off-by: Terje Bergstrom <tbergstrom@nvidia.com> Reviewed-on: http://git-master/r/288811
2013-10-21PM / QoS: Add notifier for flagsTerje Bergstrom
dev_pm_qos has a notifier for DEV_PM_QOS_LATENCY. Add a similar notifier for DEV_PM_QOS_FLAGS. Bug 1364240 Change-Id: Ica4c58708855938818a1e75896503b9023b96573 Signed-off-by: Terje Bergstrom <tbergstrom@nvidia.com> Reviewed-on: http://git-master/r/288810
2013-10-21PM / QoS: add dev_pm_qos_update_request_timeout()Terje Bergstrom
Add dev_pm_qos_update_request_timeout() that works in the same way as pm_qos_request_timeout(). Bug 1364240 Change-Id: I9da700df443f48099eac929055e9fe2db4c2f540 Signed-off-by: Terje Bergstrom <tbergstrom@nvidia.com> Reviewed-on: http://git-master/r/288808
2013-10-17arm: tegra: add more stats to power domain summaryPrashant Gaikwad
Add reference count and suspended time information to domain sumary debug fs. Change-Id: Ibac64825f44688b8a4d9f53d07de467a8e808c95 Signed-off-by: Prashant Gaikwad <pgaikwad@nvidia.com> Reviewed-on: http://git-master/r/299950 Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
2013-10-16PM / Core: add save and restore syscore opsPrashant Gaikwad
Add ops to save and restore system context when entering deep idle state. Bug 1254633 Change-Id: Iea36ed98544827ce73b50fcb2bf201c233baf2ca Signed-off-by: Prashant Gaikwad <pgaikwad@nvidia.com> Reviewed-on: http://git-master/r/299446 Reviewed-by: Automatic_Commit_Validation_User Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
2013-10-13base: dma-coherent: fix overflow issueKrishna Reddy
fix overflow issue during coherent memory free. Bug 1375907 Change-Id: Ib7164508acf9dd399d1028bd07c5b532c205aa02 Signed-off-by: Krishna Reddy <vdumpa@nvidia.com> Reviewed-on: http://git-master/r/283737 (cherry picked from commit 8cd3e197e00cb4402f0b6d01aa3ea7412baaf58d) Reviewed-on: http://git-master/r/294259 Reviewed-by: Automatic_Commit_Validation_User Reviewed-by: Vandana Salve <vsalve@nvidia.com>
2013-10-05driver core : Fix use after free of dev->parent in device_shutdownBenson Leung
commit f123db8e9d6c84c863cb3c44d17e61995dc984fb upstream. The put_device(dev) at the bottom of the loop of device_shutdown may result in the dev being cleaned up. In device_create_release, the dev is kfreed. However, device_shutdown attempts to use the dev pointer again after put_device by referring to dev->parent. Copy the parent pointer instead to avoid this condition. This bug was found on Chromium OS's chromeos-3.8, which is based on v3.8.11. See bug report : https://code.google.com/p/chromium/issues/detail?id=297842 This can easily be reproduced when shutting down with hidraw devices that report battery condition. Two examples are the HP Bluetooth Mouse X4000b and the Apple Magic Mouse. For example, with the magic mouse : The dev in question is "hidraw0" dev->parent is "magicmouse" In the course of the shutdown for this device, the input event cleanup calls a put on hidraw0, decrementing its reference count. When we finally get to put_device(dev) in device_shutdown, kobject_cleanup is called and device_create_release does kfree(dev). dev->parent is no longer valid, and we may crash in put_device(dev->parent). This change should be applied on any kernel with this change : d1c6c030fcec6f860d9bb6c632a3ebe62e28440b Signed-off-by: Benson Leung <bleung@chromium.org> Reviewed-by: Ming Lei <ming.lei@canonical.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2013-09-16drivers: dma-coherent: support coherent memory declaration with no kernel ↵Vandana Salve
mapping Add DMA_MEMORY_NOMAP flag to avoid creation of kernel virtual mapping during the declaration of DMA coherent memory. This would allow managing carveout memories via dma-coherent API with no impact on kernel VMALLOC space. bug 898152 Change-Id: I700fbfc83716516d15a97f1e18ad0b1a8154a0a9 Signed-off-by: Vandana Salve <vsalve@nvidia.com> Reviewed-on: http://git-master/r/267938 Reviewed-by: Krishna Reddy <vdumpa@nvidia.com>
generated by cgit v1.2.3 (git 2.0.4) at 2024-06-11 00:46:57 +0000