Retain 2019 as the copyright year of memory_dump.h.
Change-Id: I6c9053e64c8ee7a416a2f9af028b288ef577c5d8
Signed-off-by: Mao Jinlong <jinlmao@codeaurora.org>
Fix other headers to work when KERNEL_HEADER_TEST is enabled by adding
dependencies and advance struct prototypes where appropriate.
Change-Id: Ic0dedbad6804e5dca75b33b3d0ae9e3b89a51669
Signed-off-by: Jordan Crouse <jcrouse@codeaurora.org>
Enable the fastrpc QGKI config option that the driver can use to
detect that it is being compiled in a QGKI kernel.
Change-Id: I6bd44bfd61e79ebe70689f326d5616b6d856c146
Acked-by: Thyagarajan Venkatanarayanan <venkatan@qti.qualcomm.com>
Signed-off-by: Himateja Reddy <hmreddy@codeaurora.org>
Set sound card as private data for "state" snd info
entry to avoid dereference error when user/userspace
tries to read card state.
Change-Id: Ia165fef682dd420ffedd5352efdf31d96b232a4b
Signed-off-by: Vignesh Kulothungan <vigneshk@codeaurora.org>
The logic for calculating the request buffer sizes for the
MEM_SHARE and MEM_LEND resource manager calls is not present,
so add it.
Change-Id: I804ee108565733b0e4b376b5fd31abdb3d359c1f
Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
Use the locally calculated value of memory attribute entries when
populating the memory attribute descriptor, instead of always
dereferencing the client provided memory attribute descriptor,
as clients may not always provide one.
Change-Id: Ifbe586336e69e439ed404067616cce7515fd7953
Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
Changes to fix compilation for inline encryption
when compiled as modules for GKI.
Change-Id: If091f807fdfb42ceb846334458c48d1687231f6e
Signed-off-by: Gaurav Kashyap <gaurkash@codeaurora.org>
Add subsystem restart (SSR) support to altmode glink driver so
that when subsystem goes down and comes up again, it can send
PAN_EN to charger firmware to receive notifications about altmode
interface.
Change-Id: Ie011d5110b6c26790fe1dd6149115019f8bc261c
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
Add subsystem restart (SSR) support to battery charger driver so
that it can stop read/write properties when subsystem goes down.
Also, send message to enable notification again once subsystem
comes up.
Change-Id: I64f3abfa1d12c4e6a65fd01d7f66155c8741e68a
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
Add subsystem restart (SSR) support to UCSI Glink driver so that
it can unregister from UCSI framework when subsystem goes down
and register with UCSI framework when it comes up again. When
subsystem goes down, it is not possible for UCSI stack to send
or receive data to and from PPM (i.e. remote subsystem) over
PMIC Glink. Hence, return immediately in ucsi_qti_{read,write}()
to avoid error logs and handle cleanup easily.
Change-Id: I711920222bd531af27b87337cad7db8aabbaa466
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
Add support for PMIC Glink clients to receive notification when
the subsystem goes down and comes up again. PMIC Glink client
can pass a function pointer state_cb via which they would like
to receive when PMIC Glink state transitions so that they can
unregister from the framework (e.g. UCSI) and clean up their
state as needed.
PMIC Glink device supports SSR for the subsystem specified under
"qcom,subsys-name" property.
Change-Id: I0f32f638d72a13e231e6813fb3d782c8fa7a4af0
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
In preparation for subsystem restart (SSR) and protection domain
restart (PDR) where subsystem state transitions would be sent to
PMIC Glink clients via another callback function, change the client
callback function pointer name to msg_cb. This would convey that
this callback is for delivering the messages to a client upon its
registration.
Change-Id: I584d6c5d3898fe54e6928b25502d6382ce6ccbc4
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
The ION trusted VM flag may map to a VMID that was dynamically
assigned, instead of statically allocated. Thus, use the RM driver
APIs to determine the VMID for the trusted VM.
Change-Id: Ide4dd77a4cedbdf7e32f3c834fef9a0dfc6ba9d5
Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
Currently, the clients of the hh_msgq driver would allocate buffers,
fill with data and call hh_msgq_send(). Upon success, hh_msgq_send()
would be freeing the buffer, while in the case of failure, the clients
are responsible for it. However, this approach of buffer management is
not symmetric and could be confusing for the clients. Hence, let the
clients take full ownership of the buffers- allocating and freeing.
Also make changes to the affected client drivers.
Change-Id: I73101d823f9d3de16414e444fde494222f584e53
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
It's a highly likely situation that the clients call hh_msgq_recv()
from a thread in a polling fashion, and these threads are spawned
during client driver's initialization. Hence, it's possible that
the cap-ids for the message queues will not be ready so early and
the clients would end up continuously spinning on hh_msgq_recv(),
receiving the error -EAGAIN. To avoid this situation, put the
client process onto a wait-queue until the cap-ids are ready.
Although a little unlikely, to satisfy the symmetry, add the same
provision for the callers of hh_msgq_send() as well.
Change-Id: I4e042215c5e43271d566340ce1ef9c52ecafeb5c
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
Signed-off-by: Murali Nalajala <mnalajal@codeaurora.org>
hh_msgq_register() can now return -EPROBE_DEFER as an error code.
Since this is not a fatal error, and will end up in having the
probe function called again at a later point in time, do not
print an error when -EPROBE_DEFER is returned.
Change-Id: I7646788719bdbaac309bc1fbd840de754398e23b
Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
This change provides the infrastructure required to tune Gen2
Tx compliance parameters via device tree. The tuning values
provided through dt properties are written to the corresponding
de-emph dwc3 registers during core initialization.
Change-Id: I38015a6f12ca27247bce5ea805d86322122f3466
Signed-off-by: Elson Roy Serrao <eserrao@codeaurora.org>
Add the QRTR haven transport that facilitates sending and receiving
IPC Router messages between virtual machines that use the haven
hypervisor.
Change-Id: I805ee5b144c5a8fc92e4a045061770d06495f63c
Signed-off-by: Chris Lew <clew@codeaurora.org>
This is needed to setup the UCHE command queue configuration.
Also patch the power up register list after all register writes
are in place.
Change-Id: I370c489fd0c23101947c97a45d0da42cc9db41b7
Signed-off-by: Raghu Ananya Arabolu <rarabolu@codeaurora.org>
Set the max value of num_fds to QCEDEV_MAX_BUFFERS to prevent
out of bound access of fd, fd_size, fd_offset array.
Change-Id: I88889472a4bd14f786588bd2c9e06e69a98e94c9
Signed-off-by: Prerna Kalla <prernak@codeaurora.org>
Captures return value while registring i2c adapter to the bus, if fails
then return the same value and print the error code.
Change-Id: I6ff5b5a2bf4436ba076807fe2bdd11635a65d367
Signed-off-by: Mukesh Kumar Savaliya <msavaliy@codeaurora.org>
On RUMI, UFS PHY reset control provided from UFS host controller is not
optional, return error if it is not provided.
Change-Id: I15faa41b8e251abb773bc28b686c28a41574d229
Signed-off-by: Can Guo <cang@codeaurora.org>
Currently, process specific info like name and PID is being stored
in the internal data structures at the time of device open. But
since the DSP HAL service will now be opening the device node on
behalf of third-party applications, store process specific info in
GETINFO ioctl call which will be the first IOCTL call directly
from the client application.
Change-Id: If05d48123e4ec52c0271a7cb7f3ca790662d9abe
Acked-by: Thyagarajan Venkatanarayanan <venkatan@qti.qualcomm.com>
Signed-off-by: Edgar Flores <edgarf@codeaurora.org>
Signed-off-by: Himateja Reddy <hmreddy@codeaurora.org>
The haven RM driver header file exposes functions where notifier
blocks are used. However, not all clients who include the
header file will necessarily have the notifier header file
in their source file, which causes compilation errors. Thus,
include the notifier header file in the RM driver header file
so that all other clients don't have to.
Change-Id: If74509e5d7fc2bbaeb4a427a7cd576f853fd8358
Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
The EUD driver operates on the power-supply property,
POWER_SUPPLY_PROP_INPUT_CURRENT_LIMIT, under the power-supply "battery".
This is incorrect as POWER_SUPPLY_PROP_INPUT_CURRENT_LIMIT is a part of
"usb" power-supply and not "battery". Hence, configure the driver with
the correct power-supply (and alter the names of corresponding
variables and functions).
Also, drop the reference to the power-supply from the platform driver's
.remove callback.
Change-Id: I9629586b8e429d70f22f3f60576adad78ea5d6d4
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
Chipsets on msm-5.4 does not require PCIe bus driver to
aggregate each PCIe port rate change clock vote. Therefore,
remove the support for it.
Change-Id: I670f045b36c7473d5fc285a1cb45a8175b755dcb
Signed-off-by: Tony Truong <truong@codeaurora.org>
Having pipe clk mux source set to PCIe pipe clk can possibly
cause PCIe gdsc to be stuck while being disabled until the
source is switched to XO. Therefore switch the source to XO
before disabling PCIe gdsc.
Change-Id: I5292c1e3b7a006b3857ef82fa446392d324d616f
Signed-off-by: Tony Truong <truong@codeaurora.org>
Remove the use of DMA_ATTR_FORCE_NON_COHERENT and
DMA_ATTR_FORCE_COHERENT attributes while allocating and mapping
memory in the fastrpc driver, as they are not supported in a GKI
kernel. Ignore any per-buffer coherency attributes passed by
userspace.
Add a new config option that can be used by the fastrpc driver to
detect if it is being compiled in a QGKI kernel. Read the DMA
coherency property of the fastrpc device nodes only if this config
has been enabled. On a GKI kernel, the cache maintenance will
always be done by the fastrpc driver.
Change-Id: Id1e715da4462d9fb8819fc1c85f7b0c7d8610f24
Acked-by: Thyagarajan Venkatanarayanan <venkatan@qti.qualcomm.com>
Signed-off-by: Himateja Reddy <hmreddy@codeaurora.org>
atos_write() uses the IOVA stored in the debug device structure
for translating the input IOVA to a physical address, which is
not correct, given that the debug device structure's IOVA field
has not been initialized yet. Use the IOVA given as an input
for translating the IOVA to a physical address.
Change-Id: I7a8f241abc573fcf877147ca4d808c025cbb45f9
Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
