All of lore.kernel.org
 help / color / mirror / Atom feed
From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.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: [Freedreno] [PATCH v4 03/20] drm: allow real encoder to be passed for drm_writeback_connector
Date: Sun, 24 Apr 2022 17:02:49 -0700	[thread overview]
Message-ID: <d8641c24-0235-e5a8-0586-53b8abf65de8@quicinc.com> (raw)
In-Reply-To: <578f1db0-a32b-4379-2621-92f67daa85c0@quicinc.com>

Hi Laurent

On 4/24/2022 2:12 PM, Abhinav Kumar wrote:
> Hi Laurent
> 
> On 4/24/2022 12:59 PM, Laurent Pinchart wrote:
>> Hi Abhinav,
>>
>> On Sun, Apr 24, 2022 at 11:23:20AM -0700, Abhinav Kumar wrote:
>>> On 4/24/2022 11:12 AM, Abhinav Kumar wrote:
>>>> On 4/24/2022 7:50 AM, Laurent Pinchart wrote:
>>>>> On Fri, Apr 22, 2022 at 04:06:38PM -0700, Abhinav Kumar wrote:
>>>>>> For some vendor driver implementations, display hardware can
>>>>>> be shared between the encoder used for writeback and the physical
>>>>>> display.
>>>>>>
>>>>>> In addition resources such as clocks and interrupts can
>>>>>> also be shared between writeback and the real encoder.
>>>>>>
>>>>>> To accommodate such vendor drivers and hardware, allow
>>>>>> real encoder to be passed for drm_writeback_connector.
>>>>>>
>>>>>> For existing clients, drm_writeback_connector_init() will use
>>>>>> an internal_encoder under the hood and hence no changes will
>>>>>> be needed.
>>>>>>
>>>>>> changes in v7:
>>>>>>      - move this change before the vc4 change in the series
>>>>>>        to minimize the changes to vendor drivers in drm core
>>>>>>        changes
>>>>>
>>>>> Why is this needed ? The drm_writeback_connector functions don't need
>>>>> the drm_encoder after drm_writeback_connector_init() (or
>>>>> drm_writeback_connector_init_with_encoder()) returns.
>>>>>
>>>>
>>>> Sorry I didnt follow this comment. This change log is incorrect, so
>>>> after changing the previous change in the series and modifying this, no
>>>> further changes are needed to vc4, so I decided to drop the next 
>>>> change.
>>>> So this change log is incorrect. I can remove this.
>>>>
>>>> Is that what you meant?
>>>
>>> So till the previous change, the only user of
>>> drm_writeback_connector_init_with_encoder() was
>>> drm_writeback_connector_init() which was still passing its own
>>> internal_encoder.
>>>
>>> Only if the wb_connector->encoder is changed to a pointer, other vendor
>>> drivers can pass their own encoder to
>>> drm_writeback_connector_init_with_encoder().
>>>
>>> Hence you are right that drm_writeback_connector functions do not need
>>> drm_encoder after init() returns, but till this change is done, other
>>> vendor drivers cannot directly call
>>> drm_writeback_connector_init_with_encoder() because the encoder will not
>>> be valid till then.
>>
>> Users of drm_writeback_connector_init_with_encoder() handle the encoder
>> themselves, they can simply ignore drm_writeback_connector.encoder. The
>> documentation of the encoder field needs to be updated though (I'd do so
>> in the previous patch), to clearly mention that the field is valid only
>> when using drm_writeback_connector_init(), not when calling
>> drm_writeback_connector_init_with_encoder().
> 
> So you are suggesting to drop this change and just update the doc in 
> patch 2?
> 
> If so, I dont think it would be correct to assume that even though 
> drm_writeback_connector_init_with_encoder() is used 
> drm_writeback_connector.encoder should not be used.
> 
> The reason is that, lets consider, prepare_wb_job() and 
> cleanup_writeback_job().
> 
> These pass only the connector to the vendor hooks.
> 
> 1126      *
> 1127      * This callback is used by the atomic modeset helpers.
> 1128      */
> 1129     int (*prepare_writeback_job)(struct drm_writeback_connector 
> *connector,
> 1130                      struct drm_writeback_job *job);
> 
> Now, if you assume connector->encoder is not valid, this adds more 
> confusion because now we are putting an extra condition that 
> connector->encoder is not valid anymore.
> 
> Thats why I think we should leave it as-it-is to not allow room for such 
> discrepancies.

I was able to abandon this change and still make writeback work with 
just trivial changes to MSM driver.

So we are okay to drop this change as you requested and let the vendor 
driver manage the encoder completely.

If you do think that this change is worth re-visiting sometime, let me 
know I can absorb it as a separate change.

Thanks

