From: Sam Ravnborg <sam@ravnborg.org>
To: "Chrisanthus, Anitha" <anitha.chrisanthus@intel.com>
Cc: "Vetter, Daniel" <daniel.vetter@intel.com>,
"Dea, Edmund J" <edmund.j.dea@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Neil Armstrong <narmstrong@baylibre.com>
Subject: Re: [PATCH v7 2/4] drm/kmb: Add support for KeemBay Display
Date: Sat, 12 Sep 2020 22:20:18 +0200 [thread overview]
Message-ID: <20200912202018.GA1129610@ravnborg.org> (raw)
In-Reply-To: <BY5PR11MB418272DBF475568D4CE2B0D38C240@BY5PR11MB4182.namprd11.prod.outlook.com>
Hi Anitha.
On Fri, Sep 11, 2020 at 08:54:41PM +0000, Chrisanthus, Anitha wrote:
> Hi Neil,
> Thanks for your review. Is a device tree binding document like this one enough? Entries for kmb-drm are similar to this.
> https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/gpu/brcm%2Cbcm-v3d.txt
>
> How do I submit it once I have it ready?
Please take a look at:
Documentation/devicetree/binding/submitting-patches.rst
That should explain it all.
New bindings must be in DT Schema foramt (.yaml files).
You can be assured that if you fail to do a dt_binding_check there are
syntax erros - speaking of experience.
So you need to get the tooling up and running.
Sam
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-09-12 20:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 20:02 [PATCH v7 0/4] Add support for KeemBay DRM driver Anitha Chrisanthus
2020-08-31 20:02 ` [PATCH v7 1/4] drm/kmb: Keem Bay driver register definition Anitha Chrisanthus
2020-08-31 20:02 ` [PATCH v7 2/4] drm/kmb: Add support for KeemBay Display Anitha Chrisanthus
2020-09-10 8:30 ` Daniel Vetter
2020-09-10 18:33 ` Sam Ravnborg
2020-09-11 8:56 ` Daniel Vetter
2020-09-22 18:20 ` Chrisanthus, Anitha
2020-09-23 15:22 ` Daniel Vetter
2020-10-01 18:02 ` Chrisanthus, Anitha
2020-10-02 9:19 ` Daniel Vetter
2020-10-03 4:58 ` Chrisanthus, Anitha
2020-10-05 13:49 ` Daniel Vetter
2020-10-06 0:22 ` Chrisanthus, Anitha
2020-09-10 8:40 ` Daniel Vetter
2020-09-10 9:32 ` Neil Armstrong
2020-09-11 20:54 ` Chrisanthus, Anitha
2020-09-12 20:20 ` Sam Ravnborg [this message]
2020-08-31 20:02 ` [PATCH v7 3/4] drm/kmb: Mipi DSI part of the display driver Anitha Chrisanthus
2020-09-10 8:38 ` Daniel Vetter
2020-08-31 20:02 ` [PATCH v7 4/4] drm/kmb: Build files for KeemBay Display driver Anitha Chrisanthus
2020-09-10 8:42 ` [PATCH v7 0/4] Add support for KeemBay DRM driver Daniel Vetter
2020-09-10 22:45 ` Chrisanthus, Anitha
2020-10-07 13:37 ` 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=20200912202018.GA1129610@ravnborg.org \
--to=sam@ravnborg.org \
--cc=anitha.chrisanthus@intel.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=edmund.j.dea@intel.com \
--cc=narmstrong@baylibre.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