In case of cma allocation failure, req-size is logged, but instead of
requested size we are printing total size. Fix it.
Fixes: 45422bc880 ("mm: cma: Print region name on failure")
Change-Id: Ifc96209a0ccdb295fbb9767d3d93b3a567fa16fd
Signed-off-by: Zhenhua Huang <zhenhuah@codeaurora.org>
Rename quinvmauto to autogvm to have superset configs for
all gen linux guest.
Change-Id: Ic4a87ebdf4aa3d97ee4dd8265e4dcbde630637e7
Signed-off-by: Venkata Rao Kakani <vkakani@codeaurora.org>
qcom,converged-dt is meant to use one DT node which has multiple
sub-nodes to support multiple devices. There is also one simple
scenario that one same DT node can be directly used by multiple
devices without creating sub-nodes. Use separate DT entry for such
case to add firmware path prefix to simplify implementation and
avoid conflicts.
Change-Id: I3beb3dfce30d31f086eeb6667afa83560880ff32
Signed-off-by: Yue Ma <yuem@codeaurora.org>
In order to support MBIM in a multi-config usb composition
make use of composite gadget driver support for OS descriptor.
This allows Host to identify preferred configuration to choose.
Pass signature field, vendor code, compatibleID and
subCompatibleID from user space. Also remove redundant MBIM OS
descriptor related data structure definitions in the driver.
Change-Id: I6fd8b950d53ef700be2d435e5973dd2c74525cd8
Signed-off-by: Hemant Kumar <hemantk@codeaurora.org>
Signed-off-by: Chandana Kishori Chiluveru <cchiluve@codeaurora.org>
Signed-off-by: Mayank Rana <mrana@codeaurora.org>
Signed-off-by: Elson Roy Serrao <eserrao@codeaurora.org>
Porgramming guide for tcu clock testbus controller says:
1) Write to the ARM_SMMU_TESTBUS_SEL_HLOS1_NS.
2) Read from the ARM_SMMU_TCU_TESTBUS_HLOS1_NS
to know the internal smmu clock status. Program them accordingly.
Change-Id: I6140d877c2d8366030699fb04099078ebb3b6e2c
Fixes: 47b2cb7ab2 ("iommu: arm-smmu: update access to SMMU TCU testbus registers with scm call")
Signed-off-by: Charan Teja Reddy <charante@codeaurora.org>
SPI Transfer mode selection is based on length but in SPI responder case
we get some latency for FIFO mode transfer that will cause some delay
in SPI responder transfer and we get "TX_FIFO_RD_ERR" interrupt. Moving
SPI responder to DMA mode for all transfer will not have this latency
issue and SPI requester/responder will be in sync and we won't get any
error related to SPI requester/responder sync.
Change-Id: I6b9676aad2a4875a9ff6c4d998a45d2cd8a14cfa
Signed-off-by: Ashish Kori <akori@codeaurora.org>
Ensure usbch is ready before usb bypass start to avoid usbch is NULL
in usb_read_work_fn().
Change-Id: I0b932f1713a2d49424860728e79e3684122b4e40
Signed-off-by: Yuanfang Zhang <zhangyuanfang@codeaurora.org>
Enable LKDTM driver to enable testing PAN features
Change-Id: I37421dd50cc4241ae73db9d4b3b953997b2934c5
Signed-off-by: Likai Ding <likaid@codeaurora.org>
Enable linux bridge on QGKI builds to support multi-AP bridge mode.
Change-Id: I1c8278b3ca29d973ea5350028c8f065370e91271
Signed-off-by: wadesong <wadesong@codeaurora.org>
Add mproc related defconfig for sa8155 which inlcudes
qrtr,hwspinlock,mailbox,glink,smem,smp2p,ipc irq bridge
and ipc logging related configurations.
Change-Id: I64e8feea35a0acabf48e538dfe9e7bdd3b547b11
Signed-off-by: Arun Prakash <app@codeaurora.org>
Currently the driver explicitly clears the HWO bit of the TRB
prepared for short packet or ZLP for EPs in both the directions,
and returns with non-zero code which breaks cleanup of completed
requests. The driver does this because it is written with the
understanding that the HW does not clear HWO for such packets.
But the databook section 4.2.3.2 says that the HW does not clear
HWO for such packets on the OUT EP only.
Now consider a device-to-host(USB IN) usecase like SW NCM, where
the u_ether driver looks for interrupt on every 5th request(say).
In between these 5 requests, if there is any packet of multiple
of MPS, then ZLP TRB will also be prepared. When the event is
received for the 5th request, we will only handle upto the ZLP
TRB because of the faulty logic described above. And only on the
event for the 10th request, we handle the 5th request (because of
IOC set on the 5th request). So, clearly the TRB cleanup logic is
lagging behind the HW actually completing the requests. When this
mismatch happens multiple times, there eventually comes a time
when the SW does not have any free requests anymore and hence
stall will be seen.
Fix this by returning with non-zero code only if the IOC bit is
set for the short packet or ZLP TRB, so that the cleanup routine
continues upto the TRB for which the event was raised.
Change-Id: I984e6de383993fc3c2da6b74147d6f50e081de34
Signed-off-by: Ajay Agarwal <ajaya@codeaurora.org>
Add property to configure the default trigger for the LED.
This will allow clients to use trigger APIs to configure
the brightness of the LED if needed.
Change-Id: I1db0a5f2d697c6ac6f6ae1296e43ae55509f2298
Signed-off-by: Veera Vegivada <vvegivad@codeaurora.org>
