From: "Andreas Färber" <afaerber-l3A5Bk7waGM@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
Dylan Reid <dgreid-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
abrestic-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org,
Doug Anderson <dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Subject: Re: [PATCH v2] ARM: tegra: add Acer Chromebook 13 device tree
Date: Mon, 18 Aug 2014 19:03:04 +0200 [thread overview]
Message-ID: <53F231C8.5050309@suse.de> (raw)
In-Reply-To: <53F2255E.7090208-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Am 18.08.2014 18:10, schrieb Stephen Warren:
> On 08/16/2014 09:20 AM, Andreas Färber wrote:
>> Am 13.08.2014 21:14, schrieb Dylan Reid:
>>> + pinmux: pinmux@0,70000868 {
>>> + pinctrl-names = "default";
>>> + pinctrl-0 = <&pinmux_default>;
>>> +
>>> + pinmux_default: common {
>>> + dap_mclk1_pw4 {
>>
>> Any need to have the nodes this way? Shouldn't this rather be
>> dap-mclk1-pw4 as node name by conventions, with a dap_mclk1_pw4 label
>> for referencing if needed? Same below, obviously.
>
> Underscores are consistent with at least all the other Tegra DTs, so I
> think this is best as is.
>
>>> + pwm: pwm@0,7000a000 {
>>
>> Add the label to the .dtsi where the node is first declared? Then you
>> can override it the safer &pwm { ... }; way. Same for all other nodes
>> being extended/overridden here - that's what your colleagues requested
>> for Spring. It'll help with the 80 char limit further below by reducing
>> indentation.
>
> We certainly do have the pwm label in *.dtsi for other SoCs, so we
> should probably move the label there.
>
> Using the &pwm {} syntax would be inconsistent with all the other Tegra
> DTs, and isn't really any safer; the HW isn't going to change, so once
> this is written, it should continue to "just work".
For exactly those consistency reasons I was asked to refactor the whole
set of exynos5250-*.dts files despite having no relation to them -
turning my 1 .dts patch into a large series that still isn't applied...
It's funny and disappointing that every Linux maintainer seems to have
their own conventions, and not even the Google Chrome people can agree
on a common style or live up to what they ask of others.
As for &pwm {}, I understood it's "safer" in that mismatches in the node
name will lead to compilation errors rather than silent runtime misbehavior.
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2014-08-18 17:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 19:14 [PATCH v2] ARM: tegra: add Acer Chromebook 13 device tree Dylan Reid
[not found] ` <1407957267-3258-1-git-send-email-dgreid-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2014-08-16 15:20 ` Andreas Färber
[not found] ` <53EF76CF.9050808-l3A5Bk7waGM@public.gmane.org>
2014-08-18 16:10 ` Stephen Warren
[not found] ` <53F2255E.7090208-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-08-18 17:03 ` Andreas Färber [this message]
2014-08-18 23:24 ` Andrew Bresticker
[not found] ` <CAL1qeaH-WfA-DLKwuXA_hBPHYuXksAibLq__zisrT9ALaRGdAw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-18 23:43 ` Stephen Warren
[not found] ` <53F28F90.3000004-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-08-19 0:11 ` Andrew Bresticker
[not found] ` <CAL1qeaFnfLDOXq07fY4xLfdRpG8FQ63ya+-0Hk+ewA1wXkLOLw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-19 21:47 ` Stephen Warren
[not found] ` <53F3C5FD.4050808-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-08-20 5:36 ` Thierry Reding
2014-08-20 13:37 ` Olof Johansson
[not found] ` <CAOesGMhDe0zFYkUWqBOTunK76wccdKOQ8b+EFAzeTr+oOUQyWA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-20 15:25 ` Thierry Reding
2014-08-20 17:25 ` Andrew Bresticker
2014-08-20 13:29 ` Olof Johansson
[not found] ` <CAOesGMhBdQh_ddycZ-Y5dupR9hW74bogHtG3yyPUJ2tAgWi19A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-20 14:32 ` Thierry Reding
2014-08-20 15:40 ` Olof Johansson
[not found] ` <CAOesGMjFGabNOk0ODjbDN5aaro5309t02+B+UZoM_+q5VE9Ltw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-21 7:19 ` Thierry Reding
2014-08-18 23:05 ` Andrew Bresticker
2014-09-04 19:40 ` Stephen Warren
[not found] ` <5408C023.8060403-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-09-04 20:33 ` Dylan Reid
[not found] ` <CAEUnVG5xdbGZS5pFef0mkCB15pCCFR=vW5rELwU--KTBCT_feQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-04 21:04 ` Stephen Warren
[not found] ` <5408D3F7.5080200-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-09-04 21:08 ` Dylan Reid
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=53F231C8.5050309@suse.de \
--to=afaerber-l3a5bk7wagm@public.gmane.org \
--cc=abrestic-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=dgreid-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).