From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Cc: dri-devel@lists.freedesktop.org,
linux-renesas-soc@vger.kernel.org,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>
Subject: Re: [PATCH 2/3] drm: rcar-du: lvds: Move LVDS enable code to separate code section
Date: Tue, 14 Feb 2023 09:25:57 +0100 [thread overview]
Message-ID: <CAMuHMdWSt5uY=kSGrdt4V6311ZmvVEPo0oN6v-_c3uZNQLZ8=w@mail.gmail.com> (raw)
In-Reply-To: <20230214003736.18871-3-laurent.pinchart+renesas@ideasonboard.com>
On Tue, Feb 14, 2023 at 1:45 AM Laurent Pinchart
<laurent.pinchart+renesas@ideasonboard.com> wrote:
> To prepare for a rework of the LVDS disable code, which will need to be
> called from rcar_lvds_pclk_disable(), move the LVDS enable code,
> currently stored in the __rcar_lvds_atomic_enable() function, to a
> separate code section separate from bridge operations. It will be then
> extended with the LVDS disable code.
>
> As part of this rework the __rcar_lvds_atomic_enable() function is
> renamed to rcar_lvds_enable() to more clearly indicate its purpose.
>
> No functional change intended.
>
> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
WARNING: multiple messages have this Message-ID (diff)
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Cc: linux-renesas-soc@vger.kernel.org,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm: rcar-du: lvds: Move LVDS enable code to separate code section
Date: Tue, 14 Feb 2023 09:25:57 +0100 [thread overview]
Message-ID: <CAMuHMdWSt5uY=kSGrdt4V6311ZmvVEPo0oN6v-_c3uZNQLZ8=w@mail.gmail.com> (raw)
In-Reply-To: <20230214003736.18871-3-laurent.pinchart+renesas@ideasonboard.com>
On Tue, Feb 14, 2023 at 1:45 AM Laurent Pinchart
<laurent.pinchart+renesas@ideasonboard.com> wrote:
> To prepare for a rework of the LVDS disable code, which will need to be
> called from rcar_lvds_pclk_disable(), move the LVDS enable code,
> currently stored in the __rcar_lvds_atomic_enable() function, to a
> separate code section separate from bridge operations. It will be then
> extended with the LVDS disable code.
>
> As part of this rework the __rcar_lvds_atomic_enable() function is
> renamed to rcar_lvds_enable() to more clearly indicate its purpose.
>
> No functional change intended.
>
> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2023-02-14 8:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 0:37 [PATCH 0/3] drm: rcar-du: Fix vblank wait timeout when stopping LVDS output Laurent Pinchart
2023-02-14 0:37 ` [PATCH 1/3] drm: rcar-du: lvds: Call function directly instead of through pointer Laurent Pinchart
2023-02-15 6:18 ` Tomi Valkeinen
2023-02-14 0:37 ` [PATCH 2/3] drm: rcar-du: lvds: Move LVDS enable code to separate code section Laurent Pinchart
2023-02-14 8:25 ` Geert Uytterhoeven [this message]
2023-02-14 8:25 ` Geert Uytterhoeven
2023-02-15 6:20 ` Tomi Valkeinen
2023-02-15 8:34 ` Laurent Pinchart
2023-02-15 8:34 ` Laurent Pinchart
2023-02-14 0:37 ` [PATCH 3/3] drm: rcar-du: lvds: Fix LVDS PLL disable on D3/E3 Laurent Pinchart
2023-02-15 6:29 ` Tomi Valkeinen
2023-02-15 10:19 ` Laurent Pinchart
2023-02-15 10:19 ` Laurent Pinchart
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='CAMuHMdWSt5uY=kSGrdt4V6311ZmvVEPo0oN6v-_c3uZNQLZ8=w@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=tomi.valkeinen@ideasonboard.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 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.