devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: "Paweł Chmiel" <pawel.mikolaj.chmiel@gmail.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
	airlied@linux.ie, Jonathan Bakker <xc-racer2@live.ca>,
	linux-kernel@vger.kernel.org, krzk@kernel.org,
	robh+dt@kernel.org, thierry.reding@gmail.com,
	dri-devel@lists.freedesktop.org, m.szyprowski@samsung.com
Subject: Re: [PATCH 1/2] drm: panel: Add Samsung s6e63m0 panel documentation
Date: Sat, 26 Jan 2019 21:55:01 +0100	[thread overview]
Message-ID: <20190126205501.GA31182@ravnborg.org> (raw)
In-Reply-To: <20190125164645.19208-1-pawel.mikolaj.chmiel@gmail.com>

Hi Pawel.

Thanks for the patch, some comments follows.
Please judge what comments you chose to follow, see this as suggestions.

According to Documentation/devicetree/bindings/submitting-patches.rst:

	The preferred subject prefix for binding patches is:
	"dt-bindings: <binding dir>: ..."

It would be a good idea to follow this practice in next revision.

On Fri, Jan 25, 2019 at 05:46:44PM +0100, Paweł Chmiel wrote:
> From: Jonathan Bakker <xc-racer2@live.ca>
> 
> This commit adds documentation for Samsung s6e63m0 AMOLED LCD panel
> driver.
> 
> Signed-off-by: Jonathan Bakker <xc-racer2@live.ca>
> Signed-off-by: Paweł Chmiel <pawel.mikolaj.chmiel@gmail.com>
> ---
>  .../display/panel/samsung,s6e63m0.txt         | 60 +++++++++++++++++++
>  1 file changed, 60 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/display/panel/samsung,s6e63m0.txt
> 
> diff --git a/Documentation/devicetree/bindings/display/panel/samsung,s6e63m0.txt b/Documentation/devicetree/bindings/display/panel/samsung,s6e63m0.txt
> new file mode 100644
> index 000000000000..4979200e2dd2
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/panel/samsung,s6e63m0.txt
> @@ -0,0 +1,60 @@
> +Samsung s6e63m0 AMOLED LCD panel
> +
> +Required properties:
> +  - compatible: "samsung,s6e63m0"
> +  - reset-gpio: GPIO spec for reset pin
The preferred name is reset-gpios (added 's')

> +  - vdd3-supply: VDD regulator
> +  - vci-supply: VCI regulator
> +  - display-timings: timings for the connected panel as described by [1]
Today, as is my best understanding, it is encouraged to specify the timing
in the actual driver and not in DT,

The example include a spi-max-frequency which is not mentioned?

> +
> +Optional properties:
> +  - reset-delay: Delay in ms after adjusting reset-gpio, default 120ms
> +  - power-on-delay: Delay in ms after powering on, default 25ms
> +  - power-off-delay: Delay in ms before powering off, default 200ms
> +  - panel-width-mm: physical panel width in mm
> +  - panel-height-mm: physical panel height in mm
Likewise these delays are also properties that today are included in the driver.

I cannot explain the background for this, this is just how things are done.

> +
> +The device node can contain one 'port' child node with one child
> +'endpoint' node, according to the bindings defined in [2]. This
> +node should describe panel's video bus.
> +
> +[1]: Documentation/devicetree/bindings/display/panel/display-timing.txt
> +[2]: Documentation/devicetree/bindings/media/video-interfaces.txt
> +
> +Example:
> +
> +		s6e63m0: display@0 {
> +			compatible = "samsung,s6e63m0";
> +			reg = <0>;
> +			reset-gpio = <&mp05 5 1>;
> +			vdd3-supply = <&ldo12_reg>;
> +			vci-supply = <&ldo11_reg>;
> +			spi-max-frequency = <1000000>;
> +
> +			power-on-delay = <0>;
> +			power-off-delay = <0>;
> +			reset-delay = <10>;
> +			panel-width-mm = <53>;
> +			panel-height-mm = <89>;
> +
> +			display-timings {
> +				timing-0 {
> +					/* 480x800@60Hz */
> +					clock-frequency = <25628040>;
> +					hactive = <480>;
> +					vactive = <800>;
> +					hfront-porch = <16>;
> +					hback-porch = <16>;
> +					hsync-len = <2>;
> +					vfront-porch = <28>;
> +					vback-porch = <1>;
> +					vsync-len = <2>;
> +				};
> +			};
> +
> +			port {
> +				lcd_ep: endpoint {
> +					remote-endpoint = <&fimd_ep>;
> +				};
> +			};
> +		};

	Sam
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-01-26 20:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-25 16:46 [PATCH 1/2] drm: panel: Add Samsung s6e63m0 panel documentation Paweł Chmiel
2019-01-25 16:46 ` [PATCH 2/2] drm/panel: Add driver for Samsung S6E63M0 panel Paweł Chmiel
2019-01-26 21:41   ` Sam Ravnborg
2019-01-28 13:47   ` Andrzej Hajda
2019-01-28 16:24     ` Paweł Chmiel
2019-01-26 20:55 ` Sam Ravnborg [this message]
2019-01-26 21:23   ` [PATCH 1/2] drm: panel: Add Samsung s6e63m0 panel documentation Paweł Chmiel

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=20190126205501.GA31182@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=airlied@linux.ie \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mark.rutland@arm.com \
    --cc=pawel.mikolaj.chmiel@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=xc-racer2@live.ca \
    /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).