devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: Thierry Reding <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Rob Herring <robh+dt@kernel.org>,
	David Heidelberg <david@ixit.cz>,
	Svyatoslav Ryhel <clamor95@gmail.com>,
	Anton Bambura <jenneron@protonmail.com>,
	Antoni Aloy Torrens <aaloytorrens@gmail.com>,
	Nikola Milosavljevic <mnidza@outlook.com>,
	Ion Agorria <ion@agorria.com>,
	Ihor Didenko <tailormoon@rambler.ru>,
	Andreas Westman Dorcsak <hedmoo@yahoo.com>,
	Maxim Schwalm <maxim.schwalm@gmail.com>,
	Raffaele Tranquillini <raffaele.tranquillini@gmail.com>,
	Jasper Korten <jja2000@gmail.com>,
	Thomas Graichen <thomas.graichen@gmail.com>,
	devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 05/14] ARM: tegra: Add device-tree for ASUS Transformer Prime TF201
Date: Mon, 29 Nov 2021 00:31:34 +0300	[thread overview]
Message-ID: <8762c5e6-1ec0-4412-b3db-968551e15b30@gmail.com> (raw)
In-Reply-To: <YaLgpb2hQGzQXrej@qmqm.qmqm.pl>

28.11.2021 04:51, Michał Mirosław пишет:
> On Sat, Nov 27, 2021 at 05:23:18PM +0300, Dmitry Osipenko wrote:
>> From: Svyatoslav Ryhel <clamor95@gmail.com>
>>
>> Add device-tree for ASUS Transformer Prime TF201, which is NVIDIA
>> Tegra30-based tablet device.
>>
>> Co-developed-by: Ion Agorria <ion@agorria.com>
>> Signed-off-by: Ion Agorria <ion@agorria.com>
>> Co-developed-by: Maxim Schwalm <maxim.schwalm@gmail.com>
>> Signed-off-by: Maxim Schwalm <maxim.schwalm@gmail.com>
>> Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
>> ---
>>  arch/arm/boot/dts/Makefile                    |    1 +
>>  .../boot/dts/tegra30-asus-lvds-display.dtsi   |   46 +
>>  arch/arm/boot/dts/tegra30-asus-tf201.dts      |  623 ++++++
>>  .../dts/tegra30-asus-transformer-common.dtsi  | 1741 +++++++++++++++++
>>  4 files changed, 2411 insertions(+)
>>  create mode 100644 arch/arm/boot/dts/tegra30-asus-lvds-display.dtsi
>>  create mode 100644 arch/arm/boot/dts/tegra30-asus-tf201.dts
>>  create mode 100644 arch/arm/boot/dts/tegra30-asus-transformer-common.dtsi
> 
> I think the common.dtsi is combined from all the DT authors, so they all
> should be mentioned in the co-developed/signed-off lines. (Or maybe just
> split the common part out if you want to be more specific in assigning
> credits?)

I'll factor out the common part into separate patch and will make you
the author of that patch since it really was derived from yours original
TF300T DT. I actually wanted to do that previously, it's good that you
reminded about it.

