Update the register protection configurations as per the latest
recommendation.
Change-Id: I70365268e8e4c7ee4ff28538f22e970822e4edf0
Signed-off-by: Akhil P Oommen <akhilpo@codeaurora.org>
This reverts commit 767358cd96.
Revert as this change causing cx pc failure.
Change-Id: Ic2ee49b4420132dd7b118cd06689a875ff578928
Signed-off-by: Ram Prakash Gupta <rampraka@codeaurora.org>
Removing unwanted string format specifier in a log API to avoid
potential kernel panic.
Change-Id: Iceb2ae7a0d08946685bdd922c7e52800ed3c65a5
Signed-off-by: Sai Chaitanya Kaveti <skaveti@codeaurora.org>
Consider a scenario when a device which supports auto suspend is
connected to DUT and auto suspend happened. Now, as the device is
disconnected to DUT. Resume_work is called due to extcon notification
of disconnect and then again suspend is expected to schedule. As
a part of disconnect, power event irq and DP_HS_PHY_IRQ also got
triggered and now since usb is in lpm, resume work got scheduled
twice. This resume work flushed sm_work which is stuck because
disable_irq call is waiting for pwr_irq call which called resume_work
to complete. This is clearly a circular dependency because
resume work will flush sm_work which is waiting for pwr_irq_thread
to be complete because disable_irq in msm_suspend waits for
pwr_irq_handler to complete.
Solve this by replacing disable_irq api with disable_irq_nosync
so that it doesn't block control suspend.
Below are the sequence of events.
usb is auto suspended with device connected to DUT.
Now device is disconnected from DUT and hence resume
hanppens first and then suspend.
dwc3_resume_work is called due to extcon as a part of
disconnect then suspend will be scheduled.
When dwc3 is still in lpm, i.e dwc3_resume_work did
not take effect yet.
Now power event irq is fired because of which resume
work runs.
This resume work flushes sm work. Which is currently
executing msm_suspend where disable_irq is waiting
for power_irq call to finish which is waiting for
sm_work to finish.
Change-Id: Ibf6e73663d4acaf997291e7eff6577adeaad6e8a
Signed-off-by: Rohith Kollalsi <quic_rkollals@quicinc.com>
The API - cnss_pci_set_max_link_speed sets max pcie link speed based
RC number, and affect other endpoints for PCIe switch platform. So,
don't set max link speed if dtsi configuration - "default_gen_speed"
is invalid.
Change-Id: I2b9263fb6c0b45dcb19cdc112fb04767648016f4
Signed-off-by: Wu Gao <wugao@codeaurora.org>
This patch adds format specifier corresponding to arguments
passed to print debug logs.
Change-Id: Iff586dd827037cca3419e1c3c9822d2637ef94aa
Signed-off-by: Balakrishna Godavarthi <bgodavar@codeaurora.org>
Usecase:
1) WLAN ON triggered first and then immediately BT
ON triggered.
2) As WLAN ON triggered first, before pulling WL_EN to high
it will wait for 100ms as BT_EN is low.
3) WLAN timed out first and pulls WL_EN to high and
in mean time BT_EN is checking WL_EN status to pull BT_EN to high.
Expected behavior: BT_EN must pull high before sending version command.
Observed behavior: BT_EN is not pulled high as WL_EN state changes
from low to high. While BT_EN checking the WL_EN state.
Fix: Check BT_EN status and pull it to high if it not set to high
Change-Id: I13e209ac4e1523d377f252aa5c0d243abeb86af4
Signed-off-by: Balakrishna Godavarthi <bgodavar@codeaurora.org>
In perf_event_addr_filters_apply, the task associated with
the event (event->ctx->task) is read using READ_ONCE at the beginning
of the function checked and then re read from event->ctx->task,
voiding all guarantees of the checks. Reuse the value that was read by
READ_ONCE to ensure the consistency of the task struct throughout the
function.
Fixes: 375637bc52 ("perf/core: Introduce address range filtering")
Change-Id: Ia4f6161cfc2c95073aeaff85936efa737508c5a2
Signed-off-by: Baptiste Lepers <baptiste.lepers@xxxxxxxxx>
Signed-off-by: Peter Zijlstra (Intel) <peterz@xxxxxxxxxxxxx>
Link: https://lkml.kernel.org/r/20210906015310.12802-1-baptiste.lepers@xxxxxxxxx
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
Signed-off-by: Baptiste Lepers <baptiste.lepers@xxxxxxxxx>
Git-repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Git-commit: b89a05b21f46150ac10a962aa50109250b56b03b
Signed-off-by: Kishor Krishna Bhat <kishkris@codeaurora.org>
Enable this driver for SoftAP support on sdxnightjar.
Change-Id: I47422b43c0ea23f32275f2de23a2af40f2212613
Signed-off-by: Rohith Kollalsi <quic_rkollals@quicinc.com>
With a corner case, where shutdown context and clk ungating context is
scheduled, after turning on the clocks ungating context goes for
powering up of the phy, But shutdown context turns off the clk before
and this is leading to NoC while tyring to access phy registers.
Right fix for this would be to cancel and wait for the ungate context
but due to gki restrictions adding checks in vendor specific file to
abort phy power on when clks are off.
Change-Id: I0c6fb4506f747faf71428f8a0086ddd773c4b727
Signed-off-by: Ram Prakash Gupta <rampraka@codeaurora.org>
Move definition of IPA_ETH_API_VER to msm_ipa.h so it
can be accessed by IPACM and other user space modules.
Change-Id: Ib4dafe1db310b352bbbb08018fc9e63c398cb09a
Signed-off-by: Michael Adisumarta <madisuma@codeaurora.org>
This change adds the needed support to enable best fit algorithm
for iova allocation. Best fit algorithm helps in reducing fragmentation
and thus utilizing the iova address space more efficiently.
Change-Id: Icaa9bf1db534eba75c1b5724b6210240e4e6faef
Signed-off-by: Elson Roy Serrao <eserrao@codeaurora.org>
Register msm_nand to panic notifiers list to dump apss
qpic bam registers information during any subsytem failures.
Change-Id: If717d063b41dc8e75b707574e4f703ea4b41da65
Signed-off-by: Pradeep P V K <pragalla@codeaurora.org>
write_seqcount_begin expects to be called from a non-preemptible
context to avoid preemption by a read section that can spin due
to an odd value. But the readers of vm_sequence never retries and
thus writers need not disable preemption. Use the non-lockdep
variant as lockdep checks are now in-built to write_seqcount_begin.
Bug: 161210518
Signed-off-by: Vinayak Menon <vinmenon@codeaurora.org>
Change-Id: If4f0cddd7f0a79136495060d4acc1702abb46817
Git-commit: c9201630e8a53106406516ba40862e637c324480
Git-repo: https://android.googlesource.com/kernel/common/
Signed-off-by: Srinivasarao Pathipati <quic_spathi@quicinc.com>
Fix incomplete fw_build_id in IPC logging due to MAX
character limit. Cleaned up in debug code.
Change-Id: Ia0f104158645e27f774d9598883cfcd8ec765d3c
Signed-off-by: Naman Padhiar <quic_npadhiar@quicinc.com>
Add new ioctls for rmnet to reg/unreg for yellow water mark hit
notifications.
Change-Id: Ib1162213e8fc463efaaa1149330e889110dc3dab
Signed-off-by: Michael Adisumarta <madisuma@codeaurora.org>
Changes are to save and restore PCI switch config space as part
of suspend late using framework support.
Framework does save and resore post suspend and prior to suspend
late, hence this change is important for switch.
Change-Id: I1aa06ad43d647fb8deb8cf15903c91d43344553c
Signed-off-by: Subramanian Ananthanarayanan <skananth@codeaurora.org>
The current implementation does not check for D value is within
the accepted range for a given M & N value. Update the logic to
calculate the final D value based on the range. While at it, add
support for 2/3 divider in frac_table_pixel.
Change-Id: Ia42b9197de6d594129b1a48106f8e5a2be70a1c6
Signed-off-by: Taniya Das <tdas@codeaurora.org>
Signed-off-by: Jagadeesh Kona <jkona@codeaurora.org>
Macro for detecting consolidated stats structure mismatch
between ipa_lnx_agent and IPA stats module.
Change-Id: I5322d432710a798305b6943a0e4b379880eabab9
Signed-off-by: Michael Adisumarta <madisuma@codeaurora.org>
This change increases MBIM IN aggregation and related TRB buffer size
from 16KB to 31KB. With this aggregation change, DL throughput is
increased form 4.2 Gbps to 4.7 Gbps. Also reduced OUT buffer size from
31KB to 16 KB (i.e. as equal to size of OUT aggregation).
Change-Id: Ida6444536f27f385034fefc71e663d7b7ce5626f
Signed-off-by: Mayank Rana <mrana@codeaurora.org>
Signed-off-by: Elson Roy Serrao <eserrao@codeaurora.org>
CONFIG_SCHED_DEBUG maintains scheduler statistic debug information
and can accessed the data dynamically.
On user builds, its not needed to enable debug related information,
so disable the scheduler debug.
It can improve system performance and network throughput too.
Change-Id: Ic0ca28d49210266fc5931979cde7f72a5c421e79
CRs-Fixed: 3048893
Signed-off-by: Lingutla Chandrasekhar <clingutla@codeaurora.org>
Signed-off-by: Jianmin Zhu <jianminz@codeaurora.org>
Add code to update the bound checks for sbl reg dumps to SRAM mem
range. Due to a firmware update, the sbl start address was moved
and the bound checks to dumps sbl reg failed. Update the bound
checks to SRAM mem range, so that any future update in firmware
would not impact SRAM dumps.
Change-Id: I28026f03fe1f44f2ba6ff7f903dcb98543f8847c
Signed-off-by: Mohammed Siddiq <msiddiq@codeaurora.org>
