summaryrefslogtreecommitdiff
path: root/include/linux (follow)
Commit message (Collapse)AuthorAge
* Merge "char: msm_smd_pkt: Add snapshot of SMD packet driver"Linux Build Service Account2017-04-21
|\
| * char: msm_smd_pkt: Add snapshot of SMD packet driverDhoat Harpal2017-04-20
| | | | | | | | | | | | | | | | | | | | This snapshot is taken as of msm-3.18 'commit 7e1165aac628 ("Merge drivers: iio: bmi160: Enabled the buffering support for BMI160 Sensor")' CRs-Fixed: 2035593 Change-Id: I2951e77f226062d82e84a26fce6ab932b9685223 Signed-off-by: Dhoat Harpal <hdhoat@codeaurora.org>
* | Merge "Perf: arm64: disable irq for hotplug offline"Linux Build Service Account2017-04-21
|\ \
| * | Perf: arm64: disable irq for hotplug offlinePatrick Fay2017-04-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently the hotplug notifier calls cpu_pmu_enable_percpu_irq when a CPU comes online. The notifier doesn't have a corresponding call to cpu_pmu_disable_percpu_irq when the CPU goes offline. Change the code to follow what was done in 3.18 including tracking whether the PMU is active and the IRQ number in use. Change-Id: I1835fb543eb483713a30eb6c0ccd4e4a4b9908be Signed-off-by: Patrick Fay <pfay@codeaurora.org>
* | | Merge "iommu/arm-smmu: add support to configure IOVA range"Linux Build Service Account2017-04-20
|\ \ \
| * | | iommu/arm-smmu: add support to configure IOVA rangeLiam Mark2017-04-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Allow clients to specify the IOVA range for fastmap clients via the DOMAIN_ATTR_GEOMETRY domain attribute. Presently fastmap only allocates page tables for the IOVA range specified during the create mapping call. However clients may want to use IOVA addresses outside this range, such as for their calls to iommu_map. So allow clients to extend the available IOVA space by setting the DOMAIN_ATTR_GEOMETRY domain attribute's iommu_domain_geometry.aperture_start to the new start address of the IOVA space and by setting iommu_domain_geometry.aperture_end to the new end address of the IOVA space. The new IOVA space created by iommu_domain_geometry.aperture_start and iommu_domain_geometry.aperture_end will be a superset of the IOVA range which was created through the create mapping call. The DOMAIN_ATTR_GEOMETRY domain attribute can only be set before attaching. Calls to set the DOMAIN_ATTR_GEOMETRY domain attribute can only be used to extend the IOVA space, it cannot shrink the range. Note that extending the IOVA range will not change the range of IOVA addresses which will be available to the DMA APIs. Change-Id: Ib389e019a022d98417884002de08115fb0fc9384 Signed-off-by: Liam Mark <lmark@codeaurora.org>
* | | | Merge "ARM: dts: msm: Add PBS trigger support for OLEDB for PM660A"Linux Build Service Account2017-04-20
|\ \ \ \
| * | | | regulator: qpnp-oledb: Clear SPARE_CTL register during disableKiran Gunda2017-04-19
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | OLEDB_SPARE_CTL register bit is set by the PBS during the display enable and is used during the display suspend to trigger the PBS event. Hence, move clearing of the OLEDB_SPARE_CTL register to regulator disable. Also enable the force_pd_ctl only for DRAX-A revisions <=2.0. Change-Id: I339cefc91f94f772bc4f84e85f2471e1a73e4aed Signed-off-by: Kiran Gunda <kgunda@codeaurora.org>
* | | | Merge "regulator: qpnp-labibb: Handle LAB short circuit(SC) detection"Linux Build Service Account2017-04-19
|\ \ \ \
| * | | | regulator: qpnp-labibb: Handle LAB short circuit(SC) detectionKiran Gunda2017-04-19
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On certain PMICs, there is no short circuit (SC) detection available in LAB module. Add support to detect it manually and disable LAB/IBB module upon SC detection. In addition, notify it to OLEDB driver to disable OLEDB module. Change-Id: I2a9dc5b1ae8ece45c85b3992026c7f389fd4d135 Signed-off-by: Kiran Gunda <kgunda@codeaurora.org>
* | | | Merge "leds: qpnp-flash-v2: Enable charger mitigation"Linux Build Service Account2017-04-19
|\ \ \ \
| * | | | leds: qpnp-flash-v2: Enable charger mitigationAnkit Sharma2017-04-18
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When the charger mitigation is configured based on SW, enable it locally when the total brightness (or current level) of all torch/flash LED devices is greater than 1 A. CRs-Fixed: 2011199 Change-Id: I8336b3201f0780855c3dc3633179c398b9f62162 Signed-off-by: Ankit Sharma <ansharma@codeaurora.org>
* | | | Merge "mm: separate out the invocation of lowmemorykiller shrinker"Linux Build Service Account2017-04-18
|\ \ \ \ | |/ / / |/| | |
| * | | mm: separate out the invocation of lowmemorykiller shrinkerVinayak Menon2017-04-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The commit '6b4f77 (mm: vmscan: invoke slab shrinkers from shrink_zone())' fixed the invocation of shrinkers but resulted in lowmemorykiller shrinker being called more. Reduce the number of lowmemorykiller shrinker invocations by separating out the lowmemorykiller shrinker from shrink_slab. This will make lowmemorykiller invoked only once for all zones reclaimed in the direct reclaim path, and once for each zone in the kswap path. As a consequence the eligible pages passed to shrink_slab_lmk is now the reclaimable pages of all zones. Reducing the number of lowmemorykiller invocations reduces the unnecessary time spent in lowmemorykiller and thus contention or failures on lowmemorykiller's scan_mutex. Change-Id: Iaabb9e441711f1dc804980b5853b64b3f214698d Signed-off-by: Vinayak Menon <vinmenon@codeaurora.org>
* | | | Merge "mm: allow page poisoning to be enabled by default."Linux Build Service Account2017-04-17
|\ \ \ \ | |/ / / |/| | |
| * | | mm: enable page poisoning early at bootVinayak Menon2017-04-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On SPARSEMEM systems page poisoning is enabled after buddy is up, because of the dependency on page extension init. This causes the pages released by free_all_bootmem not to be poisoned. This either delays or misses the identification of some issues because the pages have to undergo another cycle of alloc-free-alloc for any corruption to be detected. Enable page poisoning early by getting rid of the PAGE_EXT_DEBUG_POISON flag. Since all the free pages will now be poisoned, the flag need not be verified before checking the poison during an alloc. Link: http://lkml.kernel.org/r/1490358246-11001-1-git-send-email-vinmenon@codeaurora.org Acked-by: Laura Abbott <labbott@redhat.com> Tested-by: Laura Abbott <labbott@redhat.com> Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com> Cc: Michal Hocko <mhocko@suse.com> Cc: Akinobu Mita <akinobu.mita@gmail.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> [vinmenon@codeaurora.org: resolve trivial merge conflicts. Remove the redundant free pages RO feature from the page_poison.c file which is the reason for conflicts + squash the addendum commit 40961ef8d65f51093bc94de110b97b590b6b9275 ('mm-enable-page-poisoning-early-at-boot-v2')] Git-commit: c5b7cd344fd6341e6db79e55c0f1f4d1d9c67a7e Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git Change-Id: I1bb1f99d3a2e1135131911905e0916c837ba9d8a Signed-off-by: Vinayak Menon <vinmenon@codeaurora.org>
| * | | mm/page_poisoning.c: allow for zero poisoningLaura Abbott2017-04-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | By default, page poisoning uses a poison value (0xaa) on free. If this is changed to 0, the page is not only sanitized but zeroing on alloc with __GFP_ZERO can be skipped as well. The tradeoff is that detecting corruption from the poisoning is harder to detect. This feature also cannot be used with hibernation since pages are not guaranteed to be zeroed after hibernation. Credit to Grsecurity/PaX team for inspiring this work Change-Id: If7116e6bff246abbafc38bdfeb3601d3ea063ad2 Signed-off-by: Laura Abbott <labbott@fedoraproject.org> Acked-by: Rafael J. Wysocki <rjw@rjwysocki.net> Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com> Cc: Vlastimil Babka <vbabka@suse.cz> Cc: Michal Hocko <mhocko@suse.com> Cc: Kees Cook <keescook@chromium.org> Cc: Mathias Krause <minipli@googlemail.com> Cc: Dave Hansen <dave.hansen@intel.com> Cc: Jianyu Zhan <nasa4836@gmail.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Git-commit: 1414c7f4f7d72d138fff35f00151d15749b5beda Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git Signed-off-by: Vinayak Menon <vinmenon@codeaurora.org>
| * | | mm/page_poison.c: enable PAGE_POISONING as a separate optionLaura Abbott2017-04-14
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Page poisoning is currently set up as a feature if architectures don't have architecture debug page_alloc to allow unmapping of pages. It has uses apart from that though. Clearing of the pages on free provides an increase in security as it helps to limit the risk of information leaks. Allow page poisoning to be enabled as a separate option independent of kernel_map pages since the two features do separate work. Because of how hiberanation is implemented, the checks on alloc cannot occur if hibernation is enabled. The runtime alloc checks can also be enabled with an option when !HIBERNATION. Credit to Grsecurity/PaX team for inspiring this work Change-Id: I77a36f844ddae54695089c98a97bf0a6e226a025 Signed-off-by: Laura Abbott <labbott@fedoraproject.org> Cc: Rafael J. Wysocki <rjw@rjwysocki.net> Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com> Cc: Vlastimil Babka <vbabka@suse.cz> Cc: Michal Hocko <mhocko@suse.com> Cc: Kees Cook <keescook@chromium.org> Cc: Mathias Krause <minipli@googlemail.com> Cc: Dave Hansen <dave.hansen@intel.com> Cc: Jianyu Zhan <nasa4836@gmail.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Git-commit: 8823b1dbc05fab1a8bec275eeae4709257c2661d Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git Signed-off-by: Vinayak Menon <vinmenon@codeaurora.org>
* | | Merge "usb: gadget: ccid: Fix data types of header structures"Linux Build Service Account2017-04-14
|\ \ \ | |/ / |/| |
| * | usb: gadget: ccid: Fix data types of header structuresManu Gautam2017-03-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Replace unsigned long with __u32 as 4 bytes is the length of field where as unsigned long could be 8 bytes on 64 bit machine. Also, replace short and char with u16 and u8 respectively for better readability. Change-Id: I8637f6b32d56d90c01b4453b4677f40d5b865bf6 Signed-off-by: Manu Gautam <mgautam@codeaurora.org>
* | | Merge "drivers/video: Add new aspect ratios for HDMI 2.0"Linux Build Service Account2017-04-12
|\ \ \
| * | | drivers/video: Add new aspect ratios for HDMI 2.0Shashank Sharma2017-04-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | HDMI 2.0/CEA-861-F introduces two new aspect ratios: - 64:27 - 256:135 This patch adds enumeration for the new aspect ratios in the existing aspect ratio list. V2: rebase V3: rebase V4: Added r-b from Jose, Ack by Tomi Change-Id: Ie90d43e4088a7c19274fe2aa25aa40d38683f584 Signed-off-by: Shashank Sharma <shashank.sharma@intel.com> Reviewed-by: Sean Paul <seanpaul@chromium.org> Reviewed-by: Jose Abreu <Jose.Abreu@synopsys.com> Acked-by: Tomi Valkeinen <tomi.valkeinen@ti.com> Cc: Daniel Vetter <daniel.vetter@ffwll.ch> Cc: Emil Velikov <emil.l.velikov@gmail.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Git-commit: a6e78b3e1406575323b30b65890ee3c29930fb27 Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git Signed-off-by: Abhinav Kumar <abhinavk@codeaurora.org>
| * | | drm: edid: HDMI 2.0 HF-VSDB block parsingJose Abreu2017-04-07
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds parsing for HDMI 2.0 'HDMI Forum Vendor Specific Data Block'. This block is present in some HDMI 2.0 EDID's and gives information about scrambling support, SCDC, 3D Views, and others. Parsed parameters are stored in drm_connector structure. Change-Id: I018cfefea2fd3827d5f83c8e5717ebd95e497519 Signed-off-by: Jose Abreu <joabreu@synopsys.com> Cc: Carlos Palminha <palminha@synopsys.com> Cc: David Airlie <airlied@linux.ie> Cc: Daniel Vetter <daniel.vetter@intel.com> Cc: dri-devel@lists.freedesktop.org Cc: linux-kernel@vger.kernel.org Patch-mainline: dri-devel @ 10 Aug 2016 16:29 Signed-off-by: Jin Li <jinl@codeaurora.org> Signed-off-by: Abhinav Kumar <abhinavk@codeaurora.org>
* | | | Merge "cfg80211: Add Fast Initial Link Setup (FILS) auth algs"Linux Build Service Account2017-04-11
|\ \ \ \
| * | | | cfg80211: Add Fast Initial Link Setup (FILS) auth algsJouni Malinen2017-04-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This defines authentication algorithms for FILS (IEEE 802.11ai). Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com> Git-commit: 631810603a20874554b2f17adf42b72d0f15eda5 Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git CRs-Fixed: 2028536 Change-Id: I530913c84f2c3e678e83144ac474195184f4dd3b Signed-off-by: Vidyullatha Kanchanapally <vidyullatha@codeaurora.org>
* | | | | Merge "sound: usb: Populate tunnel mode response struct for BADD devices"Linux Build Service Account2017-04-11
|\ \ \ \ \
| * | | | | sound: usb: Add support for parsing AudioControl intf for BADD devicesAjay Agarwal2017-04-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | BADD 3.0 devices support three types of topologies; Basic I/P, Basic O/P, and BASIC I/P. Accordingly, various units and terminals have to be parsed which are not exposed by the device and host must be able to figure out various class-specific descriptors based on the profile ID of the device. This patch adds this logic to build various units and terminals of the AudioControl interface of a BADD device. Change-Id: Ib52f884133cdf6e0ec95f49095c14f7d005a5356 Signed-off-by: Ajay Agarwal <ajaya@codeaurora.org>
| * | | | | sound: usb: Add support for parsing AudioStreaming intf for BADD devicesAjay Agarwal2017-04-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | BADD(Basic Audio Device Definition) is a subset of UAC3 specifications. It defines standard profiles which provide specific attributes of class descriptors. BADD audio device provides profile id and BADD supporting host will infer attributes from profile-id. Currently USB Audio Host driver has support for UAC1 and UAC2 devices. To handle BADD 3.0 devices, AudioControl and AudioStreaming Interfaces have to be properly parsed. The Host has to derive all class-specific information based on the profile ID that the device exposes. Add support for parsing the AudioStreaming interfaces exposed by the device. Change-Id: I726bbb735708fe8e395011c7228a73d5f65c092d Signed-off-by: Ajay Agarwal <ajaya@codeaurora.org>
* | | | | | Merge "smb138x: introduce support for smb1355"Linux Build Service Account2017-04-11
|\ \ \ \ \ \ | |_|/ / / / |/| | | | |
| * | | | | qpnp-revid: add smb1355 definitionsAbhijeet Dharmapurikar2017-04-07
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add revision definitions for smb1355 i2c charger chip. Change-Id: I60429c6462a2faa70df71d3440afe696a13fcab0 Signed-off-by: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
* | | | | | Merge "mhi: core: Enable mhi_dev_net interface channels"Linux Build Service Account2017-04-07
|\ \ \ \ \ \ | |/ / / / / |/| | | | |
| * | | | | mhi: core: Enable mhi_dev_net interface channelsPrasad Malisetty2017-04-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Enable 46, 47 channels for mhi_dev_net interface. mhi_dev_net client uses read and write channels to communicate mhi host rmnet interface over PCIe link. CRs-Fixed: 2029099 Change-Id: Ifdda4b1a139751bd2b36143d9125068f34fec9e5 Signed-off-by: Prasad Malisetty <prasadm@codeaurora.org>
* | | | | | Merge "sched/debug: Make the "Preemption disabled at ..." message more useful"Linux Build Service Account2017-04-06
|\ \ \ \ \ \ | |_|_|/ / / |/| | | | |
| * | | | | sched/debug: Make the "Preemption disabled at ..." message more usefulVegard Nossum2017-03-30
| | |_|/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This message is currently really useless since it always prints a value that comes from the printk() we just did, e.g.: BUG: sleeping function called from invalid context at mm/slab.h:388 in_atomic(): 0, irqs_disabled(): 0, pid: 31996, name: trinity-c1 Preemption disabled at:[<ffffffff8119db33>] down_trylock+0x13/0x80 BUG: sleeping function called from invalid context at include/linux/freezer.h:56 in_atomic(): 0, irqs_disabled(): 0, pid: 31996, name: trinity-c1 Preemption disabled at:[<ffffffff811aaa37>] console_unlock+0x2f7/0x930 Here, both down_trylock() and console_unlock() is somewhere in the printk() path. We should save the value before calling printk() and use the saved value instead. That immediately reveals the offending callsite: BUG: sleeping function called from invalid context at mm/slab.h:388 in_atomic(): 0, irqs_disabled(): 0, pid: 14971, name: trinity-c2 Preemption disabled at:[<ffffffff819bcd46>] rhashtable_walk_start+0x46/0x150 Bug report: http://marc.info/?l=linux-netdev&m=146925979821849&w=2 Change-Id: I5b08294385a2ac625dbf28d1f18ffd164aedabe0 Signed-off-by: Vegard Nossum <vegard.nossum@oracle.com> Cc: Andrew Morton <akpm@linux-foundation.org> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Mike Galbraith <efault@gmx.de> Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Rusty Russel <rusty@rustcorp.com.au> Cc: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Ingo Molnar <mingo@kernel.org> [mkhaja@codeaurora.org: Fix trivial merge conflict] Git-commit: d1c6d149cf04d6c7c3c3ebf4b66c82500cbcf6e1 Git-repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git Signed-off-by: Mohammed Khajapasha <mkhaja@codeaurora.org>
* | | | | Merge "power_supply: add HW_CURRENT_MAX power_supply property"Linux Build Service Account2017-04-05
|\ \ \ \ \
| * | | | | power_supply: add HW_CURRENT_MAX power_supply propertyAshay Jaiswal2017-04-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add support for HW_CURRENT_MAX property which returns maximum input current that can be set for an adapter. This property will be specifically used by parallel charger to cast an initial ICL vote. CRs-Fixed: 2014572 Change-Id: I49e80e6b25f40791d9035bc1567fdf881914b1e8 Signed-off-by: Ashay Jaiswal <ashayj@codeaurora.org> Signed-off-by: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
* | | | | | Merge "ARM: dts: msm: enable SDR104 workaround for MSM8998"Linux Build Service Account2017-04-05
|\ \ \ \ \ \ | |_|_|_|_|/ |/| | | | |
| * | | | | mmc: sd: reduce the bus speed in case of multiple CRC errors in SDR104Asutosh Das2017-04-03
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | UHS-I SD cards support SDR104 mode which runs the SD card interface clock upto 208 MHz. But we may see repeated CRC errors in SDR104 with some SDCC controllers. If this happens, this change would reinit the card to lower speed (SDR50) hoping that CRC error rate would reduce at lower clock speed (100MHz for SDR50). Change-Id: I140d29fdf500bb89881a0f2c1f768fe0c5afa9d5 Signed-off-by: Asutosh Das <asutoshd@codeaurora.org> Signed-off-by: Subhash Jadavani <subhashj@codeaurora.org>
| * | | | | mmc: sdhci-msm: add SDR104 CRC workaround enablement controlSubhash Jadavani2017-04-03
| | |_|/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On Certain chipsets, SDR104 mode might be unstable causing CRC error on the interface. So we need a workaround which would skip printing register dumps on CRC errors and also downgrade bus speed mode to SDR50/DDR50 in case of continuous CRC errors. This patch adds "qcom,sdr104-wa" property to enable this workaround if required. Change-Id: I626d8ef45a97e8e6558e7f20be496de1f5a2a438 Signed-off-by: Subhash Jadavani <subhashj@codeaurora.org>
* | | | | Merge "mmc: core: Remove unused variable cached_ext_csd"Linux Build Service Account2017-04-04
|\ \ \ \ \
| * | | | | mmc: core: Remove unused variable cached_ext_csdSayali Lokhande2017-04-04
| | |/ / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There is one variable defined in mmc_card, which is not being used anywhere. Also it is wrongly being freed from mmc_remove_card and causing "double kfree" related issues. To handle this, remove unused cached_ext_csd variable. Change-Id: I75f376ec787a46a2a16c38f88f444bd8ff9c86c4 Signed-off-by: Sayali Lokhande <sayalil@codeaurora.org>
* | | | | Merge "mhi: core: add support for subsystem restart and shutdown"Linux Build Service Account2017-04-04
|\ \ \ \ \ | |/ / / / |/| | | |
| * | | | mhi: core: add support for subsystem restart and shutdownSujeev Dias2017-03-31
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add support for subsystem restart and shutdown processing for slave mode and master mode. CRs-Fixed: 1097560 Change-Id: I8c60605d202d38a7a8f8fb587a179f95ec402692 Signed-off-by: Sujeev Dias <sdias@codeaurora.org>
* | | | Merge "regulator: qpnp-lcdb: Add a WA to toggle SC before module_enable"Linux Build Service Account2017-04-03
|\ \ \ \
| * | | | include: qpnp-revid: Add PM660L version infoAnirudh Ghayal2017-04-01
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | Add PM660L v1.1 version macros. Change-Id: I14c3f2110efc474686df488748b0a671f34ced90 Signed-off-by: Anirudh Ghayal <aghayal@codeaurora.org>
* | | | Merge "input: touchscreen: remove synaptics v2.6 touch driver"Linux Build Service Account2017-04-03
|\ \ \ \
| * | | | input: touchscreen: remove synaptics v2.6 touch driverShantanu Jain2017-03-31
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | Remove synaptics v2.6 touch driver from the kernel code as it has never been used in any of the recent platforms. Change-Id: Ibf14dec548a180e517d9b41098af642577c4328b Signed-off-by: Shantanu Jain <shjain@codeaurora.org>
* | | | Merge "msm: mdss: make hpd call asynchronous for HDMI in certain cases"Linux Build Service Account2017-03-31
|\ \ \ \
| * | | | msm: mdss: make hpd call asynchronous for HDMI in certain casesRay Zhang2017-03-24
| | |/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In some cases the hpd call cannot be blocked. For example, in case of framework restart, both display and audio HALs are not available, so nobody will notify and unblock hpd call. Another case is continuous splash in which unblank is delayed till the first display kickoff, so hpd cannot blocking wait for such a late notification. Change-Id: I6ed58c3ac35efdaeac2e73d36d78b7fd64a74f42 Signed-off-by: Ray Zhang <rayz@codeaurora.org>
* | | | Merge "diag: Add support for header untagging"Linux Build Service Account2017-03-31
|\ \ \ \ | |_|/ / |/| | |