Abhinav
> 
>>
>>> Hope this clarifies it.
>>>
>>>>>> Signed-off-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
>>>>>> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>>>>>> ---
>>>>>>    drivers/gpu/drm/drm_writeback.c | 18 ++++++++++++------
>>>>>>    drivers/gpu/drm/vc4/vc4_txp.c   |  4 ++--
>>>>>>    include/drm/drm_writeback.h     | 22 ++++++++++++++++++++--
>>>>>>    3 files changed, 34 insertions(+), 10 deletions(-)
>>>>>>
>>>>>> diff --git a/drivers/gpu/drm/drm_writeback.c
>>>>>> b/drivers/gpu/drm/drm_writeback.c
>>>>>> index 92658ad..0538674 100644
>>>>>> --- a/drivers/gpu/drm/drm_writeback.c
>>>>>> +++ b/drivers/gpu/drm/drm_writeback.c
>>>>>> @@ -180,21 +180,21 @@ int drm_writeback_connector_init(struct
>>>>>> drm_device *dev,
>>>>>>    {
>>>>>>        int ret = 0;
>>>>>> -    drm_encoder_helper_add(&wb_connector->encoder, 
>>>>>> enc_helper_funcs);
>>>>>> +    drm_encoder_helper_add(&wb_connector->internal_encoder, 
>>>>>> enc_helper_funcs);
>>>>>> -    wb_connector->encoder.possible_crtcs = possible_crtcs;
>>>>>> +    wb_connector->internal_encoder.possible_crtcs = possible_crtcs;
>>>>>> -    ret = drm_encoder_init(dev, &wb_connector->encoder,
>>>>>> +    ret = drm_encoder_init(dev, &wb_connector->internal_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);
>>>>>> +    ret = drm_writeback_connector_init_with_encoder(dev, 
>>>>>> wb_connector,
>>>>>> +            &wb_connector->internal_encoder, con_funcs, formats, 
>>>>>> n_formats);
>>>>>>        if (ret)
>>>>>> -        drm_encoder_cleanup(&wb_connector->encoder);
>>>>>> +        drm_encoder_cleanup(&wb_connector->internal_encoder);
>>>>>>        return ret;
>>>>>>    }
>>>>>> @@ -239,6 +239,12 @@ int 
>>>>>> drm_writeback_connector_init_with_encoder(struct drm_device *dev,
>>>>>>        struct drm_mode_config *config = &dev->mode_config;
>>>>>>        int ret = create_writeback_properties(dev);
>>>>>> +    /*
>>>>>> +     * Assign the encoder passed to this API to the 
>>>>>> wb_connector's encoder.
>>>>>> +     * For drm_writeback_connector_init(), this shall be the 
>>>>>> internal_encoder
>>>>>> +     */
>>>>>> +    wb_connector->encoder = enc;
>>>>>> +
>>>>>>        if (ret != 0)
>>>>>>            return ret;
>>>>>> diff --git a/drivers/gpu/drm/vc4/vc4_txp.c 
>>>>>> b/drivers/gpu/drm/vc4/vc4_txp.c
>>>>>> index 3447eb6..7e063a9 100644
>>>>>> --- a/drivers/gpu/drm/vc4/vc4_txp.c
>>>>>> +++ b/drivers/gpu/drm/vc4/vc4_txp.c
>>>>>> @@ -159,7 +159,7 @@ struct vc4_txp {
>>>>>>    static inline struct vc4_txp *encoder_to_vc4_txp(struct 
>>>>>> drm_encoder *encoder)
>>>>>>    {
>>>>>> -    return container_of(encoder, struct vc4_txp, connector.encoder);
>>>>>> +    return container_of(encoder, struct vc4_txp, 
>>>>>> connector.internal_encoder);
>>>>>>    }
>>>>>>    static inline struct vc4_txp *connector_to_vc4_txp(struct  
>>>>>> drm_connector *conn)
>>>>>> @@ -507,7 +507,7 @@ static int vc4_txp_bind(struct device *dev, 
>>>>>> struct device *master, void *data)
>>>>>>        if (ret)
>>>>>>            return ret;
>>>>>> -    encoder = &txp->connector.encoder;
>>>>>> +    encoder = txp->connector.encoder;
>>>>>>        encoder->possible_crtcs = drm_crtc_mask(crtc);
>>>>>>        ret = devm_request_irq(dev, irq, vc4_txp_interrupt, 0,
>>>>>> diff --git a/include/drm/drm_writeback.h 
>>>>>> b/include/drm/drm_writeback.h
>>>>>> index bb306fa..3fbae9d 100644
>>>>>> --- a/include/drm/drm_writeback.h
>>>>>> +++ b/include/drm/drm_writeback.h
>>>>>> @@ -25,13 +25,31 @@ struct drm_writeback_connector {
>>>>>>        struct drm_connector base;
>>>>>>        /**
>>>>>> -     * @encoder: Internal encoder used by the connector to fulfill
>>>>>> +     * @encoder: handle to drm_encoder used by the connector to 
>>>>>> fulfill
>>>>>>         * the DRM framework requirements. The users of the
>>>>>>         * @drm_writeback_connector control the behaviour of the 
>>>>>> @encoder
>>>>>>         * by passing the @enc_funcs parameter to 
>>>>>> drm_writeback_connector_init()
>>>>>>         * function.
>>>>>> +     *
>>>>>> +     * For some vendor drivers, the hardware resources are shared 
>>>>>> between
>>>>>> +     * writeback encoder and rest of the display pipeline.
>>>>>> +     * To accommodate such cases, encoder is a handle to the real 
>>>>>> encoder
>>>>>> +     * hardware.
>>>>>> +     *
>>>>>> +     * For current existing writeback users, this shall continue 
>>>>>> to be the
>>>>>> +     * embedded encoder for the writeback connector.
>>>>>> +     */
>>>>>> +    struct drm_encoder *encoder;
>>>>>> +
>>>>>> +    /**
>>>>>> +     * @internal_encoder: internal encoder used by writeback when
>>>>>> +     * drm_writeback_connector_init() is used.
>>>>>> +     * @encoder will be assigned to this for those cases
>>>>>> +     *
>>>>>> +     * This will be unused when 
>>>>>> drm_writeback_connector_init_with_encoder()
>>>>>> +     * is used.
>>>>>>         */
>>>>>> -    struct drm_encoder encoder;
>>>>>> +    struct drm_encoder internal_encoder;
>>>>>>        /**
>>>>>>         * @pixel_formats_blob_ptr:
>>

  reply	other threads:[~2022-04-25  0:03 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
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 [this message]
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=d8641c24-0235-e5a8-0586-53b8abf65de8@quicinc.com \
    --to=quic_abhinavk@quicinc.com \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=liviu.dudau@arm.com \
    --cc=markyacoub@chromium.org \
    --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.