Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Francesco Dolcini <francesco@dolcini.it>
To: Frank Li <Frank.li@nxp.com>, Fabio Estevam <festevam@gmail.com>
Cc: Francesco Dolcini <francesco.dolcini@toradex.com>, imx@lists.linux.dev
Subject: Re: panel-lvds for imx8mm-verdin boards
Date: Wed, 18 Dec 2024 15:11:01 +0100	[thread overview]
Message-ID: <20241218141101.GA25083@francesco-nb> (raw)
In-Reply-To: <CAOMZO5AcyVeq8TN9qK=_54gP6y_rrCLjh22LnA=E6pLnxjbpNw@mail.gmail.com>

Hello Frank,

On Fri, Oct 18, 2024 at 06:13:07PM -0300, Fabio Estevam wrote:
> On Fri, Oct 18, 2024 at 4:24 PM Frank Li <Frank.li@nxp.com> wrote:
> >
> > There are some dtb check warning
> >
> > arch/arm64/boot/dts/freescale/imx8mm-mx8menlo.dtb: panel-lvds: compatible:0: 'panel-lvds' is not one of ['admatec,9904379', 'auo,b101ew05', 'chunghwa,claa070wp03xg', 'edt,etml0700z9ndha', 'hannstar,hsd101pww2', 'hydis,hv070wx2-1e0', 'jenson,bl-jt60050-01a', 'tbs,a711-panel']
> >
> > Can you help add actual pannel-lvds compatible string to clean up these
> > warning?

I do not think that allowing just panel-lvds in the compatible is going
to be fine from the DT maintainer point of view.

Adding a specific compatible will not solve the issue, because we can
connect different kind of display there. Doing this will get rid of the
warning however.

We could remove the node completely, but this would create some
regression we need to figure out how to handle, minimizing the impact.

Unfortunate there is not a perfect solution, IMO the best solution is to
remove the node, but I need to find some time to look into the evil
details.

Francesco



  parent reply	other threads:[~2024-12-18 14:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18 19:23 panel-lvds for imx8mm-verdin boards Frank Li
2024-10-18 21:13 ` Fabio Estevam
2024-10-19 12:24   ` Fabio Estevam
2024-10-21 19:51     ` Frank Li
2024-12-13 21:12       ` Frank Li
2024-11-07 20:08   ` Frank Li
2024-12-18 14:11   ` Francesco Dolcini [this message]
2025-02-10 21:36     ` Frank Li

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=20241218141101.GA25083@francesco-nb \
    --to=francesco@dolcini.it \
    --cc=Frank.li@nxp.com \
    --cc=festevam@gmail.com \
    --cc=francesco.dolcini@toradex.com \
    --cc=imx@lists.linux.dev \
    /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