Do not allow q2spi transfer when port is in closed state,
restrict q2spi transfer if gsi failures are seen prior port
closure to avoid further failures.
Change-Id: If394b25feb6e2e68e58ce650522465b74c9b0b14
Signed-off-by: Jyothi Kumar Seerapu <quic_jseerapu@quicinc.com>
This change will clean up the unmapping of buffers in the error path
and helps in overcoming the short of buffer issues.
Also fixed the NULL pointer access issue crash
from q2spi_put_slave_to_sleep().
Corrected return value in q2spi_transfer function.
Change-Id: If95587c78ae7af915574b7c14aaf6bae575817ed
Signed-off-by: Chandana Kishori Chiluveru <quic_cchiluve@quicinc.com>
Signed-off-by: Jyothi Kumar Seerapu <quic_jseerapu@quicinc.com>
In multi CR case, driver processing HRF write request and waiting
for HRF flow doorbell and their is a chance that ganges can
report independent CR doorbell or doorbell with multi CRs.
This is leading to blocking of independent doorbell processing.
Fix this issue by moving blocking wait function from
__q2spi_send_messages.
This will help to serve incoming independent doorbells in the
order we received in multi CR case.
Change-Id: Id9a51979cfcf7780e66a7b2ae9f47786fff986be
Signed-off-by: Chandana Kishori Chiluveru <quic_cchiluve@quicinc.com>
If scaling_min_freq/scaling_max_freq changes, then there can be scenarios
where it is not honored promptly due to down_rate_delay_ns and
up_rate_delay_ns. Remove this check as scaling_cur_freq should honor
scaling_min_freq and scaling_max_freq.
Change-Id: I9dcc7cc431ab0b56872fbd6ee4b21e5dc86284fc
Signed-off-by: Shivnandan Kumar <quic_kshivnan@quicinc.com>
Update the config state from bool to tristate for VirtIO minidump
module.
Change-Id: Ic678c32586c242a4997765edc2f78735b3edc69e
Signed-off-by: LADI RAM SAI <quic_lramsai@quicinc.com>
Enable Virtio minidump and debug_symbol modules for
auto LAGVM.
Change-Id: Ib09d0c86c7de2e98b5c805df378418bc67164aaa
Signed-off-by: LADI RAM SAI <quic_lramsai@quicinc.com>
Add the support for RIMPS based cpufreq domain, thereby also adding the
soc_data for RIMPS and RIMPS-PDMEM.
Change-Id: I0ee06b0e8113c950958e25a9f59a5c27ef692fec
Signed-off-by: Anaadi Mishra <quic_anaadim@quicinc.com>
Signed-off-by: Taniya Das <quic_tdas@quicinc.com>
This change enables the compilation of the DRM helpers for
display driver on niobe target.
Change-Id: Ib59f3a2e8a80e6d4431a4880cfa9e9f36be0413c
Signed-off-by: Soutrik Mukhopadhyay <quic_mukhopad@quicinc.com>
Check for NULL before going ahead and waking up the SOCCP
during SoC crash scenario.
Change-Id: I829d3ab676676c9dbfc4ca6d9acf35180f3bcd22
Signed-off-by: Gokul krishna Krishnakumar <quic_gokukris@quicinc.com>
Signed-off-by: Kamati Srinivas <quic_kamasrin@quicinc.com>
In the stop sequence the state is forced to change from D3
to D0, however this state change is not needed for the teardown
sequence to take effect.
Change-Id: I57b89885f9bdf6309349c95e27689abd72313822
Signed-off-by: Gokul krishna Krishnakumar <quic_gokukris@quicinc.com>
Signed-off-by: Kamati Srinivas <quic_kamasrin@quicinc.com>
Voting for power rails during SoC crash is leading
delay in panic handling. During a SoC crash scenario
the power rails will already be up, therefore we
dont need to vote for this again.
Change-Id: I084e6eee8a51dd75dd728e39feb50e17d4f220a7
Signed-off-by: Gokul krishna Krishnakumar <quic_gokukris@quicinc.com>
Signed-off-by: Kamati Srinivas <quic_kamasrin@quicinc.com>
During the deep sleep we should program the registers, similar like
during the probe. We are calling master setup function during deep
sleep, it will do basic register config. Same changes added for
spi slave as well.
Change-Id: I2d048c391442d6c704b7b7ad674325ff9a8ecf13
Signed-off-by: Anil Veshala Veshala <quic_aveshala@quicinc.com>
Signed-off-by: Mehul Raninga <quic_mraninga@quicinc.com>
Set the priority of hgsl workqueue by using API
alloc_workqueue instead of create_workqueue.
Change-Id: I640bc2b110f7b3997c402098f315f97a77fa7531
Signed-off-by: Jun Zhang <quic_juzhan@quicinc.com>
non-HWKM targets have only 32 keyslots. Update the
LUT KEYS secure Interrupt register offset and R16
and R17 register offset for non HWKM targets.
Test: Verified on non-hwkm target.
Change-Id: I0a70c62a270a44b1887240e06e41ada5d517d989
Signed-off-by: Seshu Madhavi Puppala <quic_spuppala@quicinc.com>
Enable the following modules which enables
data encryption (FBE) using wrapped keys.
CONFIG_QTI_CRYPTO_COMMON
CONFIG_SCSI_UFS_CRYPTO_QTI
CONFIG_QTI_HW_KEY_MANAGER.
Change-Id: Iffc1023aaa24b6406206748d7a5a8848e9847b87
Signed-off-by: kundan kumar <quic_kunkum@quicinc.com>
Add modules for USB Phys, repeaters function driver modules and IPC
logging for FFS.
Change-Id: I8a20a9aca6e00729ea40226be48f18c12046e39e
Signed-off-by: Krishna Kurapati <quic_kriskura@quicinc.com>
Add the list of modules required to exercise FBE
path during bootup. These include:
hwkm.ko
crypto-qti.ko
ufshcd-crypto-qti.ko.
Change-Id: Ifd3ffc515424af4d8365a26ff690dd7099a12640
Signed-off-by: kundan kumar <quic_kunkum@quicinc.com>
This change mainly intended to cover deep sleep requirements
along with GSI driver. There exiting deep sleep need to be
restored with probe similar configurations.
Added channel dealloc and alloc for tx,rx,event ring channels.
Change-Id: I910d58b06f3973cf7ecc8d75e0ed248310dc11f5
Signed-off-by: blingala <quic_blingala@quicinc.com>
This change is to bring the GPII channels [Tx, RX] to the reset
point and also reset the Event channel.
When system enters into deep sleep and exits, this path to gpi
configs need to be in similar state to the probe. So that we are
in same state post or during deep sleep exit path.
Change-Id: I80cd0ecf61cb004f4ec10dfde5dedc81aace81bb
Signed-off-by: Viken Dadhaniya <quic_vdadhani@quicinc.com>
Do not allow configuration access request to certain BDFs.
This is required for PCIe switches, unable to respond to
configuration access request to certain supported BDFs.
Without filtering, such BDFs are causing system bus hang
or enumeration failure of downstream ports of switch.
Change-Id: I4c4fa5cc4921dfe0217e05aaad4600abebcacd2b
Signed-off-by: Hemant Kumar <hemantk@codeaurora.org>
Signed-off-by: Krishna chaitanya chundru <quic_krichai@quicinc.com>
Signed-off-by: Yogesh Jadav <quic_yjadav@quicinc.com>
Signed-off-by: Joco Zhang <quic_pingshen@quicinc.com>
While using 32-bit userspace application, current vendor
specific ioctl calls are not getting invoked due to missing
compat_ioctl support in serial_core driver on 64-bit platform.
To fix this issue, sysfs entries are created to send the
existing ioctls commands via sysfs interface and perform
operations internally similar to the ioctls.
Below IOCTL cmds which are supported by the driver can
now be issued via sysfs path also:
(1) MSM_GENI_SERIAL_TIOCPMGET
(2) MSM_GENI_SERIAL_TIOCPMPUT
(3) MSM_GENI_SERIAL_TIOCPMACT
(4) MSM_GENI_SERIAL_TIOCFAULT
Sysfs entry /sys/class/tty/ttyHS0/device/hs_uart_version
is used to get uart driver version. Current version is 1.1
which reflects sysfs support is available along with existing
ioctl implementations.
Sysfs entry /sys/class/tty/ttyHS0/device/hs_uart_operation
is used to send commands to the driver, similar to ioctls.
Ex: echo 0x54EC > /sys/class/tty/ttyHS0/device/hs_uart_operation
will perform functionality of MSM_GENI_SERIAL_TIOCFAULT.
Change-Id: I39e5d612cfbf698a1f4c5af3ca2e3a85d9d0d06c
Signed-off-by: Prasanna S <quic_prass@quicinc.com>
