From: Amit Barzilai <amit.barzilai22@gmail.com>
To: sashiko-bot@kernel.org
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
dri-devel@lists.freedesktop.org, robh@kernel.org,
sashiko-reviews@lists.linux.dev, krzk+dt@kernel.org
Subject: Re: [PATCH v3 1/3] dt-bindings: display: Add Solomon SSD1351 OLED controller
Date: Mon, 6 Jul 2026 11:39:13 +0300 [thread overview]
Message-ID: <20260706083913.19172-1-amit.barzilai22@gmail.com> (raw)
In-Reply-To: <20260704081758.0BD4D1F000E9@smtp.kernel.org>
>> Assisted-by: Claude:claude-opus-4-8
>
> [Severity: Low]
> This isn't a bug, but this Git trailer does not follow the standard format
> `Tag: Full Name <email@address.tld>`. Without an email address enclosed in
> angle brackets, this will likely trigger checkpatch warnings.
This is a standard Assisted-by tag, see Documentation/process/coding-assistants.rst
for basis.
>> +allOf:
>> + - $ref: solomon,ssd-common.yaml#
>> +
>> +properties:
>> + compatible:
>> + enum:
>> + - solomon,ssd1351
>
> [Severity: Low]
> Should there be default values defined for `solomon,width` and
> `solomon,height` in this block?
>
> Since the common schema `solomon,ssd-common.yaml` indicates these defaults
> are controller-dependent, omitting them here leaves the hardware's default
> resolution undocumented in this schema.
These defaults were present in v1 and were dropped for v2 following
Krzysztof's review: this binding has a single compatible, so the hardware
default (128x128) is deducible from the compatible itself and does not
need to be restated in the schema. The driver applies that default when
the properties are absent, and the properties remain available through
solomon,ssd-common.yaml for modules that wire a smaller panel.
Keeping them out, per that earlier feedback.
next prev parent reply other threads:[~2026-07-06 8:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 8:09 [PATCH v3 0/3] drm/ssd130x: Add support for the Solomon SSD1351 OLED controller Amit Barzilai
2026-07-04 8:09 ` [PATCH v3 1/3] dt-bindings: display: Add " Amit Barzilai
2026-07-04 8:17 ` sashiko-bot
2026-07-06 8:39 ` Amit Barzilai [this message]
2026-07-04 8:09 ` [PATCH v3 2/3] drm/ssd130x: Change SSD133X color format to RGB565 from RGB332 Amit Barzilai
2026-07-04 8:23 ` sashiko-bot
2026-07-04 8:09 ` [PATCH v3 3/3] drm/ssd130x: Add SSD135X_FAMILY and SSD1351 support Amit Barzilai
2026-07-04 8:26 ` sashiko-bot
2026-07-06 10:46 ` [PATCH v3 0/3] drm/ssd130x: Add support for the Solomon SSD1351 OLED controller Javier Martinez Canillas
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=20260706083913.19172-1-amit.barzilai22@gmail.com \
--to=amit.barzilai22@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzk+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-bot@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox