From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: shmobile: defconfig: Refresh for v6.1-rc5
Date: Fri, 6 Jan 2023 15:41:55 +0200 [thread overview]
Message-ID: <Y7glIwlrJknBOfCo@pendragon.ideasonboard.com> (raw)
In-Reply-To: <4f7757bd700edff487df387ca40ffb1524d688a4.1672744302.git.geert+renesas@glider.be>
Hi Geert,
On Tue, Jan 03, 2023 at 12:13:54PM +0100, Geert Uytterhoeven wrote:
> Refresh the defconfig for Renesas ARM systems:
> - Disable CONFIG_DRM_RCAR_USE_MIPI_DSI (defaults to yes since commit
> a830a15678593948 ("drm: rcar-du: Fix Kconfig dependency between
> RCAR_DU and RCAR_MIPI_DSI"), but only used on R-Car V3U).
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> To be queued in renesas-devel for v6.3, unless someone plans to fix the
> default?
Patches are welcome :-)
> ---
> arch/arm/configs/shmobile_defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/configs/shmobile_defconfig b/arch/arm/configs/shmobile_defconfig
> index 452aef74cc5c1256..751d939fcb761b31 100644
> --- a/arch/arm/configs/shmobile_defconfig
> +++ b/arch/arm/configs/shmobile_defconfig
> @@ -136,6 +136,7 @@ CONFIG_VIDEO_ADV7604_CEC=y
> CONFIG_VIDEO_ML86V7667=y
> CONFIG_DRM=y
> CONFIG_DRM_RCAR_DU=y
> +# CONFIG_DRM_RCAR_USE_MIPI_DSI is not set
> CONFIG_DRM_PANEL_SIMPLE=y
> CONFIG_DRM_PANEL_EDP=y
> CONFIG_DRM_DISPLAY_CONNECTOR=y
--
Regards,
Laurent Pinchart
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-01-06 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 11:13 [PATCH] ARM: shmobile: defconfig: Refresh for v6.1-rc5 Geert Uytterhoeven
2023-01-06 13:41 ` Laurent Pinchart [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=Y7glIwlrJknBOfCo@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@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;
as well as URLs for NNTP newsgroup(s).