From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/3] video: add simple, transparent, bridge implementation
Date: Fri, 21 Aug 2020 10:14:44 +0200 [thread overview]
Message-ID: <054fcca5-29f5-04db-f58e-31ae2bfaedef@pengutronix.de> (raw)
In-Reply-To: <20200820133357.GA180086@ravnborg.org>
Hello,
On 8/20/20 3:33 PM, Sam Ravnborg wrote:
>>> And in the kernel we today only accept bindings in DT schema format
>>> (.yaml). Maybe do the same in the barebox and convert this binding to DT
>>> Schema format while at it.
>>
>> having make dtbs and dtbs_check as barebox make targets is on my todo list.
>> For now, I don't see the utility in having yaml bindings when they aren't
>> easily tested.
> You are coloring me confused here.
>
> .txt based bindings are not testable and syntax errros needs to be
> spotted manually. Futrthermore there is very little in description of
> the syntax.
>
> .yaml bindings are very simple to test - there is full infrastructure in
> the kernel. And there is semi formal specification of the syntax. And
> this is the syntax to be used for all new bindings.
I am not used to writing yaml bindings. I think the effort is better
invested, when I know the bindings are actively put to use by having
a target that can be run that automatically tests everything.
When we have that, I intend to migrate existing barebox-specific bindings
to YAML, so we can spot the errors.
> Tooling is simple - barebox tooling is not needed:
>
> cp foobar.yaml ${kernel}/Documentation/bindings/
> make dt_binding_check DT_SCHEMA_FILES=foobar.yaml
>
> I do not know what is the right approach in barebox, but as I wrote
> above the arguments confused me.
>
> Sam
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2020-08-21 8:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 4:53 Ahmad Fatoum
2020-08-17 4:53 ` [PATCH 2/3] video: ipuv3: parallel-display: support of_graph binding Ahmad Fatoum
2020-08-20 12:47 ` Sascha Hauer
2020-08-17 4:53 ` [PATCH 3/3] video: simple-panel: don't error out on unhandled ioctl command Ahmad Fatoum
2020-08-17 6:38 ` [PATCH 1/3] video: add simple, transparent, bridge implementation Sam Ravnborg
2020-08-20 12:24 ` Ahmad Fatoum
2020-08-20 13:33 ` Sam Ravnborg
2020-08-21 8:14 ` Ahmad Fatoum [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=054fcca5-29f5-04db-f58e-31ae2bfaedef@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=sam@ravnborg.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