dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime@cerno.tech>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: devicetree@vger.kernel.org, linux-fbdev@vger.kernel.org,
	David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH] dt-bindings: display: ssd1307fb: Convert to json-schema
Date: Tue, 18 May 2021 16:33:17 +0200	[thread overview]
Message-ID: <20210518143317.yy2sxxnd7yt6cyrx@gilmour> (raw)
In-Reply-To: <20210518075131.1463091-1-geert@linux-m68k.org>

[-- Attachment #1: Type: text/plain, Size: 4221 bytes --]

Hi

On Tue, May 18, 2021 at 09:51:31AM +0200, Geert Uytterhoeven wrote:
> Convert the Solomon SSD1307 Framebuffer Device Tree binding
> documentation to json-schema.
> 
> Fix the spelling of the "pwms" property.
> Document default values.
> Make properties with default values not required.
> 
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> ---
> I have listed Maxime as the maintainer, as he wrote the original driver
> and bindings.  Maxime: Please scream if this is inappropriate ;-)

Fine by me :)

> ---
>  .../bindings/display/solomon,ssd1307fb.yaml   | 166 ++++++++++++++++++
>  .../devicetree/bindings/display/ssd1307fb.txt |  60 -------
>  2 files changed, 166 insertions(+), 60 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/display/solomon,ssd1307fb.yaml
>  delete mode 100644 Documentation/devicetree/bindings/display/ssd1307fb.txt
> 
> diff --git a/Documentation/devicetree/bindings/display/solomon,ssd1307fb.yaml b/Documentation/devicetree/bindings/display/solomon,ssd1307fb.yaml
> new file mode 100644
> index 0000000000000000..bd632d86a4f814a0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/solomon,ssd1307fb.yaml
> @@ -0,0 +1,166 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/display/solomon,ssd1307fb.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Solomon SSD1307 OLED Controller Framebuffer
> +
> +maintainers:
> +  - Maxime Ripard <mripard@kernel.org>
> +
> +properties:
> +  compatible:
> +    enum:
> +      - solomon,ssd1305fb-i2c
> +      - solomon,ssd1306fb-i2c
> +      - solomon,ssd1307fb-i2c
> +      - solomon,ssd1309fb-i2c
> +
> +  reg:
> +    maxItems: 1
> +
> +  pwms:
> +    maxItems: 1
> +
> +  reset-gpios:
> +    maxItems: 1
> +
> +  vbat-supply:
> +    description: The supply for VBAT
> +
> +  solomon,height:
> +    $ref: /schemas/types.yaml#/definitions/uint32
> +    default: 16
> +    description:
> +      Height in pixel of the screen driven by the controller
> +
> +  solomon,width:
> +    $ref: /schemas/types.yaml#/definitions/uint32
> +    default: 96
> +    description:
> +      Width in pixel of the screen driven by the controller
> +
> +  solomon,page-offset:
> +    $ref: /schemas/types.yaml#/definitions/uint32
> +    default: 1
> +    description:
> +      Offset of pages (band of 8 pixels) that the screen is mapped to
> +
> +  solomon,segment-no-remap:
> +    type: boolean
> +    description:
> +      Display needs normal (non-inverted) data column to segment mapping
> +
> +  solomon,col-offset:
> +    $ref: /schemas/types.yaml#/definitions/uint32
> +    default: 0
> +    description:
> +      Offset of columns (COL/SEG) that the screen is mapped to
> +
> +  solomon,com-seq:
> +    type: boolean
> +    description:
> +      Display uses sequential COM pin configuration
> +
> +  solomon,com-lrremap:
> +    type: boolean
> +    description:
> +      Display uses left-right COM pin remap
> +
> +  solomon,com-invdir:
> +    type: boolean
> +    description:
> +      Display uses inverted COM pin scan direction
> +
> +  solomon,com-offset:
> +    $ref: /schemas/types.yaml#/definitions/uint32
> +    default: 0
> +    description:
> +      Number of the COM pin wired to the first display line
> +
> +  solomon,prechargep1:
> +    $ref: /schemas/types.yaml#/definitions/uint32
> +    default: 2
> +    description:
> +      Length of deselect period (phase 1) in clock cycles
> +
> +  solomon,prechargep2:
> +    $ref: /schemas/types.yaml#/definitions/uint32
> +    default: 2
> +    description:
> +      Length of precharge period (phase 2) in clock cycles.  This needs to be
> +      the higher, the higher the capacitance of the OLED's pixels is.
> +
> +  solomon,dclk-div:
> +    $ref: /schemas/types.yaml#/definitions/uint32
> +    minimum: 1
> +    maximum: 16
> +    description:
> +      Clock divisor. The default value is controller-dependent.

I guess we could document the default using an if / else statement?
Looks good otherwise :)

Maxime

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2021-05-18 14:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18  7:51 [PATCH] dt-bindings: display: ssd1307fb: Convert to json-schema Geert Uytterhoeven
2021-05-18 14:33 ` Maxime Ripard [this message]
2021-05-18 14:49   ` Geert Uytterhoeven
2021-05-24 11:48     ` Maxime Ripard
2021-05-19 21:33 ` Rob Herring

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=20210518143317.yy2sxxnd7yt6cyrx@gilmour \
    --to=maxime@cerno.tech \
    --cc=airlied@linux.ie \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    /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).