From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Abhinav Kumar <quic_abhinavk@quicinc.com>
Cc: markyacoub@chromium.org, liviu.dudau@arm.com,
dri-devel@lists.freedesktop.org, swboyd@chromium.org,
seanpaul@chromium.org, dmitry.baryshkov@linaro.org,
quic_jesszhan@quicinc.com, quic_aravindh@quicinc.com,
freedreno@lists.freedesktop.org
Subject: Re: [PATCH v4 02/20] drm: introduce drm_writeback_connector_init_with_encoder() API
Date: Sun, 24 Apr 2022 17:47:38 +0300 [thread overview]
Message-ID: <YmVjCssUV89V5BOR@pendragon.ideasonboard.com> (raw)
In-Reply-To: <1650668815-7048-3-git-send-email-quic_abhinavk@quicinc.com>
Hi Abhinav,
Thank you for the patch.
On Fri, Apr 22, 2022 at 04:06:37PM -0700, Abhinav Kumar wrote:
> For vendors drivers which pass an already allocated and
> initialized encoder especially for cases where the encoder
> hardware is shared OR the writeback encoder shares the resources
> with the rest of the display pipeline introduce a new API,
> drm_writeback_connector_init_with_encoder() which expects
> an initialized encoder as a parameter and only sets up the
> writeback connector.
>
> changes in v4:
> - removed the possible_crtcs part
>
> changes in v5:
> - reorder this change to come before in the series
> to avoid incorrect functionality in subsequent changes
> - continue using struct drm_encoder instead of
> struct drm_encoder * and switch it in next change
>
> changes in v6:
> - remove drm_writeback_connector_setup() and instead
> directly call drm_writeback_connector_init_with_encoder()
> - fix a drm_writeback_connector typo and function doc which
> incorrectly shows that the function accepts enc_helper_funcs
> - pass encoder as a parameter explicitly to the new API
> for better readability
>
> changes in v7:
> - fix the function doc slightly as suggested by Liviu
>
> Reviewed-by: Liviu Dudau <liviu.dudau@arm.com>
> Signed-off-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
> drivers/gpu/drm/drm_writeback.c | 72 +++++++++++++++++++++++++++++++++--------
> include/drm/drm_writeback.h | 6 ++++
> 2 files changed, 64 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_writeback.c b/drivers/gpu/drm/drm_writeback.c
> index 9e0b845..92658ad 100644
> --- a/drivers/gpu/drm/drm_writeback.c
> +++ b/drivers/gpu/drm/drm_writeback.c
> @@ -178,6 +178,62 @@ int drm_writeback_connector_init(struct drm_device *dev,
> const u32 *formats, int n_formats,
> u32 possible_crtcs)
> {
> + int ret = 0;
> +
> + drm_encoder_helper_add(&wb_connector->encoder, enc_helper_funcs);
> +
> + wb_connector->encoder.possible_crtcs = possible_crtcs;
> +
> + ret = drm_encoder_init(dev, &wb_connector->encoder,
> + &drm_writeback_encoder_funcs,
> + DRM_MODE_ENCODER_VIRTUAL, NULL);
> + if (ret)
> + return ret;
> +
> + ret = drm_writeback_connector_init_with_encoder(dev, wb_connector, &wb_connector->encoder,
> + con_funcs, formats, n_formats);
> +
> + if (ret)
> + drm_encoder_cleanup(&wb_connector->encoder);
> +
> + return ret;
> +}
> +EXPORT_SYMBOL(drm_writeback_connector_init);
> +
> +/**
> + * drm_writeback_connector_init_with_encoder - Initialize a writeback connector and its properties
> + * using the encoder which already assigned and initialized
That sounds a bit convoluted to me. How about
* drm_writeback_connector_init_with_encoder - Initialize a writeback connector
* with a custom encoder
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> + *
> + * @dev: DRM device
> + * @wb_connector: Writeback connector to initialize
> + * @enc: handle to the already initialized drm encoder
> + * @con_funcs: Connector funcs vtable
> + * @formats: Array of supported pixel formats for the writeback engine
> + * @n_formats: Length of the formats array
> + *
> + * This function creates the writeback-connector-specific properties if they
> + * have not been already created, initializes the connector as
> + * type DRM_MODE_CONNECTOR_WRITEBACK, and correctly initializes the property
> + * values.
> + *
> + * This function assumes that the drm_writeback_connector's encoder has already been
> + * created and initialized before invoking this function.
> + *
> + * In addition, this function also assumes that callers of this API will manage
> + * assigning the encoder helper functions, possible_crtcs and any other encoder
> + * specific operation.
> + *
> + * Drivers should always use this function instead of drm_connector_init() to
> + * set up writeback connectors if they want to manage themselves the lifetime of the
> + * associated encoder.
> + *
> + * Returns: 0 on success, or a negative error code
> + */
> +int drm_writeback_connector_init_with_encoder(struct drm_device *dev,
> + struct drm_writeback_connector *wb_connector, struct drm_encoder *enc,
> + const struct drm_connector_funcs *con_funcs, const u32 *formats,
> + int n_formats)
> +{
> struct drm_property_blob *blob;
> struct drm_connector *connector = &wb_connector->base;
> struct drm_mode_config *config = &dev->mode_config;
> @@ -191,15 +247,6 @@ int drm_writeback_connector_init(struct drm_device *dev,
> if (IS_ERR(blob))
> return PTR_ERR(blob);
>
> - drm_encoder_helper_add(&wb_connector->encoder, enc_helper_funcs);
> -
> - wb_connector->encoder.possible_crtcs = possible_crtcs;
> -
> - ret = drm_encoder_init(dev, &wb_connector->encoder,
> - &drm_writeback_encoder_funcs,
> - DRM_MODE_ENCODER_VIRTUAL, NULL);
> - if (ret)
> - goto fail;
>
> connector->interlace_allowed = 0;
>
> @@ -208,8 +255,7 @@ int drm_writeback_connector_init(struct drm_device *dev,
> if (ret)
> goto connector_fail;
>
> - ret = drm_connector_attach_encoder(connector,
> - &wb_connector->encoder);
> + ret = drm_connector_attach_encoder(connector, enc);
> if (ret)
> goto attach_fail;
>
> @@ -238,12 +284,10 @@ int drm_writeback_connector_init(struct drm_device *dev,
> attach_fail:
> drm_connector_cleanup(connector);
> connector_fail:
> - drm_encoder_cleanup(&wb_connector->encoder);
> -fail:
> drm_property_blob_put(blob);
> return ret;
> }
> -EXPORT_SYMBOL(drm_writeback_connector_init);
> +EXPORT_SYMBOL(drm_writeback_connector_init_with_encoder);
>
> int drm_writeback_set_fb(struct drm_connector_state *conn_state,
> struct drm_framebuffer *fb)
> diff --git a/include/drm/drm_writeback.h b/include/drm/drm_writeback.h
> index 5d9263f..bb306fa 100644
> --- a/include/drm/drm_writeback.h
> +++ b/include/drm/drm_writeback.h
> @@ -153,6 +153,12 @@ int drm_writeback_connector_init(struct drm_device *dev,
> const u32 *formats, int n_formats,
> u32 possible_crtcs);
>
> +int drm_writeback_connector_init_with_encoder(struct drm_device *dev,
> + struct drm_writeback_connector *wb_connector,
> + struct drm_encoder *enc,
> + const struct drm_connector_funcs *con_funcs, const u32 *formats,
> + int n_formats);
> +
> int drm_writeback_set_fb(struct drm_connector_state *conn_state,
> struct drm_framebuffer *fb);
>
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2022-04-24 14:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 23:06 [PATCH v4 00/20] Add writeback block support for DPU Abhinav Kumar
2022-04-22 23:06 ` [PATCH v4 01/20] drm: allow passing possible_crtcs to drm_writeback_connector_init() Abhinav Kumar
2022-04-24 14:19 ` Laurent Pinchart
2022-04-22 23:06 ` [PATCH v4 02/20] drm: introduce drm_writeback_connector_init_with_encoder() API Abhinav Kumar
2022-04-24 14:47 ` Laurent Pinchart [this message]
2022-04-22 23:06 ` [PATCH v4 03/20] drm: allow real encoder to be passed for drm_writeback_connector Abhinav Kumar
2022-04-24 14:50 ` Laurent Pinchart
2022-04-24 18:12 ` Abhinav Kumar
2022-04-24 18:23 ` [Freedreno] " Abhinav Kumar
2022-04-24 19:59 ` Laurent Pinchart
2022-04-24 21:12 ` Abhinav Kumar
2022-04-25 0:02 ` Abhinav Kumar
2022-04-25 10:50 ` Dmitry Baryshkov
2022-04-25 16:25 ` Abhinav Kumar
2022-04-25 17:32 ` Laurent Pinchart
2022-04-25 17:48 ` Abhinav Kumar
2022-04-25 18:20 ` Laurent Pinchart
2022-04-22 23:06 ` [PATCH v4 04/20] drm/msm/dpu: add writeback blocks to the sm8250 DPU catalog Abhinav Kumar
2022-04-22 23:06 ` [PATCH v4 05/20] drm/msm/dpu: add reset_intf_cfg operation for dpu_hw_ctl Abhinav Kumar
2022-04-22 23:06 ` [PATCH v4 06/20] drm/msm/dpu: rename dpu_hw_pipe_cdp_cfg to dpu_hw_cdp_cfg Abhinav Kumar
2022-04-22 23:06 ` [PATCH v4 07/20] drm/msm/dpu: add dpu_hw_wb abstraction for writeback blocks Abhinav Kumar
2022-04-22 23:06 ` [PATCH v4 08/20] drm/msm/dpu: add writeback blocks to DPU RM Abhinav Kumar
2022-04-22 23:06 ` [PATCH v4 09/20] drm/msm/dpu: add changes to support writeback in hw_ctl Abhinav Kumar
2022-04-22 23:06 ` [PATCH v4 10/20] drm/msm/dpu: add an API to reset the encoder related hw blocks Abhinav Kumar
2022-04-22 23:06 ` [PATCH v4 11/20] drm/msm/dpu: make changes to dpu_encoder to support virtual encoder Abhinav Kumar
2022-04-26 0:18 ` Dmitry Baryshkov
2022-04-22 23:06 ` [PATCH v4 12/20] drm/msm/dpu: add encoder operations to prepare/cleanup wb job Abhinav Kumar
2022-04-22 23:06 ` [PATCH v4 13/20] drm/msm/dpu: move _dpu_plane_get_qos_lut to dpu_hw_util file Abhinav Kumar
2022-04-22 23:06 ` [PATCH v4 14/20] drm/msm/dpu: introduce the dpu_encoder_phys_* for writeback Abhinav Kumar
2022-04-22 23:06 ` [PATCH v4 15/20] drm/msm/dpu: add the writeback connector layer Abhinav Kumar
2022-04-22 23:06 ` [PATCH v4 16/20] drm/msm/dpu: initialize dpu encoder and connector for writeback Abhinav Kumar
2022-04-22 23:06 ` [PATCH v4 17/20] drm/msm/dpu: gracefully handle null fb commits " Abhinav Kumar
2022-04-22 23:06 ` [PATCH v4 18/20] drm/msm/dpu: add writeback blocks to the display snapshot Abhinav Kumar
2022-04-22 23:06 ` [PATCH v4 19/20] drm/msm/dpu: add wb_idx to existing DRM prints in dpu_encoder Abhinav Kumar
2022-04-22 23:06 ` [PATCH v4 20/20] drm/msm/dpu: add wb_idx to DRM traces " Abhinav Kumar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YmVjCssUV89V5BOR@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=liviu.dudau@arm.com \
--cc=markyacoub@chromium.org \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_aravindh@quicinc.com \
--cc=quic_jesszhan@quicinc.com \
--cc=seanpaul@chromium.org \
--cc=swboyd@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.