>> +	i2c@7000c400 {
>> +		/* Atmel MXT768E touchscreen */
>> +		touchscreen@4d {
> [...]
>> +			interrupt-parent = <&gpio>;
>> +			interrupts = <TEGRA_GPIO(H, 4) IRQ_TYPE_EDGE_FALLING>;
> [...]
> 
> Nit: This could use 'interrupts-extended' as it's more readable, I think.
> (There are similar cases in other DTs.)

I don't have objections, although the classic variant is also good to me.

I don't think that it makes sense to change only the Transformer DTs to
use 'interrupts-extended'. I'd suggest to create a followup patches that
will cleanup and improve all Tegra device-trees together, making them
all more uniform and nicer to look.

>> +	uartb: serial@70006040 {
>> +		compatible = "nvidia,tegra30-hsuart";
> [...]
> 
> I wonder why isn't this in the tegra30.dtsi? The DT shouldn't select a
> driver - it should only describe the hardware.

The "nvidia,tegra30-hsuart" implies that UART port is capable of
performing the high speed transfers, which should be board dependent.
Meanwhile "nvidia,tegra30-uart" should work for all hardware variants.
That's how I understand it.

The comment in the Tegra dtsi really shouldn't refer to the drivers.
Changing that comment should be material for a separate patch. It could
become a part of the DT cleanup patches together with the
'interrupts-extended' changes.

  reply	other threads:[~2021-11-28 21:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-27 14:23 [PATCH v3 00/14] NVIDIA Tegra ARM32 device-tree patches for 5.17 (new devices and more) Dmitry Osipenko
2021-11-27 14:23 ` [PATCH v3 01/14] dt-bindings: ARM: tegra: Document ASUS Transformers Dmitry Osipenko
2021-11-29  1:21   ` Rob Herring
2021-11-27 14:23 ` [PATCH v3 02/14] dt-bindings: ARM: tegra: Document Pegatron Chagall Dmitry Osipenko
2021-11-29  1:21   ` Rob Herring
2021-11-27 14:23 ` [PATCH v3 03/14] ARM: tegra: Add labels to tegra114.dtsi Dmitry Osipenko
2021-11-28  1:32   ` Michał Mirosław
2021-11-28 21:12     ` Dmitry Osipenko
2021-11-27 14:23 ` [PATCH v3 04/14] ARM: tegra: Add device-tree for ASUS Transformer EeePad TF101 Dmitry Osipenko
2021-11-27 14:23 ` [PATCH v3 05/14] ARM: tegra: Add device-tree for ASUS Transformer Prime TF201 Dmitry Osipenko
2021-11-28  1:51   ` Michał Mirosław
2021-11-28 21:31     ` Dmitry Osipenko [this message]
2021-11-27 14:23 ` [PATCH v3 06/14] ARM: tegra: Add device-tree for ASUS Transformer Pad TF300T Dmitry Osipenko
2021-11-27 14:23 ` [PATCH v3 07/14] ARM: tegra: Add device-tree for ASUS Transformer Pad TF300TG Dmitry Osipenko
2021-11-27 14:23 ` [PATCH v3 08/14] ARM: tegra: Add device-tree for ASUS Transformer Infinity TF700T Dmitry Osipenko
2021-11-27 14:23 ` [PATCH v3 09/14] ARM: tegra: Add device-tree for ASUS Transformer Pad TF701T Dmitry Osipenko
2021-11-27 14:23 ` [PATCH v3 10/14] ARM: tegra: Add device-tree for Pegatron Chagall tablet Dmitry Osipenko
2021-11-27 14:23 ` [PATCH v3 11/14] ARM: tegra: Add device-tree for 1080p version of Nyan Big Dmitry Osipenko
2021-11-27 14:23 ` [PATCH v3 12/14] ARM: tegra: Name clock and regulator nodes according to DT-schema Dmitry Osipenko
2021-11-27 14:23 ` [PATCH v3 13/14] ARM: tegra: nexus7: Drop clock-frequency from NFC node Dmitry Osipenko
2021-11-27 14:23 ` [PATCH v3 14/14] ARM: tegra: Enable video decoder on Tegra114 Dmitry Osipenko

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=8762c5e6-1ec0-4412-b3db-968551e15b30@gmail.com \
    --to=digetx@gmail.com \
    --cc=aaloytorrens@gmail.com \
    --cc=clamor95@gmail.com \
    --cc=david@ixit.cz \
    --cc=devicetree@vger.kernel.org \
    --cc=hedmoo@yahoo.com \
    --cc=ion@agorria.com \
    --cc=jenneron@protonmail.com \
    --cc=jja2000@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=maxim.schwalm@gmail.com \
    --cc=mirq-linux@rere.qmqm.pl \
    --cc=mnidza@outlook.com \
    --cc=raffaele.tranquillini@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=tailormoon@rambler.ru \
    --cc=thierry.reding@gmail.com \
    --cc=thomas.graichen@gmail.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;
as well as URLs for NNTP newsgroup(s).