From: Doug Anderson <dianders@chromium.org>
To: neil.armstrong@linaro.org
Cc: Cong Yang <yangcong5@huaqin.corp-partner.google.com>,
sam@ravnborg.org, daniel@ffwll.ch, linus.walleij@linaro.org,
krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
conor+dt@kernel.org, airlied@gmail.com,
dmitry.baryshkov@linaro.org, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
xuxinxiong@huaqin.corp-partner.google.com
Subject: Re: [v7 3/7] arm64: defconfig: Enable HIMAX_HX83102 panel
Date: Wed, 15 May 2024 14:28:25 -0700 [thread overview]
Message-ID: <CAD=FV=XkBkQUN-93eQDKZcw_66uSeNBBhbiq2hRLcFN+Ck71RQ@mail.gmail.com> (raw)
In-Reply-To: <0fcdb0ac-2e4a-44b2-a5d6-a67a1d747df8@linaro.org>
Hi,
On Wed, May 15, 2024 at 2:16 PM <neil.armstrong@linaro.org> wrote:
>
> Hi,
>
> On 15/05/2024 03:46, Cong Yang wrote:
> > DRM_PANEL_HIMAX_HX83102 is being split out from DRM_PANEL_BOE_TV101WUM_NL6.
> > Since the arm64 defconfig had the BOE panel driver enabled, let's also
> > enable the himax driver.
> >
> > Signed-off-by: Cong Yang <yangcong5@huaqin.corp-partner.google.com>
> > Reviewed-by: Douglas Anderson <dianders@chromium.org>
> > ---
> > arch/arm64/configs/defconfig | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> > index 2c30d617e180..687c86ddaece 100644
> > --- a/arch/arm64/configs/defconfig
> > +++ b/arch/arm64/configs/defconfig
> > @@ -864,6 +864,7 @@ CONFIG_DRM_PANEL_BOE_TV101WUM_NL6=m
> > CONFIG_DRM_PANEL_LVDS=m
> > CONFIG_DRM_PANEL_SIMPLE=m
> > CONFIG_DRM_PANEL_EDP=m
> > +CONFIG_DRM_PANEL_HIMAX_HX83102=m
> > CONFIG_DRM_PANEL_ILITEK_ILI9882T=m
> > CONFIG_DRM_PANEL_MANTIX_MLAF057WE51=m
> > CONFIG_DRM_PANEL_RAYDIUM_RM67191=m
>
> You should probably sent this one separately since only an ARM SoC maintainer
> can apply this, probably via the qcom tree.
Really? I always kinda figured that this was a bit like MAINTAINERS
where it can come through a bunch of different trees. Certainly I've
landed changes to it before through the drm-misc tree. If that was
wrong then I'll certainly stop doing it, of course.
-Doug
next prev parent reply other threads:[~2024-05-15 21:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 1:46 [PATCH v7 0/7] Break out as separate driver and add BOE nv110wum-l60 IVO t109nw41 MIPI-DSI panel Cong Yang
2024-05-15 1:46 ` [v7 1/7] dt-bindings: display: panel: Add himax hx83102 panel bindings Cong Yang
2024-05-28 11:22 ` Linus Walleij
2024-05-15 1:46 ` [v7 2/7] drm/panel: himax-hx83102: Break out as separate driver Cong Yang
2024-05-15 21:13 ` Doug Anderson
2024-05-15 1:46 ` [v7 3/7] arm64: defconfig: Enable HIMAX_HX83102 panel Cong Yang
2024-05-15 21:15 ` neil.armstrong
2024-05-15 21:28 ` Doug Anderson [this message]
2024-05-16 6:43 ` cong yang
2024-05-16 6:55 ` neil.armstrong
2024-05-16 13:43 ` Doug Anderson
2024-05-16 14:09 ` Doug Anderson
2024-05-17 6:41 ` Arnd Bergmann
2024-05-15 1:46 ` [v7 4/7] dt-bindings: display: panel: Add compatible for BOE nv110wum-l60 Cong Yang
2024-05-28 11:23 ` Linus Walleij
2024-05-15 1:46 ` [v7 5/7] drm/panel: himax-hx83102: Support for BOE nv110wum-l60 MIPI-DSI panel Cong Yang
2024-05-15 1:46 ` [v7 6/7] dt-bindings: display: panel: Add compatible for IVO t109nw41 Cong Yang
2024-05-28 11:23 ` Linus Walleij
2024-05-15 1:46 ` [v7 7/7] drm/panel: himax-hx83102: Support for IVO t109nw41 MIPI-DSI panel Cong Yang
2024-05-17 7:29 ` (subset) [PATCH v7 0/7] Break out as separate driver and add BOE nv110wum-l60 " Neil Armstrong
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='CAD=FV=XkBkQUN-93eQDKZcw_66uSeNBBhbiq2hRLcFN+Ck71RQ@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=xuxinxiong@huaqin.corp-partner.google.com \
--cc=yangcong5@huaqin.corp-partner.google.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 read-only IMAP folder(s) and NNTP newsgroup(s).