| Age | Commit message (Collapse) | Author |
|---|
|
|
|
These are all driver changes needed for disablement of
CONFIG_CC_OPTIMIZE_FOR_SIZE. CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE
is enabled by default once CONFIG_CC_OPTIMIZE_FOR_SIZE is disabled.
Change-Id: Ia46a1f24e8a082a29ea6151e41e6d3a85a05fd4f
Signed-off-by: Prasad Sodagudi <psodagud@codeaurora.org>
Signed-off-by: Sridhar Parasuram <sridhar@codeaurora.org>
|
|
|
|
|
|
Fix use of uninitialized variable.
CRs-Fixed: 2050786
Change-Id: I3e0ac770df89347b878c9fe6eeaf5e4d8d53537c
Signed-off-by: Ankit Sharma <ansharma@codeaurora.org>
|
|
* origin/tmp-285c137:
Linux 4.4.68
block: get rid of blk_integrity_revalidate()
drm/ttm: fix use-after-free races in vm fault handling
f2fs: sanity check segment count
bnxt_en: allocate enough space for ->ntp_fltr_bmap
ipv6: reorder ip6_route_dev_notifier after ipv6_dev_notf
ipv6: initialize route null entry in addrconf_init()
rtnetlink: NUL-terminate IFLA_PHYS_PORT_NAME string
ipv4, ipv6: ensure raw socket message is big enough to hold an IP header
tcp: do not inherit fastopen_req from parent
tcp: fix wraparound issue in tcp_lp
bpf, arm64: fix jit branch offset related to ldimm64
tcp: do not underestimate skb->truesize in tcp_trim_head()
ALSA: hda - Fix deadlock of controller device lock at unbinding
staging: emxx_udc: remove incorrect __init annotations
staging: wlan-ng: add missing byte order conversion
brcmfmac: Make skb header writable before use
brcmfmac: Ensure pointer correctly set if skb data location changes
MIPS: R2-on-R6 MULTU/MADDU/MSUBU emulation bugfix
scsi: mac_scsi: Fix MAC_SCSI=m option when SCSI=m
serial: 8250_omap: Fix probe and remove for PM runtime
phy: qcom-usb-hs: Add depends on EXTCON
USB: serial: io_edgeport: fix descriptor error handling
USB: serial: mct_u232: fix modem-status error handling
USB: serial: quatech2: fix control-message error handling
USB: serial: ftdi_sio: fix latency-timer error handling
USB: serial: ark3116: fix open error handling
USB: serial: ti_usb_3410_5052: fix control-message error handling
USB: serial: io_edgeport: fix epic-descriptor handling
USB: serial: ssu100: fix control-message error handling
USB: serial: digi_acceleport: fix incomplete rx sanity check
USB: serial: keyspan_pda: fix receive sanity checks
usb: chipidea: Handle extcon events properly
usb: chipidea: Only read/write OTGSC from one place
usb: host: ohci-exynos: Decrese node refcount on exynos_ehci_get_phy() error paths
usb: host: ehci-exynos: Decrese node refcount on exynos_ehci_get_phy() error paths
KVM: nVMX: do not leak PML full vmexit to L1
KVM: nVMX: initialize PML fields in vmcs02
Revert "KVM: nested VMX: disable perf cpuid reporting"
x86/platform/intel-mid: Correct MSI IRQ line for watchdog device
kprobes/x86: Fix kernel panic when certain exception-handling addresses are probed
clk: Make x86/ conditional on CONFIG_COMMON_CLK
x86/pci-calgary: Fix iommu_free() comparison of unsigned expression >= 0
x86/ioapic: Restore IO-APIC irq_chip retrigger callback
mwifiex: Avoid skipping WEP key deletion for AP
mwifiex: remove redundant dma padding in AMSDU
mwifiex: debugfs: Fix (sometimes) off-by-1 SSID print
ARM: OMAP5 / DRA7: Fix HYP mode boot for thumb2 build
leds: ktd2692: avoid harmless maybe-uninitialized warning
power: supply: bq24190_charger: Handle fault before status on interrupt
power: supply: bq24190_charger: Don't read fault register outside irq_handle_thread()
power: supply: bq24190_charger: Call power_supply_changed() for relevant component
power: supply: bq24190_charger: Install irq_handler_thread() at end of probe()
power: supply: bq24190_charger: Call set_mode_host() on pm_resume()
power: supply: bq24190_charger: Fix irq trigger to IRQF_TRIGGER_FALLING
powerpc/powernv: Fix opal_exit tracepoint opcode
cpupower: Fix turbo frequency reporting for pre-Sandy Bridge cores
ARM: 8452/3: PJ4: make coprocessor access sequences buildable in Thumb2 mode
9p: fix a potential acl leak
ANDROID: android-base.cfg: remove spurious CONFIG_MODULES line
ANDROID: memory_state_time: fix undefined behavior with missing DT properties
ANDROID: rfkill: fix unused function warning
ANDROID: make PF_KEY SHA256 use RFC-compliant truncation.
ANDROID: sdcardfs: fix sdcardfs_destroy_inode for the inode RCU approach
ANDROID: android-base.cfg: remove NETFILTER_XT_MATCH_QUOTA2_LOG
ANDROID: sdcardfs: Don't iput if we didn't igrab
ANDROID: Add untag hacks to inet_release function
Change-Id: I6d750f8bb186774ff9630beeb0ed8e680af26231
Signed-off-by: Kyle Yan <kyan@codeaurora.org>
|
|
commit cbe99c538d1776009e8710755bb6e726f7fffa9b upstream.
gcc gets confused about the control flow in ktd2692_parse_dt(), causing
it to warn about what seems like a potential bug:
drivers/leds/leds-ktd2692.c: In function 'ktd2692_probe':
drivers/leds/leds-ktd2692.c:244:15: error: '*((void *)&led_cfg+8)' may be used uninitialized in this function [-Werror=maybe-uninitialized]
drivers/leds/leds-ktd2692.c:225:7: error: 'led_cfg.flash_max_microamp' may be used uninitialized in this function [-Werror=maybe-uninitialized]
drivers/leds/leds-ktd2692.c:232:3: error: 'led_cfg.movie_max_microamp' may be used uninitialized in this function [-Werror=maybe-uninitialized]
The code is fine, and slightly reworking it in an equivalent way lets
gcc figure that out too, which gets rid of the warning.
Fixes: 77e7915b15bb ("leds: ktd2692: Add missing of_node_put")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Acked-by: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Jacek Anaszewski <jacek.anaszewski@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
|
Flash LED3 can be configured for LPG strobe in addition to the
existing HW or SW strobe types. LPG strobe works the same way
as HW strobe except the strobing is controlled by LPG output
instead of a GPIO. To accommodate this, device tree property
"qcom,hw-strobe-sel" got renamed to "qcom,strobe-sel".
While at it, configure hardware strobe option only when the
option is specified through device tree.
Change-Id: I9351d7b7cd8c57ff7707a4ada6c5bdfa42772390
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
|
|
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>
|
|
Change minimum current configuration from hard coded value to
based on current resolution step.
CRs-Fixed: 2014773
Change-Id: I69d6f2af032495a263d3d41a0569efe0acf0ce72
Signed-off-by: Ankit Sharma <ansharma@codeaurora.org>
|
|
Currently pinctrl is obtained after it is used to obtain
strobe_enable and strobe_disable states. This is incorrect and
needs to be fixed. Also, when the switch device is disabled, the
pinctrl configuration for GPIO that drives the LED output is
selected only when the brightness or current is set to a non-zero
value in flash device.
To keep it simple, move the pinctrl configuration for GPIO that
drives the LED output (e.g. flash LED3) to the switch device so
that both flash and torch device need not have to control it.
Also, fix the pinctrl configuration for GPIOs that are used to
drive flash LED3 output on both 8998 and 660 for functional
correctness.
Change-Id: If6ec27dd39fd750b6d4311a5e370020961f30e08
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
|
|
An out of bounds access is attempted to calculate code for
iclamp_low_ma and iclamp_mid_ma for LED3. Use the right index in
flash_node pointer to fix it.
When an error is found during probe especially before registering
a flash LED class device, unregistering flash LED class devices
is made on a flash LED class device that is not registered yet.
Fix it.
Change-Id: I2f6650eb24ecbece473abfe18a9a2e26c62c1253
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
|
|
pwm_free() is called in the driver incorrectly when trying to disable PWM
channel while changing the configuration. pwm_free() checks PWMF_REQUESTED
flag before calling disable() hook. The driver doesn't call pwm_request()
but only calls of_pwm_get() at the probe to get the flag once. The Flag
will be cleared when pwm_free() is called for the first time and calling it
afterwards will simply bailout not calling disable().
Replace pwm_free() with pwm_disable(), this won't cause any issue because
the PWM channel is considered statically allocated to the led devices from
hardware perspective and no need to free it in the driver.
While at it, free the PWM device if any errors when getting PWM
configuration.
CRs-Fixed: 2014600
Change-Id: I373d2a1ac83232ce94933c287b4ebe3f23519c83
Signed-off-by: Fenglin Wu <fenglinw@codeaurora.org>
|
|
|
|
|
|
As per the hardware recommendation, keep PSM disabled 10 ms after
WLED module is enabled. Enable PSM back when the module is
disabled. This is to ensure that PFM mode is operational without
the precedence from PSM. Make this configurable through a device
tree property.
Change-Id: Ic6be160a88be40e94a4a0798646b8aa3f169ab49
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
|
|
If there is an OVP event happened in the bootloader and the
interrupt is not handled before, then as soon as the WLED
module is enabled, fault interrupt can fire. This is seen
sometimes during bootup. This is harmless as such and cannot
be stopped completely. However, it would be good to keep the
OVP fault interrupt disabled at the startup. When WLED module
is enabled again, it will get enabled anyways after ~10 ms.
While at it, print the error message in OVP fault interrupt
handler only when the fault status is set.
Change-Id: I0759c87137a52a8872b37d126e71c13f76d10e05
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
|
|
leds-qpnp-flash driver is not supported anymore. Remove it.
Change-Id: Ie2f570bad8171c460b8167f140d71c052ada2b17
Signed-off-by: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
|
|
|
|
There is a possible race condition when debugfs files are concurrently
accessed by multiple threads. Fix this.
CRs-Fixed: 1109420, 1109326
Change-Id: I19e9107079ac8d039b12a37ae612727f824552d4
Signed-off-by: Ankit Sharma <ansharma@codeaurora.org>
|
|
As per the hardware recommendation, a delay of 500 us is needed
after LMH mitigation is enabled by software and before the flash
LED is strobed. Add it.
Change-Id: Ib70efbb7267510ffb9d95c4aba8566bf6e777c0f
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
|
|
Correct warnings flagged by checkpatch. In particular, modify
the following:
- Add 'const' to the type of a struct of_device_id variable.
- Use octal file permissions instead of symbolic.
- Replace sscanf() for a single integer with kstrtoint().
- Update the LEDS_QPNP_WLED Kconfig entry to use the name
'Qualcomm Technologies, Inc.'
- Expand the description of the LEDS_QPNP_WLED config
option.
Change-Id: I848983cd7beeb1a41191aba94fc8b33ce45fb2bc
Signed-off-by: David Collins <collinsd@codeaurora.org>
|
|
Correct warnings flagged by checkpatch. In particular, modify
the following:
- Use octal file permissions instead of symbolic.
- Add a comment explaining the strncmp() usage.
- Update the LEDS_QPNP_FLASH_V2 Kconfig entry to use the
name 'Qualcomm Technologies, Inc.'
- Expand the description of the LEDS_QPNP_FLASH_V2 config
option.
Change-Id: I18f49e3c56bfc7ad6770f4f9dc508ad8331af0d4
Signed-off-by: David Collins <collinsd@codeaurora.org>
|
|
Correct warnings flagged by checkpatch. In particular, modify
the following:
- Add 'const' to the type of a struct of_device_id variable.
- Use octal file permissions instead of symbolic.
- Remove unnecessary out-of-memory error messages.
- Use variable name in sizeof() for kzalloc() calls.
- Restructure conditionals to avoid else after return.
- Remove 'return' from the end of void functions.
- Correct the format of block comments.
- Correct the spelling of 'cannot'.
- Update the LEDS_QPNP_FLASH Kconfig entry to use the name
'Qualcomm Technologies, Inc.'
- Expand the description of the LEDS_QPNP_FLASH config
option.
Change-Id: I342fe2d0e6a027c87cd17a3697529b422ec49ab6
Signed-off-by: David Collins <collinsd@codeaurora.org>
|
|
Correct warnings flagged by checkpatch. In particular, modify
the following:
- Add 'const' to the type of a struct of_device_id variable.
- Remove unnecessary out-of-memory error messages.
- Restructure conditionals to avoid else after return.
- Replace kzalloc() with kcalloc() for arrays.
- Replace strncmp() with strcmp().
- Join strings that are wrapped across two lines.
- Correct the format of block comments.
- Remove 'return' from the end of void functions.
- Remove unnecessary parentheses.
- Remove unnecessary line continuations.
- Call usleep_range() with max > min.
- Update the LEDS_QPNP Kconfig entry and the device tree
documentation to use the name: 'Qualcomm Technologies, Inc.'
- Expand the description of the LEDS_QPNP config option.
- Correct the spelling of 'controlled'.
Change-Id: Id29de0da18aa1ce75a0c7604b8c0ecd1633fcaf3
Signed-off-by: David Collins <collinsd@codeaurora.org>
|
|
Remove the duplicate Kconfig options for LEDS_QPNP,
LEDS_QPNP_FLASH, and LEDS_QPNP_WLED. Also fix the help text
for LEDS_POWERNV which was associated with LEDS_QPNP_WLED.
Change-Id: I11cc6b30280c4e2e1f33720308353ba746c5612a
Signed-off-by: David Collins <collinsd@codeaurora.org>
|
|
qpnp_flash_led_prepare() is a global function used by clients
like camera flash driver. Add a check to validate the trigger
pointer before using it to obtain LED class device.
Change-Id: I72c0690c13629cb3dd2ef6b9fd084835e58aa410
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
|
|
LED_KEEP_TRIGGER flag needs to be set on switch devices so that
the trigger will not be removed when the brightness is set to 0.
Without this, when an user sets brightness to 0 on switch device
and try to use camera flash, qpnp_flash_led_prepare() will fail
which in turn fails the camera flash operation.
Change-Id: I521bc6c6750bafc742dccac90ef585bc250b0270
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
|
|
Commit 0013b23d66a2768f5babbb0ea9f03ab067a990d8 ("leds: disable
triggers on brightness set") removes the trigger on a LED class
device when brightness is set to 0. However, there are some LED
class devices which needs the trigger not to be removed. In an
use case like camera flash, camera flash driver passes in a
trigger device to LED class driver. If the trigger is removed
when the brightness is set to 0, this will affect the clients
using those triggers. Hence add a flag to always keep the trigger
even when brightness is set to 0.
Change-Id: Icec1380b297bc87058ea5024ef690ee3c1bed9e3
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
|
|
Update the code name from msmfalcon/apqfalcon to sdm660/sda660.
As part of this, update the filename containing "falcon" and
files content containing "falcon".
Change-Id: Iec85862251b9e1b4dcc8bdce8b214ce87c0049bc
Signed-off-by: Neeraj Upadhyay <neeraju@codeaurora.org>
|
|
|
|
Update WLED configuration to enable HVG_PULL_SWITCH bit to
temporarily pull up Hvgate with larger switch(for pm2falcon)
and enable DEBOUNCE_BYPASS_ILIM bit to remove debouncing for
Ilim. This guarantee stable operation of WLED.
CRs-Fixed: 1102641
Change-Id: I39a1266f4158e71238f374b6cba49e1a8c2b1a3b
Signed-off-by: ansharma <ansharma@codeaurora.org>
|
|
In certain PMICs, when WLED is configured for AMOLED panels, AVDD
default voltage configured for SWIRE mode has to be reconfigured
every time WLED module is disabled and enabled. Otherwise, AVDD
voltage can stay at the previous voltage level configured through
SWIRE pulses. Add support for it.
CRs-Fixed: 1071936
Change-Id: I938ce65f42eebe31be27151281d7e8502ba29f6e
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
|
|
Sometimes, OVP fault interrupt fires as soon as WLED module is
enabled. This does not really represent a harmful event. Hence
add support to enable OVP fault interrupt 10 mS after enabling
WLED module so that the soft start is completed. Keep the OVP
fault interrupt disabled when the module is disabled.
While at it, print the fault status from both OVP and short
circuit interrupt handlers which might be useful.
Change-Id: If3c264c6e3a2bf4b23069c0960b354f7967ecb4c
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
|
|
Fix the order of parameters passed into read/write APIs of WLED
driver to make it more readable. Fix the masked_write API to
directly use regmap API so that it can be protected properly to
avoid racing with secure writes.
While at it, remove the comments for variables that were removed
a while ago.
Change-Id: Ib372d3272550973fd98992f28b3b9bf7e5eb7f0f
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
|
|
Update the code name from msmcobalt to msm8998. As a result, update
the filename containing "cobalt" and files content containing "cobalt".
CRs-Fixed: 1070840
Change-Id: I2c7b95e3e2a2fec7730724da9eeb86a39a77faf1
Signed-off-by: Runmin Wang <runminw@codeaurora.org>
Signed-off-by: Kyle Yan <kyan@codeaurora.org>
Signed-off-by: Jeevan Shriram <jshriram@codeaurora.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The WLED boost controller in pmicobalt supports auto PFM mode when
LCD mode is selected. Auto PFM mode is enabled by default except
on some specific hardware versions. Add a property to specify
AUTO_PFM_THRESHOLD for the boost controller so that it can enter
PFM mode when the adaptive headroom voltage falls below the
threshold.
CRs-Fixed: 1081738
Change-Id: I964b3452d0cdb3618b4ab446655ae75fa3a1049d
Signed-off-by: Fenglin Wu <fenglinw@codeaurora.org>
|
|
|
|
Use the correct LED_OPTIONS mask to enable all the supported
flash prepare APIs.
CRs-Fixed: 1090029
Change-Id: I66f6de42b106fa2027285e7393b6f9fc143d00d8
Signed-off-by: Anirudh Ghayal <aghayal@codeaurora.org>
|
|
Currently, dev_*() variants are used in the flashv2 LED driver
for logging. However, it spews the kernel log because of the
device name being longer. Logging with device name is also not
really needed. Move to using pr_*() variants. Add a pr_fmt() to
help that by adding a function name which will be more useful.
Change-Id: I42503ccd2b2dcc62c5c868132d202b9698c9d216
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
|
|
Add support for configuring the three thermal mitigation
thresholds from device tree.
CRs-Fixed: 1060212
Change-Id: Iafb7915e196a18b5f8076dda8fb06a4bd71a8e6e
Signed-off-by: Devesh Jhunjhunwala <deveshj@codeaurora.org>
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
|
|
Add support to configure thermal debounce, hysteresis and
ramp down rates from device tree.
CRs-Fixed: 1060212
Change-Id: Iabe79bae5f9471c3c6128ed21efd04de00739daa
Signed-off-by: Devesh Jhunjhunwala <deveshj@codeaurora.org>
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
|
|
There are some features which needs to be enabled based on the
PMIC. PMIC information such as subtype, revision can be obtained
from revid peripheral. Hence add support to read pmic revid.
Change-Id: Ie7a94f59e58b8f1b0816afda2496449694629205
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
|
|
Allow the mitigation clamp current values for the leds to be
configured through the device tree.
CRs-Fixed: 1060212
Change-Id: I23bf67fba7cef2735db436899a9d5b3306e5a77f
Signed-off-by: Devesh Jhunjhunwala <deveshj@codeaurora.org>
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
|
