On 5/13/25 05:28, Ekansh Gupta wrote:
> The initially allocated memory is not properly included in the pool,
> leading to potential issues with memory management. Set the number
> of pages to one to ensure that the initially allocated memory is
> correctly added to the Audio PD memory pool.
>
> Fi
On 5/13/25 05:28, Ekansh Gupta wrote:
> Remote heap allocations are not organized in a maintainable manner,
> leading to potential issues with memory management. As the remote
> heap allocations are maintained in fl mmaps list, the allocations
> will go away if the audio daemon process is killed bu
On 5/19/25 11:09, Dmitry Baryshkov wrote:
> On Mon, May 19, 2025 at 10:25:46AM +0100, Srinivas Kandagatla wrote:
>> On 5/13/25 05:28, Ekansh Gupta wrote:
>>> The fastrpc_buf_free function currently does not handle the case where
>>> the input buffer pointer (buf) is NU
On 5/13/25 05:28, Ekansh Gupta wrote:
> The fastrpc_buf_free function currently does not handle the case where
> the input buffer pointer (buf) is NULL. This can lead to a null pointer
> dereference, causing a crash or undefined behavior when the function
> attempts to access members of the buf str
On 07/04/2025 10:13, Ling Xu wrote:
在 3/21/2025 1:11 AM, Srinivas Kandagatla 写道:
On 20/03/2025 09:14, Ling Xu wrote:
The fastrpc driver has support for 5 types of remoteprocs. There are
some products which support GPDSP remoteprocs. Add changes to support
GPDSP remoteprocs.
Reviewed-by
t = true;
/* Create both device nodes so that we can allow both Signed
and Unsigned PD */
err = fastrpc_device_register(rdev, data, true,
domains[domain_id]);
Can you try this patch: only compile tested.
-->cut<-----
On 03/04/2025 05:44, Ekansh Gupta wrote:
On 4/2/2025 2:12 PM, Dmitry Baryshkov wrote:
On 02/04/2025 11:38, Ekansh Gupta wrote:
On 3/21/2025 5:53 PM, Srinivas Kandagatla wrote:
On 20/03/2025 18:43, Dmitry Baryshkov wrote:
On Thu, Mar 20, 2025 at 05:11:20PM +, Srinivas Kandagatla
On 21/03/2025 14:07, Dmitry Baryshkov wrote:
On Thu, Mar 20, 2025 at 05:11:20PM +, Srinivas Kandagatla wrote:
On 20/03/2025 09:14, Ling Xu wrote:
The fastrpc driver has support for 5 types of remoteprocs. There are
some products which support GPDSP remoteprocs. Add changes to support
On 20/03/2025 18:43, Dmitry Baryshkov wrote:
On Thu, Mar 20, 2025 at 05:11:20PM +, Srinivas Kandagatla wrote:
On 20/03/2025 09:14, Ling Xu wrote:
The fastrpc driver has support for 5 types of remoteprocs. There are
some products which support GPDSP remoteprocs. Add changes to support
80100 compatible
commit: 3419bdfd88e314bc5f80b02fa4651c81a0a85b57
Best regards,
--
Srinivas Kandagatla
On 30/12/2024 18:22, Dmitry Baryshkov wrote:
On Mon, Dec 30, 2024 at 04:15:42PM +, Srinivas Kandagatla wrote:
On Wed, 18 Dec 2024 15:54:27 +0530, Ekansh Gupta wrote:
This patch series adds the listed bug fixes that have been missing
in upstream fastRPC driver:
- Page address for
red buffer(copy buffer) is
> incorrect.
>
> [...]
Applied, thanks!
[1/2] misc: fastrpc: Fix registered buffer page address
commit: fa22a9743aece593fe9f1e0a0d6189a777d67e38
[2/2] misc: fastrpc: Fix copy buffer page size
commit: 58570026c7ac249bfbd90f9fcb7d2e0a74a106a1
Be
nsure proper cleanup in case of error.
>
>
Applied, thanks!
[1/1] misc: fastrpc: Deregister device nodes properly in error scenarios
commit: bd79a7dbb3625304abe3086de99168534e9552c5
Best regards,
--
Srinivas Kandagatla
> @@
>
> [...]
Applied, thanks!
[31/35] slimbus: messaging: Reorganize kerneldoc parameter names
commit: 52d3d7f7a77ee9afc6a846b415790e13e1434847
Best regards,
--
Srinivas Kandagatla
anks!
[1/2] misc: fastrpc: Add support for multiple PD from one process
commit: 0c3e383ce74b4239033fceb6f241cb09612f9547
[2/2] misc: fastrpc: Rename tgid and pid to client_id
commit: 9f86299512e04b24fb0b4a49849affbb397780e1
Best regards,
--
Srinivas Kandagatla
-by: Thomas Weißschuh
---
drivers/cxl/port.c | 2 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_psp.c | 2 +-
drivers/infiniband/hw/qib/qib_sysfs.c | 2 +-
drivers/mtd/spi-nor/sysfs.c | 2 +-
thanks for the patch.
Acked-by: Srinivas Kandagatla #nvmem
--srini
On 03/11/2024 17:03, Thomas Weißschuh wrote:
Stop abusing the is_bin_visible() callback to calculate the attribute
size. Instead use the new, dedicated bin_size() one.
Signed-off-by: Thomas Weißschuh
---
Thanks for the patch,
LGTM.
Acked-by: Srinivas Kandagatla
--srini
drivers
0/serial@3089/mcu/eeprom@a4: failed to match any schema
> with compatible: ['zii,rave-sp-eeprom']
>
> [...]
Applied, thanks!
[3/5] dt-bindings: nvmem: convert zii,rave-sp-eeprom.txt to yaml format
commit: 17d6f058403d4e3458ec9c7dae607c065cabe089
Best regards,
--
Srinivas Kandagatla
Thanks Ekansh for the patch,
On 08/08/2024 11:42, Ekansh Gupta wrote:
Memory intensive applications(which requires more tha 4GB) that wants
to offload tasks to DSP might have to split the tasks to multiple
user PD to make the resources available.
For every call to DSP, fastrpc driver passes the
>
> [...]
Applied, thanks!
[1/6] dt-bindings: misc: qcom,fastrpc: increase the max number of iommus
commit: 42a21d00aac515fad1f9a10052c6e9710c6f7813
[4/6] misc: fastrpc: Add support for cdsp1 remoteproc
commit: 590c42d9e278f8e6bf6d673f3101ac102369efc7
Best regards,
--
Srinivas Kandagatla
: Dmitry Baryshkov
Cc: Srinivas Kandagatla
Cc: Greg Kroah-Hartman
Reported-by: Joel Selvaraj
Link:
https://lore.kernel.org/r/9a9f5646-a554-4b65-8122-d212bb665...@umsystem.edu
Signed-off-by: Griffin Kroah-Hartman
---
Lets fix this properly by updating existing device tree entries and
> uAPI changes. This follows the usual practice established by the "DMA
> BUFFER SHARING FRAMEWORK" entry in the file.
>
>
> [...]
Applied, thanks!
[1/1] MAINTAINERS: CC dri-devel list on Qualcomm FastRPC patches
commit: 47bf4198bf386018e99673c1ce5dbd8e5eda293e
Best regards,
--
Srinivas Kandagatla
ntel-CI found a deadlock problem in a case of self-imported dma-buf [1].
>
> [...]
Applied, thanks!
[4/7] fastrpc: Don't assert held reservation lock for dma-buf mmapping
commit: 3f6b4c6f0bd0126f673f3578429239ae3860718b
Best regards,
--
Srinivas Kandagatla
audio codec device instead of just 3 codec devices for 3 dp ports.
Fix this by unregistering codecs on unbind.
Signed-off-by: Srinivas Kandagatla
---
drivers/gpu/drm/msm/dp/dp_audio.c | 12
drivers/gpu/drm/msm/dp/dp_audio.h | 2 ++
drivers/gpu/drm/msm/dp/dp_display.c | 1 +
3
On 31/08/2022 16:37, Dmitry Osipenko wrote:
Prepare fastrpc to the common dynamic dma-buf locking convention by
starting to use the unlocked versions of dma-buf API functions.
Signed-off-by: Dmitry Osipenko
---
LGTM,
Incase you plan to take it via another tree.
Acked-by: Srinivas
On 31/08/2022 16:37, Dmitry Osipenko wrote:
Prepare fastrpc to the common dynamic dma-buf locking convention by
starting to use the unlocked versions of dma-buf API functions.
Signed-off-by: Dmitry Osipenko
---
LGTM,
Incase you plan to take it via another tree.
Acked-by: Srinivas
Hi Krzysztof,
I seems to have missed this one,
On 25/08/2022 13:54, Krzysztof Kozlowski wrote:
Document compatibles for QFPROM used on IPQ8064 and SDM630. They are
compatible with generic QFPROM fallback.
Signed-off-by: Krzysztof Kozlowski
Applied thanks,
Srini
---
Documentation/devic
On 05/03/2021 14:45, Doug Anderson wrote:
Hi,
On Fri, Mar 5, 2021 at 2:28 AM Srinivas Kandagatla
wrote:
On 27/02/2021 00:26, Douglas Anderson wrote:
When running the latest kernel on an sc7180 with KASAN I got this
splat:
BUG: KASAN: slab-out-of-bounds in a6xx_gpu_init+0x618/0x644
On 27/02/2021 00:26, Douglas Anderson wrote:
When running the latest kernel on an sc7180 with KASAN I got this
splat:
BUG: KASAN: slab-out-of-bounds in a6xx_gpu_init+0x618/0x644
Read of size 4 at addr ff8088f36100 by task kworker/7:1/58
CPU: 7 PID: 58 Comm: kworker/7:1 Not tainted
n/ABI/stable/firewire-cdev| 4 +
Documentation/ABI/stable/sysfs-acpi-pmprofile | 22 +++--
Documentation/ABI/stable/sysfs-bus-firewire | 3 +
Documentation/ABI/stable/sysfs-bus-nvmem | 19 ++--
for nvmem parts:
Acked-by: Srinivas Kandagatla
--srini
Documentation/ABI/s
d here.
Documentation/devicetree/bindings/nvmem/nvmem.yaml | 2 ++
.../devicetree/bindings/nvmem/qcom,qfprom.yaml | 2 ++
for nvmem parts,
Acked-by: Srinivas Kandagatla
thanks,
--srini
___
dri-devel mailing list
dr
Herring
Documentation/devicetree/bindings/nvmem/nvmem-consumer.yaml | 2 ++
Documentation/devicetree/bindings/nvmem/nvmem.yaml | 2 ++
for nvmem parts,
Acked-by: Srinivas Kandagatla
thanks,
srini
___
dri-devel mailing list
dri-devel
On 01/08/17 13:28, Mark Brown wrote:
On Tue, Aug 01, 2017 at 01:24:03PM +0100, Srinivas Kandagatla wrote:
On 01/08/17 09:42, Arnaud Pouliquen wrote:
On 08/01/2017 12:49 AM, srinivas.kandaga...@linaro.org wrote:
I already used ADV7513 and i did not observe this limitation.
I had a look
On 01/08/17 09:42, Arnaud Pouliquen wrote:
Hello Srinivas,
On 08/01/2017 12:49 AM, srinivas.kandaga...@linaro.org wrote:
From: Srinivas Kandagatla
ADV7533 only supports audio samples word width from 16-24 bits.
This patch restricts the audio sample sizes to the supported ones,
so that
From: Srinivas Kandagatla
This patch adds option to allow hdmi-codec drivers to restrict
the audio sample size based on the values that are suppored in hardware.
First patch is adding that formats option to hdmi_codec_pdata and
second patch is a fix in adv7511 codec driver which only supports
From: Srinivas Kandagatla
Currently hdmi client drivers does have means to limit the
sample sizes that it can only support. Having formats parameter
option would solve this.
This issue was noticed on DB410c board when adv7511 hdmi codec driver
failed to play a 32 bits audio samples, as it does
From: Srinivas Kandagatla
ADV7533 only supports audio samples word width from 16-24 bits.
This patch restricts the audio sample sizes to the supported ones,
so that sound card does not report wrong list of supported hwparms.
Without this patch aplay would fail when playing a 32 bit audio
On 27/07/17 11:34, Jyri Sarha wrote:
On 07/17/17 17:02, srinivas.kandaga...@linaro.org wrote:
From: Srinivas Kandagatla
Currently hdmi client drivers does have means to limit the
sample sizes that it can only support. Having formats parameter
option would solve this.
This issue was noticed
From: Srinivas Kandagatla
ADV7533 only supports audio samples word width from 16-24 bits.
This patch restricts the audio sample sizes to the supported ones,
so that sound card does not report wrong list of supported hwparms.
Without this patch aplay would fail when playing a 32 bit audio
From: Srinivas Kandagatla
Currently hdmi client drivers does have means to limit the
sample sizes that it can only support. Having formats parameter
option would solve this.
This issue was noticed on DB410c board when adv7511 hdmi codec driver
failed to play a 32 bits audio samples, as it does
From: Srinivas Kandagatla
This patch adds option to allow hdmi-codec drivers to restrict
the audio sample size based on the values that are suppored in hardware.
First patch is adding that formats option to hdmi_codec_pdata and
second patch is a fix in adv7511 codec driver which only supports
Few Minor comments below..
On 23/08/16 06:50, John Stultz wrote:
> This patch adds support to Audio for both adv7511 and adv7533
> bridge chips.
>
> This patch was originally from [1] by Lars-Peter Clausen
> and was adapted by Archit Taneja and
> Srinivas Kandagatla .
Hi John,
On 23/08/16 06:50, John Stultz wrote:
> This is an initial swing at getting the adv7511 hdmi bridge
> audio support reviewed.
>
> I've taken the core audio work done by Lars-Peter Clausen, and
> adapted by Srinivas Kandagatla and Archit Taneja, and tried to
> re
This patch adds support to generic audio codec via
ASoC hdmi-codec infrastucture which is merged recently.
Signed-off-by: Srinivas Kandagatla
---
Changes since v1:
-Fixed typo for 44.1Kz case spotted by Jyri Sarha
drivers/gpu/drm/msm/Kconfig | 1 +
drivers/gpu/drm/msm/hdmi/hdmi.c
On 06/06/16 13:23, Jyri Sarha wrote:
> On 06/03/16 16:56, Srinivas Kandagatla wrote:
>> >This patch adds support to generic audio codec via
>> >ASoC hdmi-codec infrastucture which is merged recently.
>> >
> I know nothing about msm HW, but from the hdmi-codec
This patch adds support to generic audio codec via
ASoC hdmi-codec infrastucture which is merged recently.
Signed-off-by: Srinivas Kandagatla
---
drivers/gpu/drm/msm/Kconfig | 1 +
drivers/gpu/drm/msm/hdmi/hdmi.c | 120 +++-
drivers/gpu/drm/msm/hdmi
On 17/08/15 08:52, Jani Nikula wrote:
> On Fri, 14 Aug 2015, Srinivas Kandagatla
> wrote:
>> This patch adds support to get edid way early before the connector is
>> created, this is mainly used for panel drivers to auto-probe the panel
>> based on the vendor
This patch checks if the panel node is disabled in DT or not, this would
let us return proper error code so that the driver could stop panel
specific intialization.
Signed-off-by: Srinivas Kandagatla
---
drivers/gpu/drm/msm/mdp/mdp4/mdp4_kms.c | 5 +
1 file changed, 5 insertions(+)
diff
elated things. This patch adds two things.
1> moves the panel specific intialization only if the panel is detected
2> let the driver continue with hdmi intialization if detect_panel()
return -ENODEV.
Signed-off-by: Srinivas Kandagatla
---
drivers/gpu/drm/msm/mdp/mdp4/mdp
driver
would mark the panel DT node as disabled so that the drm driver would
be able to take right decision based on that panel node status.
Signed-off-by: Srinivas Kandagatla
---
drivers/gpu/drm/panel/panel-simple.c | 83 +++-
1 file changed, 81 insertions(+)
This patch exports edid_vendor() match function, so that other drivers
could use it for matching the vendor id.
Signed-off-by: Srinivas Kandagatla
---
drivers/gpu/drm/drm_edid.c | 4 ++--
include/drm/drm_crtc.h | 1 +
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers
This patch adds support to get edid way early before the connector is
created, this is mainly used for panel drivers to auto-probe the panel
based on the vendor and product id from EDID.
Signed-off-by: Srinivas Kandagatla
---
drivers/gpu/drm/drm_edid.c | 8
include/drm/drm_crtc.h
s to get more inputs and comments.
Thanks,
srini
Srinivas Kandagatla (5):
drm/edid: Add support to get edid early
drm/edid: export edid_vendor()
drm/panel: simple-panel: Add panel picker support.
drm/msm: mdp4 lvds: continue if the panel is not connected
drm/msm: mdp4 lvds: Che
On 10/08/15 14:26, Thierry Reding wrote:
> On Mon, Aug 10, 2015 at 02:15:18PM +0100, Srinivas Kandagatla wrote:
>>
>>
>> On 10/08/15 13:38, Thierry Reding wrote:
>>> On Mon, Aug 10, 2015 at 12:59:34PM +0100, Srinivas Kandagatla wrote:
>>>> This patch mo
On 10/08/15 14:33, Thierry Reding wrote:
> On Mon, Aug 10, 2015 at 02:18:15PM +0100, Srinivas Kandagatla wrote:
>>
>>
>> On 10/08/15 13:49, Thierry Reding wrote:
>>> On Mon, Aug 10, 2015 at 12:59:49PM +0100, Srinivas Kandagatla wrote:
>>>> This patch up
On 10/08/15 13:49, Thierry Reding wrote:
> On Mon, Aug 10, 2015 at 12:59:49PM +0100, Srinivas Kandagatla wrote:
>> This patch updates the bindings to discourage the usage of non standard
>> clock names, this will help in projects focused on upstreaming.
>>
>> Thes
On 10/08/15 13:38, Thierry Reding wrote:
> On Mon, Aug 10, 2015 at 12:59:34PM +0100, Srinivas Kandagatla wrote:
>> This patch modifies the driver to support standard gpio properties along
>> with deprecated properties. This will help us upstream and cleanup the
>> non-sta
: Srinivas Kandagatla
---
drivers/gpu/drm/msm/hdmi/hdmi.c | 29 -
1 file changed, 24 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/msm/hdmi/hdmi.c b/drivers/gpu/drm/msm/hdmi/hdmi.c
index e918889..c454d32 100644
--- a/drivers/gpu/drm/msm/hdmi/hdmi.c
+++ b/drivers
This patch updates the bindings to discourage the usage of non standard
clock names, this will help in projects focused on upstreaming.
These deprecated properties are still supported but will be remove over
the time.
Signed-off-by: Srinivas Kandagatla
---
Documentation/devicetree/bindings/drm
This patch updates the bindings to include the clock names used in the
driver, this would make it easy to add deprecated warning once we move
to use standard clock properties.
Signed-off-by: Srinivas Kandagatla
---
Documentation/devicetree/bindings/drm/msm/hdmi.txt | 13 +
1 file
This patch modifies the driver to support standard gpio properties along
with deprecated properties. This will help us upstream and cleanup the
non-standard properties over the time.
Signed-off-by: Srinivas Kandagatla
---
drivers/gpu/drm/msm/hdmi/hdmi.c | 35
This patch updates the bindings to discourage the usage of non standard
gpio properites, this will help in projects focused on upstreaming.
These deprecated properties are still supported but will be remove over
the time.
Signed-off-by: Srinivas Kandagatla
---
Documentation/devicetree/bindings
patches with more standard
dt properites
Old style properties are still supported and will be removed
once we see no users for it.
I have tested these changes on IFC6410.
Thanks,
srini
Srinivas Kandagatla (5):
drm/msm/hdmi: deprecate non standard gpio properties.
drm/msm/hdmi: make use of
Prepare the panel before it's enabled and un-prepare after disable, this
will make sure that the regulators are switched on and off correctly.
Tested it on APQ8064 based IFC6410 with panel.
Signed-off-by: Srinivas Kandagatla
---
drivers/gpu/drm/msm/mdp/mdp4/mdp4_lcdc_encoder.c | 8 ++
On 22/06/15 15:54, Archit Taneja wrote:
> Decrement device node refcount if of_get_child_by_name is successfully
> called.
>
> Signed-off-by: Archit Taneja
> ---
> drivers/gpu/drm/msm/dsi/dsi_host.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/msm/dsi/dsi_host.c
On 21/09/12 19:37, Leela Krishna Amudala wrote:
> This patch is a part of moving the driver to support DT style probing
> of exynos drm device. The compatible name should match with the
> entry in the dtsi file.
>
> Signed-off-by: Leela Krishna Amudala
> ---
> drivers/gpu/drm/exynos/exynos_drm_dr
On 21/09/12 19:37, Leela Krishna Amudala wrote:
> This patch is a part of moving the driver to support DT style probing
> of exynos drm device. The compatible name should match with the
> entry in the dtsi file.
>
> Signed-off-by: Leela Krishna Amudala
> ---
> drivers/gpu/drm/exynos/exynos_drm_dr
67 matches
Mail list logo
