Add __ioread32_copy to the ABI whitelist and update the ABI
snapshot accordingly.
Change-Id: I92a42471848c30d2cb174287d59b7c721eacc8cb
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
Add the symbols qcom_scm_dcvs_reset, qcom_scm_io_reset,
qcom_scm_dcvs_init_ca_v2, qcom_scm_dcvs_ca_available, and
qcom_scm_dcvs_init_v2 to the whitelist and update the
ABI snapshot.
Change-Id: I3049cecbc4256c47050a91125f359993ee1af96b
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
Remove the device tree property "qcom,altmode-name" and the logic it
feeds as it was meant to help in the cases when there are multiple
altmode devices. Since there is going to be only one altmode device as
per design, this is no longer needed.
Change-Id: Ife15e39becee5f4ff03bdcc56ff62ae812fe2726
Signed-off-by: Guru Das Srinagesh <gurus@codeaurora.org>
Client API changes:
- Update client APIs to align them more closely with upstream
conventions.
- In particular, change the link between altmode device and client from
the altmode device's name string to a phandle to the altmode device
followed by the port index of the client.
- Instead of using solely the client's SVID as the key for idr_alloc,
include port_index as well because the unique identifier of a client
is the (SVID, port_index) tuple.
Updates to client notifying mechanism:
- Get rid of the standard notifier APIs in favour of a simpler callback
function-based mechanism to notify clients of probe completion.
- In addition, if clients probe after altmode finishes probing, they
will not get notified of probe completion as this is done only once at
the end of altmode_probe(). Fix this so that if a client registers for
probe completion notifications after altmode probes, they get notified
immediately.
While at it, get rid of the global list of altmode devices (amdev_list)
as there will only be a single altmode device in the system as per
design.
Change-Id: Iea450d30d9cc94671f505b7ff0c6e98b0b8a4467
Signed-off-by: Guru Das Srinagesh <gurus@codeaurora.org>
Add the symbol, drm_dp_check_act_status, to the qcom whitelist
and update the ABI snapshot accordingly.
Change-Id: I239fafdd2d57b0600a130b7610777da8a5874afe
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
Reject idle restart request if it fails to acquire driver ops lock to
avoid deadlock inside WLAN driver. E.g. Driver remove from unregister
driver request will be blocked if idle restart request is pending.
Change-Id: I5825e02961117eaaea4202812a5d2d7140799e19
Signed-off-by: Yue Ma <yuem@codeaurora.org>
Signed-off-by: Manikandan Mohan <manikand@codeaurora.org>
Since idle restart is a multiple stages power up sequence, there will be
race conditions when idle restart and unregister driver (which is power
down sequence) come at the same time. Add mutex protection for them so
that they can be serialized completely.
Change-Id: Icc28b5f759cd690cb505b16ab70eaa4abaf2e4cc
Signed-off-by: Yue Ma <yuem@codeaurora.org>
WLAN driver unload should happen only when it has been probed
successfully. So, In driver unload path wait for driver probe
to be completed or timed out if it is already in progress.
Change-Id: I3359a4286fc36aa9b2abc95c7af3ca2b6dc3a980
Signed-off-by: Sandeep Singh <sandsing@codeaurora.org>
