From: martinayotte@gmail.com (martinayotte at gmail.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 1/1] add missing UARTs pins for AllWinner H3 DTS + add new I2C entries for AllWinner H3 DTS
Date: Tue, 19 Apr 2016 07:46:08 -0700 (PDT) [thread overview]
Message-ID: <21e74cd8-2ec7-4fd3-aa5c-ba4eed29a6ab@googlegroups.com> (raw)
In-Reply-To: <CAGb2v67e_F1=VaY7ovzW7Whc2ToJU3YabeT-orrLTb0Pouhw_Q@mail.gmail.com>
Hi ChenYu,
Thanks for your comments.
On Tuesday, April 19, 2016 at 7:11:50 AM UTC-4, Chen-Yu Tsai wrote:
> Hi,
>
> > arch/arm/boot/dts/sun8i-h3-orangepi-2.dts | 36 ++++++++++++++
> > arch/arm/boot/dts/sun8i-h3-orangepi-pc.dts | 36 ++++++++++++++
> > arch/arm/boot/dts/sun8i-h3.dtsi | 75
>
> First of all, you are touching 3 different files here. These should
> be separate patches.
I'm trying to understand you here, but I can't. Those 3 files changed are related each other. I could have separated the UART changes from I2C changes, but still those 3 files would have been modified at the same time for a single commit and "git patch-format" would still have created a single patch for the 3 files commit.
Seeing all the patches that coming into the mailing lists, all of them contains multiple files patches, why should it be different here ?
>
> Secondly, our policy is to not have a default function for generic GPIO pins.
>
If this is the official policy, then why so many DTS currently present are not following the same rules, such sun6i-a31-hummingbird, sun7i-a20-olinuxino-micro, sun7i-a20-mk808c, sun7i-a20-cubietruck and so many others ?
I thought the rules were there to make DTS the most default common usage definitions for most end-users in a general availability.
Then, if someone is really in shortage of GPIOs, they could easily turn them back to "disabled" state.
Regards,
Martin.
next prev parent reply other threads:[~2016-04-19 14:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 17:11 [PATCH v1 1/1] add missing UARTs pins for AllWinner H3 DTS + add new I2C entries for AllWinner H3 DTS Martin Ayotte
2016-04-19 11:11 ` Chen-Yu Tsai
2016-04-19 14:46 ` martinayotte at gmail.com [this message]
2016-04-19 15:11 ` Chen-Yu Tsai
2016-04-19 18:27 ` martinayotte at gmail.com
2016-04-19 18:30 ` martinayotte at gmail.com
2016-04-19 19:49 ` [linux-sunxi] " Code Kipper
-- strict thread matches above, loose matches on Subject: below --
2016-04-15 18:20 Martin Ayotte
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=21e74cd8-2ec7-4fd3-aa5c-ba4eed29a6ab@googlegroups.com \
--to=martinayotte@gmail.com \
--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).