diff options
| author | Marek Szyprowski <m.szyprowski@samsung.com> | 2020-05-28 16:03:26 +0200 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab+huawei@kernel.org> | 2020-06-11 19:20:09 +0200 |
| commit | cc8c0363ddce6308168d8223378ca884c213f280 (patch) | |
| tree | b5e91b0aba512a7655b18f0f9fbab0c03a9fb7f4 /init | |
| parent | 15168b204691aa8cbff043c1151e9dbfdd088364 (diff) | |
| download | linux-stable-cc8c0363ddce6308168d8223378ca884c213f280.tar.gz linux-stable-cc8c0363ddce6308168d8223378ca884c213f280.tar.bz2 linux-stable-cc8c0363ddce6308168d8223378ca884c213f280.zip | |
media: s5p-mfc: Properly handle dma_parms for the allocated devices
Commit 9495b7e92f71 ("driver core: platform: Initialize dma_parms for
platform devices") in v5.7-rc5 added allocation of dma_parms structure to
all platform devices. Then vb2_dma_contig_set_max_seg_size() have been
changed not to allocate dma_parms structure and rely on the one allocated
by the device core. Lets allocate the needed structure also for the
devices created for the 2 MFC device memory ports.
Reported-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Suggested-by: Ulf Hansson <ulf.hansson@linaro.org>
Fixes: 9495b7e92f71 ("driver core: platform: Initialize dma_parms for platform devices")
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions