All of lore.kernel.org
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javierm@redhat.com>
To: Amit Barzilai <amit.barzilai22@gmail.com>,
	Krzysztof Kozlowski <krzk@kernel.org>
Cc: sashiko-reviews@lists.linux.dev, dri-devel@lists.freedesktop.org,
	conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 1/6] dt-bindings: display: Add Solomon SSD1351 OLED controller
Date: Mon, 14 Sep 2026 09:07:25 +0200	[thread overview]
Message-ID: <87v7881fbm.fsf@ocarina.mail-host-address-is-not-set> (raw)
In-Reply-To: <CAOEgbEqd6pGUL6o2CbyePUWm=NBy1GJJaOm+_7rg3CsEGqEfYw@mail.gmail.com>

Amit Barzilai <amit.barzilai22@gmail.com> writes:

Hello Amit,

> On Thu, Sep 10, 2026 at 2:16 PM Javier Martinez Canillas
> <javierm@redhat.com> wrote:
>>
>> sashiko-bot@kernel.org writes:
>>
>> >> +allOf:
>> >> +  - $ref: solomon,ssd-common.yaml#
>> >> +
>> >> +properties:
>> >> +  compatible:
>> >> +    enum:
>> >> +      - solomon,ssd1351
>> >
>> > [Severity: Low]
>> > Should this properties block also declare default values for solomon,width
>> > and solomon,height?
>> >
>> > Other bindings that include solomon,ssd-common.yaml, such as
>> > solomon,ssd133x.yaml, establish default geometry values for their specific
>> > compatible strings in this block. Without these default values, device trees
>> > that omit the width and height properties will lack a schema-defined default
>> > geometry.
>> >
>> > --
>> > Sashiko AI review · https://sashiko.dev/#/patchset/20260823111959.17029-1-amit.barzilai22@gmail.com?part=1
>> >
>>
>> I think Sashiko is correct here. Let's include the default values in the
>> DT binding schema to be consistent to what is done in the other bindings.
>
> I included them in v1, Krzysztof mentioned that they should be removed
> since they are deducible from the compatible:
> https://lore.kernel.org/dri-devel/20260611-psychedelic-funky-foxhound-a8e39d@quoll/
>
> I personally agree with Krzysztof, but I won't die on this hill.
> Let me know which way you'd like this to go.
>

I see. I don't have a strong opinion either so I'm OK with not having it
in the binding doc then.

> -- 
> Thanks,
> Amit
>

-- 
Best regards,

Javier Martinez Canillas
Core Platforms
Red Hat


  reply	other threads:[~2026-09-14  7:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-23 11:19 [PATCH v5 0/6] drm/ssd130x: Add support for the Solomon SSD1351 OLED controller Amit Barzilai
2026-08-23 11:19 ` [PATCH v5 1/6] dt-bindings: display: Add " Amit Barzilai
2026-08-23 11:28   ` sashiko-bot
2026-09-10 11:16     ` Javier Martinez Canillas
2026-09-13 14:54       ` Amit Barzilai
2026-09-14  7:07         ` Javier Martinez Canillas [this message]
2026-09-10 11:14   ` Javier Martinez Canillas
2026-08-23 11:19 ` [PATCH v5 2/6] drm/ssd130x: Change SSD133X color format to RGB565 from RGB332 Amit Barzilai
2026-08-23 11:36   ` sashiko-bot
2026-08-24 15:22   ` Andy Shevchenko
2026-08-23 11:19 ` [PATCH v5 3/6] drm/ssd130x: Constify ssd130x_write_data() 'values' parameter Amit Barzilai
2026-08-23 11:19 ` [PATCH v5 4/6] drm/ssd130x: Replace positional ssd130x_spi_id[] initialization with C99 Amit Barzilai
2026-09-10 11:17   ` Javier Martinez Canillas
2026-08-23 11:19 ` [PATCH v5 5/6] drm/ssd130x: Implement ssd130x_write_cmd() on top of ssd130x_write_cmds() Amit Barzilai
2026-09-10 11:22   ` Javier Martinez Canillas
2026-08-23 11:19 ` [PATCH v5 6/6] drm/ssd130x: Add SSD135X_FAMILY and SSD1351 support Amit Barzilai
2026-08-23 11:34   ` sashiko-bot
2026-09-02  8:47     ` Amit Barzilai
2026-09-10 12:00   ` Javier Martinez Canillas
2026-09-14  9:04     ` Amit Barzilai

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=87v7881fbm.fsf@ocarina.mail-host-address-is-not-set \
    --to=javierm@redhat.com \
    --cc=amit.barzilai22@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=krzk@kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.