From: Sam Ravnborg <sam@ravnborg.org>
To: Benjamin Gaignard <benjamin.gaignard@st.com>
Cc: thierry.reding@gmail.com, airlied@linux.ie, daniel@ffwll.ch,
robh+dt@kernel.org, mark.rutland@arm.com, philippe.cornu@st.com,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/3] dt-bindings: add simple DSI panels
Date: Sun, 9 Feb 2020 09:20:19 +0100 [thread overview]
Message-ID: <20200209082019.GB5321@ravnborg.org> (raw)
In-Reply-To: <20200206133344.724-1-benjamin.gaignard@st.com>
Hi Benjamin.
On Thu, Feb 06, 2020 at 02:33:41PM +0100, Benjamin Gaignard wrote:
> To complement panel-simple.yaml, create panel-simple-dsi.yaml.
> panel-simple-dsi-yaml are for all simple DSP panels with a single
> power-supply and optional backlight / enable GPIO / reset GPIO.
>
> Some DSI panels like orisetech,otm8009a or raydium,rm68200 are quite
> similar to simple dsi panel but with small variations. Create dedicated
> yaml files for them.
>
> Benjamin Gaignard (2):
> dt-bindings: panel: Convert raydium,rm68200 to json-schema
> dt-bindings: panel: Convert orisetech,otm8009a to json-schema
>
> Sam Ravnborg (1):
> dt-bindings: one file of all simple DSI panels
Thanks for picking this up.
Applied and pushed to drm-misc-next.
Sam
prev parent reply other threads:[~2020-02-09 8:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 13:33 [PATCH v4 0/3] dt-bindings: add simple DSI panels Benjamin Gaignard
2020-02-06 13:33 ` [PATCH v4 1/3] dt-bindings: one file of all " Benjamin Gaignard
2020-02-06 22:00 ` Rob Herring
2020-02-07 9:39 ` Philippe CORNU
2020-02-06 13:33 ` [PATCH v4 2/3] dt-bindings: panel: Convert raydium,rm68200 to json-schema Benjamin Gaignard
2020-02-06 22:02 ` Rob Herring
2020-02-07 9:35 ` Philippe CORNU
2020-02-06 13:33 ` [PATCH v4 3/3] dt-bindings: panel: Convert orisetech,otm8009a " Benjamin Gaignard
2020-02-06 22:02 ` Rob Herring
2020-02-07 9:34 ` Philippe CORNU
2020-02-09 8:20 ` Sam Ravnborg [this message]
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=20200209082019.GB5321@ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@linux.ie \
--cc=benjamin.gaignard@st.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=philippe.cornu@st.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
/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).