mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chintan Patel <chintanlike@gmail.com>
To: Doug Anderson <dianders@chromium.org>
Cc: sumit.semwal@linaro.org, neil.armstrong@linaro.org,
	jesszhan0024@gmail.com, maarten.lankhorst@linux.intel.com,
	mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com,
	simona@ffwll.ch, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/panel: novatek-nt36672a: Inline command sequences
Date: Fri, 17 Apr 2026 18:51:11 -0700	[thread overview]
Message-ID: <9947777e-ad0e-4af2-ac43-a2bb91339966@gmail.com> (raw)
In-Reply-To: <CAD=FV=UCyfjiqcpYCM5ePz-auX4g=i_+i78ivvvyA8R1XtAKzg@mail.gmail.com>

Hi Doug,

> 
> While that may seem a lot less efficient, the design of
> mipi_dsi_dcs_write_seq_multi() limits the inefficiency. Writing things
> like the above also allows you to share code better. For instance, if
> a second panel is added to the driver that uses the same sequence of
> commands for "dimming enable", or setting the resolution, or turning
> on "UI" mode, you could create a helper function to share the code.
> That is impossible / awkward with the tables-based approach.
> 
> Eyeballing the table, you could also potentially optimize things a
> little bit if it matters. For instance, I see a big sequence of 0x80
> going to lots of registers (without seeing the panel datasheet, I
> don't know why). Potentially, you could do things like:
> 
>    for (uint8_t reg = 0x8b, i < 0xa0, i++)
>      mipi_dsi_dcs_write_var_seq_multi(dsi_ctx, reg, 0x80);
> 
> I dunno if it's worth it. You could try running bloat-o-meter to see
> if the code is smaller, I guess...
> 
> [1] https://lore.kernel.org/r/CAD=FV=WtjW5WWmjeb2zwF2PjiJeZv1jZS_UKZ0bT1658=CkwVA@mail.gmail.com/

Thank you for the clarification and patience. I apologize for 
misunderstanding your initial feedback—I appreciate you taking the time 
to explain that the goal was to inline the command sequences as 
functions rather than simply removing the helper.

I will send v2.

      reply	other threads:[~2026-04-18  1:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-15 23:56 Chintan Patel
2026-04-17  3:16 ` Doug Anderson
2026-04-18  1:51   ` Chintan Patel [this message]

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=9947777e-ad0e-4af2-ac43-a2bb91339966@gmail.com \
    --to=chintanlike@gmail.com \
    --cc=airlied@gmail.com \
    --cc=dianders@chromium.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jesszhan0024@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=simona@ffwll.ch \
    --cc=sumit.semwal@linaro.org \
    --cc=tzimmermann@suse.de \
    /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

Powered by JetHome