dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Yannick Fertre <yannick.fertre@foss.st.com>,
	Alexandre Torgue <alexandre.torgue@st.com>,
	Philippe Cornu <philippe.cornu@foss.st.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	Sam Ravnborg <sam@ravnborg.org>, David Airlie <airlied@linux.ie>,
	Daniel Vetter <daniel@ffwll.ch>, Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	<dri-devel@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: multi_v7_defconfig: add STM32 CEC support
Date: Mon, 25 Jan 2021 15:36:18 +0100	[thread overview]
Message-ID: <687e3445-ffc3-7133-db2a-14e6c7c8efea@foss.st.com> (raw)
In-Reply-To: <20210115143236.27675-1-yannick.fertre@foss.st.com>

Hi Yannick

On 1/15/21 3:32 PM, Yannick Fertre wrote:
> Enable CEC support for STMicroelectronics as loadable module.
> 
> Signed-off-by: Yannick Fertre <yannick.fertre@foss.st.com>
> ---
>   arch/arm/configs/multi_v7_defconfig | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig
> index c5f25710fedc..05cc0607a9ad 100644
> --- a/arch/arm/configs/multi_v7_defconfig
> +++ b/arch/arm/configs/multi_v7_defconfig
> @@ -656,6 +656,7 @@ CONFIG_V4L_TEST_DRIVERS=y
>   CONFIG_VIDEO_VIVID=m
>   CONFIG_CEC_PLATFORM_DRIVERS=y
>   CONFIG_CEC_SAMSUNG_S5P=m
> +CONFIG_CEC_STM32=m
>   CONFIG_VIDEO_ADV7180=m
>   CONFIG_VIDEO_ADV7604=m
>   CONFIG_VIDEO_ADV7604_CEC=y
> 

Applied on stm32-next.

Thanks.
Alex
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2021-01-26  8:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15 14:32 [PATCH] ARM: multi_v7_defconfig: add STM32 CEC support Yannick Fertre
2021-01-25 14:36 ` Alexandre TORGUE [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=687e3445-ffc3-7133-db2a-14e6c7c8efea@foss.st.com \
    --to=alexandre.torgue@foss.st.com \
    --cc=airlied@linux.ie \
    --cc=alexandre.torgue@st.com \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=philippe.cornu@foss.st.com \
    --cc=robh+dt@kernel.org \
    --cc=sam@ravnborg.org \
    --cc=thierry.reding@gmail.com \
    --cc=yannick.fertre@foss.st.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).