From: Eric Anholt <eric@anholt.net>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: dri-devel@lists.freedesktop.org,
Archit Taneja <architt@codeaurora.org>,
Andrzej Hajda <a.hajda@samsung.com>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 1/3] drm/vc4: Move the DSI clock divider workaround closer to the clock call.
Date: Thu, 28 Sep 2017 10:20:08 -0700 [thread overview]
Message-ID: <871smqhh9z.fsf@anholt.net> (raw)
In-Reply-To: <20170928125449.GA28022@ulmo>
[-- Attachment #1: Type: text/plain, Size: 766 bytes --]
Thierry Reding <thierry.reding@gmail.com> writes:
> [ Unknown signature status ]
> On Wed, Sep 27, 2017 at 12:36:52PM -0700, Eric Anholt wrote:
>> We want the adjusted_mode->clock to be the actual clock we're
>> expecting to program, so that consumers see the right values for clock
>> and vrefresh.
>>
>> Signed-off-by: Eric Anholt <eric@anholt.net>
>> ---
>> drivers/gpu/drm/vc4/vc4_dsi.c | 12 ++++++------
>> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> Do you want me to apply this to drm-misc-next along with the touchscreen
> panel driver?
drm-misc-next procedure trends toward the submitter applies the patch
once they get review, if they have the commit rights. However, I'm
happy either way as long as I can get the code in.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-09-28 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 19:36 [PATCH v6 0/3] RPi touchscreen panel resend Eric Anholt
2017-09-27 19:36 ` [PATCH v6 1/3] drm/vc4: Move the DSI clock divider workaround closer to the clock call Eric Anholt
2017-09-28 12:54 ` Thierry Reding
2017-09-28 17:20 ` Eric Anholt [this message]
2017-09-27 19:36 ` [PATCH v6 2/3] dt-bindings: Document the Raspberry Pi Touchscreen nodes Eric Anholt
2017-09-27 19:36 ` [PATCH v6 3/3] drm/panel: Add support for the Raspberry Pi 7" Touchscreen Eric Anholt
2017-10-06 4:08 ` Archit Taneja
2017-10-06 9:22 ` Thierry Reding
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=871smqhh9z.fsf@anholt.net \
--to=eric@anholt.net \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=architt@codeaurora.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thierry.reding@gmail.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