Home
last modified time | relevance | path

Searched hist:"6 ca91bb43a63ad036a05491ad662aa18feb0e4ce" (Results 1 – 5 of 5) sorted by relevance

/linux/drivers/gpu/drm/xlnx/
H A Dzynqmp_dp.hdiff 6ca91bb43a63ad036a05491ad662aa18feb0e4ce Fri Aug 06 13:29:52 CEST 2021 Laurent Pinchart <laurent.pinchart@ideasonboard.com> drm: xlnx: zynqmp_dpsub: Manage DP and DISP allocations manually

The zynqmp_disp and zynqmp_dp structures are allocated with
drmm_kzalloc(). While this simplifies management of memory, it requires
a DRM device, which will not be available at probe time when the DP
bridge will be used standalone, with a DRM device in the PL. To prepare
for this, switch to manual allocation for zynqmp_disp and zynqmp_dp. The
cleanup still uses the DRM managed infrastructure, but one level up, at
the top level. This will be addressed separately.

Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
H A Dzynqmp_disp.hdiff 6ca91bb43a63ad036a05491ad662aa18feb0e4ce Fri Aug 06 13:29:52 CEST 2021 Laurent Pinchart <laurent.pinchart@ideasonboard.com> drm: xlnx: zynqmp_dpsub: Manage DP and DISP allocations manually

The zynqmp_disp and zynqmp_dp structures are allocated with
drmm_kzalloc(). While this simplifies management of memory, it requires
a DRM device, which will not be available at probe time when the DP
bridge will be used standalone, with a DRM device in the PL. To prepare
for this, switch to manual allocation for zynqmp_disp and zynqmp_dp. The
cleanup still uses the DRM managed infrastructure, but one level up, at
the top level. This will be addressed separately.

Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
H A Dzynqmp_dpsub.cdiff 6ca91bb43a63ad036a05491ad662aa18feb0e4ce Fri Aug 06 13:29:52 CEST 2021 Laurent Pinchart <laurent.pinchart@ideasonboard.com> drm: xlnx: zynqmp_dpsub: Manage DP and DISP allocations manually

The zynqmp_disp and zynqmp_dp structures are allocated with
drmm_kzalloc(). While this simplifies management of memory, it requires
a DRM device, which will not be available at probe time when the DP
bridge will be used standalone, with a DRM device in the PL. To prepare
for this, switch to manual allocation for zynqmp_disp and zynqmp_dp. The
cleanup still uses the DRM managed infrastructure, but one level up, at
the top level. This will be addressed separately.

Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
H A Dzynqmp_dp.cdiff 6ca91bb43a63ad036a05491ad662aa18feb0e4ce Fri Aug 06 13:29:52 CEST 2021 Laurent Pinchart <laurent.pinchart@ideasonboard.com> drm: xlnx: zynqmp_dpsub: Manage DP and DISP allocations manually

The zynqmp_disp and zynqmp_dp structures are allocated with
drmm_kzalloc(). While this simplifies management of memory, it requires
a DRM device, which will not be available at probe time when the DP
bridge will be used standalone, with a DRM device in the PL. To prepare
for this, switch to manual allocation for zynqmp_disp and zynqmp_dp. The
cleanup still uses the DRM managed infrastructure, but one level up, at
the top level. This will be addressed separately.

Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
H A Dzynqmp_disp.cdiff 6ca91bb43a63ad036a05491ad662aa18feb0e4ce Fri Aug 06 13:29:52 CEST 2021 Laurent Pinchart <laurent.pinchart@ideasonboard.com> drm: xlnx: zynqmp_dpsub: Manage DP and DISP allocations manually

The zynqmp_disp and zynqmp_dp structures are allocated with
drmm_kzalloc(). While this simplifies management of memory, it requires
a DRM device, which will not be available at probe time when the DP
bridge will be used standalone, with a DRM device in the PL. To prepare
for this, switch to manual allocation for zynqmp_disp and zynqmp_dp. The
cleanup still uses the DRM managed infrastructure, but one level up, at
the top level. This will be addressed separately.

Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>