From: Jani Nikula <jani.nikula@intel.com>
To: "Tseng, William" <william.tseng@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: RE: [PATCH 0/2] drm/i915/dsi: couple of fixing
Date: Wed, 09 Apr 2025 10:54:51 +0300 [thread overview]
Message-ID: <8734ehydkk.fsf@intel.com> (raw)
In-Reply-To: <SJ0PR11MB58940EE32DA88AFBB2D8EE49F1B52@SJ0PR11MB5894.namprd11.prod.outlook.com>
On Tue, 08 Apr 2025, "Tseng, William" <william.tseng@intel.com> wrote:
> Hi Jani
>
> Both patches look good to me after reviewing and testing the
> two patches with the hardware. The MIPI DSI panel is working
> with the patches. In the test, both clock and data timing have
> no change before and after patch.
>
> Please let me know if you have any questions.
If you think we should merge these, please provide your Reviewed-by and
Tested-by, and I will. :)
BR,
Jani.
>
>
> Regards
> William
>
>> -----Original Message-----
>> From: Nikula, Jani <jani.nikula@intel.com>
>> Sent: Thursday, April 3, 2025 8:22 PM
>> To: intel-gfx@lists.freedesktop.org
>> Cc: Nikula, Jani <jani.nikula@intel.com>; Tseng, William
>> <william.tseng@intel.com>
>> Subject: [PATCH 0/2] drm/i915/dsi: couple of fixing
>>
>> When I was reviewing [1] these oddities caught my eye.
>>
>> BR,
>> Jani.
>>
>> [1] https://lore.kernel.org/r/20250311100626.533888-1-
>> william.tseng@intel.com
>>
>> Cc: William Tseng <william.tseng@intel.com>
>>
>> Jani Nikula (2):
>> drm/i915/dsi: separate clock and data lane prepare timing
>> drm/i915/dsi: unify naming and simplify checks for dphy params
>>
>> drivers/gpu/drm/i915/display/icl_dsi.c | 90 ++++++++------------------
>> 1 file changed, 26 insertions(+), 64 deletions(-)
>>
>> --
>> 2.39.5
>
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-04-09 7:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 12:21 [PATCH 0/2] drm/i915/dsi: couple of fixing Jani Nikula
2025-04-03 12:21 ` [PATCH 1/2] drm/i915/dsi: separate clock and data lane prepare timing Jani Nikula
2025-04-03 12:21 ` [PATCH 2/2] drm/i915/dsi: unify naming and simplify checks for dphy params Jani Nikula
2025-04-03 13:06 ` ✓ i915.CI.BAT: success for drm/i915/dsi: couple of fixing Patchwork
2025-04-03 15:01 ` ✗ i915.CI.Full: failure " Patchwork
2025-04-08 9:04 ` [PATCH 0/2] " Tseng, William
2025-04-09 7:54 ` Jani Nikula [this message]
2025-04-09 9:28 ` Tseng, William
2025-04-09 12:01 ` Jani Nikula
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=8734ehydkk.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=william.tseng@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