devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Dharma.B@microchip.com
Cc: krzysztof.kozlowski@linaro.org,
	maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	tzimmermann@suse.de, airlied@gmail.com, daniel@ffwll.ch,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	Nicolas.Ferre@microchip.com, alexandre.belloni@bootlin.com,
	claudiu.beznea@tuxon.dev, dri-devel@lists.freedesktop.org,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: display: atmel,lcdc: convert to dtschema
Date: Fri, 1 Mar 2024 12:10:07 -0600	[thread overview]
Message-ID: <20240301181007.GA2481641-robh@kernel.org> (raw)
In-Reply-To: <dc8181d9-c7c9-4817-96f1-84a1b64575d6@microchip.com>

On Thu, Feb 29, 2024 at 06:25:56AM +0000, Dharma.B@microchip.com wrote:
> On 28/02/24 3:53 pm, Krzysztof Kozlowski wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> > 
> > On 28/02/2024 11:18, Dharma.B@microchip.com wrote:
> >> On 28/02/24 12:43 pm, Krzysztof Kozlowski wrote:
> >>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> >>>
> >>> On 28/02/2024 07:59, Dharma.B@microchip.com wrote:
> >>>>
> >>>>>
> >>>>> I don't know what's this exactly, but if embedded display then maybe
> >>>>> could be part of this device node. If some other display, then maybe you
> >>>>> need another schema, with compatible? But first I would check how others
> >>>>> are doing this.
> >>>>
> >>>> Okay, then I think the driver also needs to be modified, currently the
> >>>> driver parses the phandle and looks for these properties. Also the
> >>>> corresponding dts files.
> >>>
> >>> Driver does not have to be modified in my proposal. You would still have
> >>> phandle.
> >>
> >> If I understand correctly, I could define the dt bindings as below
> >>
> >>     display:
> >>       $ref: /schemas/types.yaml#/definitions/phandle
> >>       description: A phandle pointing to the display node.
> >>
> >>     panel:
> >>       $ref: panel/panel-common.yaml#
> >>       properties:
> >>
> > 
> > So these are standard panel bindings? Then the node should live outside
> > of lcdc. If current driver needs to poke inside panel and panel could be
> > anything, then probably you need peripheral-props-like approach. :/
> 
> Thank you so much, so can I use something like this
> 
>    display:
>      $ref: /schemas/types.yaml#/definitions/phandle
>      description: A phandle pointing to the display node.
> 
> patternProperties:
>    "^panel":

Just 'panel' and not a pattern.

However, that's not what the original binding had. It was a separate 
node. If you want to preserve that, then you'll need a separate 
schema file and a special 'select'. Something like:

select:
  anyOf:
    - required: [ atmel,dmacon ]
    - required: [ atmel,lcdcon2 ]
    - required: [ atmel,guard-time ]

Up to you and at91 maintainers if you want to have to update your dts 
files or not.

Rob

  reply	other threads:[~2024-03-01 18:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-23  9:14 [PATCH] dt-bindings: display: atmel,lcdc: convert to dtschema Dharma Balasubiramani
2024-02-27 12:03 ` Krzysztof Kozlowski
2024-02-28  6:59   ` Dharma.B
2024-02-28  7:13     ` Krzysztof Kozlowski
2024-02-28 10:18       ` Dharma.B
2024-02-28 10:23         ` Krzysztof Kozlowski
2024-02-29  6:25           ` Dharma.B
2024-03-01 18:10             ` Rob Herring [this message]
2024-03-04  4:14               ` Dharma.B

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=20240301181007.GA2481641-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=Dharma.B@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=airlied@gmail.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=conor+dt@kernel.org \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=tzimmermann@suse.de \
    /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).