This adds support for MAX31760 Fan Controller.
Fan is enabled and its speed can be controlled.
Change-Id: Ie716b8558ebbd357f85d2484eaa66121eb09f52d
Signed-off-by: Minghao Zhang <[email protected]>
The change includes passing the packet structure to the sfe module
which includes functional pointer to tpacket_rcv needed for tcpdump
log collection.
Change-Id: Icab7663dac3f7b8681386b96945b7e170a4325f3
Acked-by: Rishav LNU <[email protected]>
Signed-off-by: Utkarsh Saxena <[email protected]>
Add support to enable IO Coherency based on DT property.
Change-Id: I8de1b1cb6603c6852fe0f02b8b22806ad550bc48
Signed-off-by: Naman Padhiar <[email protected]>
Doorbells can be received immediately after registering. Ensure the
qrtr endpoint has been registered and initialized before enabling the
rx doorbell.
The tx doorbell should be done before registering the endpoint since
the qrtr core logic can attempt to send immediately after registration.
Change-Id: Ice332b4a053ea6e78bfded1e3625d8c527917e7b
Signed-off-by: Chris Lew <[email protected]>
When battery_id is set to a value for which there exists no
battery profile, QG driver prints error logs frequently as
some properties doesn't exist.
[ 4305.969087] QG-K: qg_get_charge_counter: Failed to get FCC for charge-counter rc=-19
[ 4305.969123] QG-K: qg_iio_read_raw: Couldn't read IIO channel 73, rc = -19
[ 4305.976657] QG-K: qg_iio_read_raw: Couldn't read IIO channel 83, rc = -19
[ 4305.989355] QG-K: qg_iio_read_raw: Couldn't read IIO channel 84, rc = -19
Fix this by changing pr_err() to pr_err_ratelimited(). While at
it, change a pr_err() to pr_debug(). Also fix an error log to
correct that the error is for reading IIO channel and not for a
property.
Change-Id: I936409d4ffafd664c571976d17ec4baf1b8de218
Signed-off-by: Subbaraman Narayanamurthy <[email protected]>
Initialize the waitq before registering with the doorbell framework to
prevent uninitialized variable access.
Change-Id: Icb902b829a6af52716713b18891e4e35c0c2a620
Signed-off-by: Chris Lew <[email protected]>
This also includes new extended ingress-egress ioctls for configuring
system pipe.
Change-Id: I96f3d57037f32e1f904737439cacc8026f7cdb1f
Signed-off-by: Michael Adisumarta <[email protected]>
It has been observed that default values for some of key tcp/ip
parameters are affecting the tput/performance of the system. Hence
extending configuration capabilities to TCP/Ip stack through
sysctl interface.
Change-Id: I4287e9103769535f43e0934bac08435a524ee6a4
CRs-Fixed: 507581
Signed-off-by: Ravi Joshi <[email protected]>
Signed-off-by: Ganesh Babu Kumaravel <[email protected]>
Signed-off-by: Mohit Khanna <[email protected]>
Signed-off-by: Manjunathappa Prakash <[email protected]>
Signed-off-by: Sandeep Singh <[email protected]>
Signed-off-by: Rakesh Pillai <[email protected]>
Currently err_evt_seen flag is cleared only while clearing
run/stop. Consider a case where err_evt_seen flag is set and
controller is swtiching from peripheral mode to host mode.
Now, from dwc3_gadget_pullup driver will bail out since the
flag is set. Also since softconnect flag is not set run_stop
will not get cleared from vbus_session(0), leaving the err
evt_seen flag set. If any interrupt is generated then driver
will bail out from interrupt handler without processing the
interrupt, which can lead to irq storm. Fix this by clearing
the err_evt_seen flag in disconnect and also add a judgement
in pullup so that driver can proceed with clearing run/stop
if softconnect is cleared, even with the err_evt_seen flag is
set.
Change-Id: Ib7026dca8b4e76e943832419b19cef180ca96171
Signed-off-by: Pratham Pratap <[email protected]>
For ADSP based charger detection set the current for all
charger types as it will again be handled on ADSP side.
Other wise set current only for SDP charger which is usb
based charger. For NON ADSP based charger detection if
'iio-channel-names' is passed in the device tree, charger
detection is done through iio channel or else it is
done by power_supply_get_property.
Change-Id: I17e65448459318ad26b7a2c36742296afa5f0adf
Signed-off-by: Rohith Kollalsi <[email protected]>
With ARM_SMMU_POWER_ALWAYS_ON enabled, clocks are always on. There arch
write sync is not required. Move arch write sync post checking for clock
refcount.
Arch write sync takes longer due to virtualized global register read. Use
non virtuazlied global register to reduce read latency.
Change-Id: Ic497c7ba75cc8ba2ed804f2c987e0c595487ce40
Signed-off-by: Prakash Gupta <[email protected]>
Don't clear io pad power switch setting when 3V support is faked.
This bit has to be cleared for allowing IO pad to switch to 3V when
Vccq is really configured to 3V. But in case of faking 3V where we
configure Vccq to 1.8V only, we shouldn't clear this bit.
Change-Id: I15c7e3f49703c3ac31d59d7d4bfbd81f3c2dc028
Signed-off-by: Sarthak Garg <[email protected]>
Change the ILED_SYNC and MOD_SYNC write sequence from 0 to 1
instead of 1 to 0 as per HW recommendation.
Change-Id: I93f4491cd1fd59ba5839c458157265c2d75315f9
Signed-off-by: Kiran Gunda <[email protected]>
The current design of sw-jeita handling requires some predefined
steps to be added for jeita step charge, These steps need to be
tuned and updated appropriately on every platform to get the best
charge time. Add support for auto jeita fcc scaling which
when enabled auto-scales the FCC depending upon the granularity
of increase in battery temperature.
Change-Id: Ida1c9b62f1a94e32de5e74ecb75c5c0b5d47548d
Signed-off-by: Ashish Chavan <[email protected]>
lock_sock got wrongly added in qrtr_recvmsg as part of the
patch "net: qrtr: print error case for qrtr receive".
Reverting lock_sock and release_sock in qrtr_recvmsg.
Change-Id: I7f9639405a67e2201a848277145bac57c88f6567
Signed-off-by: Sarannya S <[email protected]>
Server arrive may come before initializing penv which
causes possible NULL pointer dereference.
To address this, use function argument priv instead of
global variable penv.
Change-Id: I1355074614b4f30fff1c021db53654b4c844135c
Signed-off-by: Dundi Raviteja <[email protected]>
SMBLITE charger drivers and their helper files use several power supply
properties on msm-4.19 which cannot be supported on msm-5.4 due to the
need for GKI compliance. Add support for main charger to register
as an IIO device with individual channels under it corresponding to
missing power supply properties from msm-4.19.
Change-Id: I397ed52d2fa822c7f93616090e15b109435d9657
Signed-off-by: Ashish Chavan <[email protected]>
Upon bus suspend when IPA requests for usb remote wake up, it is not
allowing enough time for the host to wakeup from U3. IPA is continuously
trying to wakeup the host and eventually resets the bus. Fix this issue
by adding a flag to check the status of usb remote wakeup and ignores
the request from IPA if it is in progress.
Change-Id: Id55928b7f5d3ae7f282a3b8db44949d396db0ddd
Signed-off-by: Hemant Kumar <[email protected]>
Signed-off-by: Mayank Rana <[email protected]>
we need to enable out of kernel compilation of SOUNDWIRE
bus driver.
Change-Id: I3275eba112b44701071595e45d11c3d6cff0ee2e
Signed-off-by: Asish Bhattacharya <[email protected]>
Add a condition check before calling gpio_request in order
to avoid non-fatal panic.
Change-Id: Id77b99b0a7c119efb75e50c85ec185895dd8c031
Signed-off-by: Mahesh Kumar Sharma <[email protected]>
Following race condition was detected:
<CPU A, t0> - neigh_flush_dev() is under execution and calls
neigh_mark_dead(n) marking the neighbour entry 'n' as dead.
<CPU B, t1> - Executing: __netif_receive_skb() ->
__netif_receive_skb_core() -> arp_rcv() -> arp_process().arp_process()
calls __neigh_lookup() which takes a reference on neighbour entry 'n'.
<CPU A, t2> - Moves further along neigh_flush_dev() and calls
neigh_cleanup_and_release(n), but since reference count increased in t2,
'n' couldn't be destroyed.
<CPU B, t3> - Moves further along, arp_process() and calls
neigh_update()-> __neigh_update() -> neigh_update_gc_list(), which adds
the neighbour entry back in gc_list(neigh_mark_dead(), removed it
earlier in t0 from gc_list)
<CPU B, t4> - arp_process() finally calls neigh_release(n), destroying
the neighbour entry.
This leads to 'n' still being part of gc_list, but the actual
neighbour structure has been freed.
The situation can be prevented from happening if we disallow a dead
entry to have any possibility of updating gc_list. This is what the
patch intends to achieve.
Change-Id: Ic8d4870586e09a8f6b6ebd190e815a18f49a269e
Fixes: 9c29a2f55e ("neighbor: Fix locking order for gc_list changes")
Signed-off-by: Chinmay Agarwal <[email protected]>
Enable QoS for the master ports on Yupik with predefined
values for priority and urgency.
Change-Id: I37c3e8e53322cc5e60cced60990333480d158f46
Signed-off-by: Odelu Kukatla <[email protected]>
Add the debug mux structure with inputs for measuring the
HLOS controlled clocks on SM6150.
Change-Id: I4f8565dcd2bd2750f56e4e0aaee990130b3d2d61
Signed-off-by: Veera Vegivada <[email protected]>
Export slew pll ops to allow clock drivers to be
compiled as modules.
Change-Id: I52e087ea1f0e3b8286255bae6ea65f411a7c4178
Signed-off-by: Veera Vegivada <[email protected]>
Add a sensor clock controller (SCC) driver which can be used
to control sensor clocks on boards in which the application
processor owns these clocks.
Change-Id: I76aa5a35509f7fa48ee4109941caa9b410d7f350
Signed-off-by: Veera Vegivada <[email protected]>
Add support for the video clock controller found on SM6150
based devices. This would allow video device drivers to
probe and control their clocks.
Change-Id: Iffccc48d642d291db2133092cf19d4a726f25c99
Signed-off-by: Veera Vegivada <[email protected]>
There is a possibility of the "real capacity" dropping post
termination due to a OCV update causing the charger-termination
WA to exit. Fix this by explicitly checking that we are not
in termination before exiting from the WA.
Change-Id: I5bf91367b633abf79cbc60ef5bdf93cca9559029
Signed-off-by: Anirudh Ghayal <[email protected]>
