All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Amit Barzilai" <amit.barzilai22@gmail.com>
Cc: robh@kernel.org, dri-devel@lists.freedesktop.org,
	conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v6 1/6] dt-bindings: display: Add Solomon SSD1351 OLED controller
Date: Mon, 14 Sep 2026 09:07:45 +0000	[thread overview]
Message-ID: <20260914090746.52B6E1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260914085931.66857-2-amit.barzilai22@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The binding schema omits default values for `solomon,width` and `solomon,height`.
--

commit d69921d470fb48f9128b8539591beb3d33f26088
Author: Amit Barzilai <amit.barzilai22@gmail.com>

dt-bindings: display: Add Solomon SSD1351 OLED controller

This commit adds a device tree binding for the Solomon SSD1351 RGB OLED
display controller. It builds upon the shared solomon,ssd-common.yaml
properties.

> diff --git a/Documentation/devicetree/bindings/display/solomon,ssd1351.yaml b/Documentation/devicetree/bindings/display/solomon,ssd1351.yaml
> new file mode 100644
> index 0000000000000..80850c2ab5b3e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/solomon,ssd1351.yaml
[ ... ]
> +allOf:
> +  - $ref: solomon,ssd-common.yaml#
> +
> +properties:
> +  compatible:
> +    enum:
> +      - solomon,ssd1351

[Severity: Low]
Does this properties block need to define solomon,width and solomon,height
with default constraints?

The SSD1351 controller is 128x128 according to the commit message. Since this
binding includes solomon,ssd-common.yaml, validation of a device tree node
for solomon,ssd1351 without explicit width and height properties will not
populate or document the default values in the schema output.

Adding these properties here with a default constraint of 128 would match the
hardware specs and maintain subsystem consistency.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260914085931.66857-1-amit.barzilai22@gmail.com?part=1

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14  8:59 [PATCH v6 0/6] drm/ssd130x: Add support for the Solomon SSD1351 OLED controller Amit Barzilai
2026-09-14  8:59 ` [PATCH v6 1/6] dt-bindings: display: Add " Amit Barzilai
2026-09-14  9:07   ` sashiko-bot [this message]
2026-09-14  8:59 ` [PATCH v6 2/6] drm/ssd130x: Change SSD133X color format to RGB565 from RGB332 Amit Barzilai
2026-09-14  9:14   ` sashiko-bot
2026-09-14  8:59 ` [PATCH v6 3/6] drm/ssd130x: Constify ssd130x_write_data() 'values' parameter Amit Barzilai
2026-09-14  8:59 ` [PATCH v6 4/6] drm/ssd130x: Replace positional ssd130x_spi_id[] initialization with C99 Amit Barzilai
2026-09-14  8:59 ` [PATCH v6 5/6] drm/ssd130x: Implement ssd130x_write_cmd() on top of ssd130x_write_cmds() Amit Barzilai
2026-09-14  8:59 ` [PATCH v6 6/6] drm/ssd130x: Add SSD135X_FAMILY and SSD1351 support Amit Barzilai
2026-09-14  9:27   ` sashiko-bot
2026-09-14 10:13 ` [PATCH v6 0/6] 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=20260914090746.52B6E1F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=amit.barzilai22@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.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.