dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Lin, Wayne" <Wayne.Lin@amd.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Cc: "ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>,
	"Limonciello, Mario" <Mario.Limonciello@amd.com>,
	"Wentland, Harry" <Harry.Wentland@amd.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [PATCH] drm/dp: Fix Write_Status_Update_Request AUX request format
Date: Thu, 08 May 2025 15:16:29 +0300	[thread overview]
Message-ID: <878qn7ti02.fsf@intel.com> (raw)
In-Reply-To: <CO6PR12MB5489386C2D4F5D6DC49FF27AFC8BA@CO6PR12MB5489.namprd12.prod.outlook.com>

On Thu, 08 May 2025, "Lin, Wayne" <Wayne.Lin@amd.com> wrote:
> [Public]
>
>> -----Original Message-----
>> From: Jani Nikula <jani.nikula@intel.com>
>> Sent: Thursday, May 8, 2025 4:19 PM
>> To: Lin, Wayne <Wayne.Lin@amd.com>; dri-devel@lists.freedesktop.org
>> Cc: ville.syrjala@linux.intel.com; Limonciello, Mario <Mario.Limonciello@amd.com>;
>> Wentland, Harry <Harry.Wentland@amd.com>; Lin, Wayne
>> <Wayne.Lin@amd.com>; stable@vger.kernel.org
>> Subject: Re: [PATCH] drm/dp: Fix Write_Status_Update_Request AUX request
>> format
>>
>> On Sun, 27 Apr 2025, Wayne Lin <Wayne.Lin@amd.com> wrote:
>> > +                   /*
>> > +                    * When I2C write firstly get defer and get ack after
>> > +                    * retries by wirte_status_update, we have to return
>> > +                    * all data bytes get transferred instead of 0.
>> > +                    */
>>
>> My brain gives me syntax and parse error here. ;)
>
> Appreciate for the feedback, Jani.
> Could you elaborate more on your concerns please?
>
> Since Write_Status_Update_Request is address only request. Data length
> is 0. When I2C write request completes, reply for
> Write_Status_Update_Request from DPRx will be ACK only (i.e. data
> length is 0).
>
> Is your concern about returning 0 from aux->transfer?
> My thoughts is drm_dp_i2c_do_msg() is designed to handle I2C-Over-Aux
> reply data, and aux->transfer() is handling hw specific manipulation and
> return transferred bytes. For Write_Status_Update_Request request itself,
> nothing new to be transferred. I think drm_dp_i2c_do_msg() should be
> responsible for determining the correct transferred data bytes under this
> case. Or do you expect aux->transfer to memorize the data length of
> write request?

My concern is that I don't understand what the comment is trying to say.

"when i2c write firstly get defer" - what does it mean?

"wirte_status_update" - typo

"we have to" - why?

"return all data bytes get transferred" - what does it mean?

>
> Thanks!
>>
>> BR,
>> Jani.
>>
>> --
>> Jani Nikula, Intel
> --
> Wayne Lin

-- 
Jani Nikula, Intel

  reply	other threads:[~2025-05-08 12:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-27  9:50 [PATCH] drm/dp: Fix Write_Status_Update_Request AUX request format Wayne Lin
2025-05-05 20:22 ` Mario Limonciello
2025-05-08  1:48   ` Lin, Wayne
2025-05-08  8:19 ` Jani Nikula
2025-05-08 12:02   ` Lin, Wayne
2025-05-08 12:16     ` Jani Nikula [this message]
2025-05-08 12:54       ` Lin, Wayne

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=878qn7ti02.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=Harry.Wentland@amd.com \
    --cc=Mario.Limonciello@amd.com \
    --cc=Wayne.Lin@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=stable@vger.kernel.org \
    --cc=ville.syrjala@linux.intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).