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 <clew@codeaurora.org>
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 <subbaram@codeaurora.org>
Initialize the waitq before registering with the doorbell framework to
prevent uninitialized variable access.
Change-Id: Icb902b829a6af52716713b18891e4e35c0c2a620
Signed-off-by: Chris Lew <clew@codeaurora.org>
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 <ravij@codeaurora.org>
Signed-off-by: Ganesh Babu Kumaravel <kganesh@codeaurora.org>
Signed-off-by: Mohit Khanna <mkhannaqca@codeaurora.org>
Signed-off-by: Manjunathappa Prakash <prakashpm@codeaurora.org>
Signed-off-by: Sandeep Singh <sandsing@codeaurora.org>
Signed-off-by: Rakesh Pillai <pillair@codeaurora.org>
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 <prathampratap@codeaurora.org>
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 <rkollals@codeaurora.org>
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 <sartgarg@codeaurora.org>
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 <sarannya@codeaurora.org>
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 <ashichav@codeaurora.org>
Enable QoS for the master ports on Yupik with predefined
values for priority and urgency.
Change-Id: I37c3e8e53322cc5e60cced60990333480d158f46
Signed-off-by: Odelu Kukatla <okukatla@codeaurora.org>
Add the debug mux structure with inputs for measuring the
HLOS controlled clocks on SM6150.
Change-Id: I4f8565dcd2bd2750f56e4e0aaee990130b3d2d61
Signed-off-by: Veera Vegivada <vvegivad@codeaurora.org>
Export slew pll ops to allow clock drivers to be
compiled as modules.
Change-Id: I52e087ea1f0e3b8286255bae6ea65f411a7c4178
Signed-off-by: Veera Vegivada <vvegivad@codeaurora.org>
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 <vvegivad@codeaurora.org>
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 <vvegivad@codeaurora.org>
Some (PON gen2) platforms still use legacy hard-reset offset [7:2]
of the PON_RB_SPARE register. Add a DT property to support it.
Change-Id: I8fd3434bcc064965b11aaf3e9c7fcbf694145d21
Signed-off-by: Kavya Nunna <knunna@codeaurora.org>
Enable core hang detect support on gen3auto targets.
Change-Id: Ie5eb562a8aed9ac1b211c666876bf8c49bd39f2a
Signed-off-by: Shreyas K K <shrekk@codeaurora.org>
Enable the devfreq governor, monitor and device
support on gen3auto targets.
Change-Id: I463d99a61b90ec15d0661c113c57cc1ca3dd53be
Signed-off-by: Shreyas K K <shrekk@codeaurora.org>
Enable kernel configs needed to suppot ramdump on gen3auto,
these drivers help to capture necessary debug information
in DDR and IMEM when the system crashes either after a panic
or due to any system lockup.
Change-Id: Ie4d2b0cafba363703fe9cac03e6255df3e09cd7e
Signed-off-by: Vivek Kumar <vivekuma@codeaurora.org>
Signed-off-by: Shreyas K K <shrekk@codeaurora.org>
Update compatible string from qcom,wcn6750 to
qcom,wcn6750-bt inorder to make it different from
WLAN compatible string.
This will help in removing probe warnings during bootup.
Change-Id: If6f938187b5f34438ee8bf5330844b839de942b9
Signed-off-by: priyankar <prigup@codeaurora.org>
