From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] nokia n900: update dts with camera support
Date: Mon, 28 Aug 2017 15:59:59 +0200 [thread overview]
Message-ID: <20170828135959.GA32560@amd> (raw)
In-Reply-To: <20170817000845.agkcuvqaheejm33j@earth>
Hi!
> > > Well, strobe property above already uses = <0>/<1> format, as do
> > > others.
> >
> > > Problem with "false = property does not exist" is that you don't know
> > > if it is "someone forgot to define it" or "someone made a typo" or
> > > "dts is too old to know about this property" or "the property indeed
> > > should be false"...
> >
> > As this is an established practice, I think we should follow it for bool
> > properties.
>
> Yes it's common practice, there is also device_property_read_bool()
> to get the value.
>
> > We could change the existing ones, too, and leave some extra checks in
> > place to handle old dtbs.
>
> The following should be downward compatible:
>
> var = read_bool();
> if (var && !read_int())
> var = false;
>
> Btw. DT people should be CC'd for DT binding additions/changes.
Ok, so for now we do crc=1 by default. Now we'd like to have crc
support configurable in the dts. But if we just introduce "crc;"
option, it will break old dts users. We could introduce "no-crc;" and
that would work in this particular case, but will break when we want
different defaults at different devices.
Anyway, introducing "no-crc;" seems pretty ugly to me. I'd rather do
"crc=<0>;", in a similar way we handle other options now.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170828/99e52bf9/attachment.sig>
next prev parent reply other threads:[~2017-08-28 13:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 20:49 [PATCH] nokia n900: update dts with camera support Pavel Machek
2017-08-13 15:37 ` Pali Rohár
2017-08-14 17:49 ` Tony Lindgren
2017-08-14 20:19 ` Sakari Ailus
2017-08-14 20:33 ` Tony Lindgren
2017-08-15 22:03 ` Pavel Machek
2017-08-16 20:53 ` Sebastian Reichel
2017-08-16 20:59 ` Pavel Machek
2017-08-16 21:23 ` Sakari Ailus
2017-08-17 0:08 ` Sebastian Reichel
2017-08-17 6:20 ` Sakari Ailus
2017-08-28 13:59 ` Pavel Machek [this message]
2017-08-28 15:07 ` Sakari Ailus
2017-08-28 18:20 ` Ivaylo Dimitrov
2017-08-28 13:18 ` [PATCH] nokia n900: drop unneeded/undocumented parts of the dts Pavel Machek
2017-09-19 17:42 ` Tony Lindgren
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=20170828135959.GA32560@amd \
--to=pavel@ucw.cz \
--cc=linux-arm-kernel@lists.infradead.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).