public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: David Heidelberg <david@ixit.cz>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	Lukas Timmermann <linux@timmermann.space>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
	Russell King <linux@armlinux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org,
	Alexandre Marquet <tb@a-marquet.fr>
Subject: Re: [PATCH v3 2/3] ARM: dts: exynos: Add Google Manta (Nexus 10)
Date: Mon, 15 Dec 2025 21:53:15 +0100	[thread overview]
Message-ID: <5c780cb5-d605-4568-bb53-e0fc0885f6a0@ixit.cz> (raw)
In-Reply-To: <cc15ff73-7322-41a9-b0db-a321d6835c36@kernel.org>

On 15/12/2025 21:33, Krzysztof Kozlowski wrote:
> On 15/12/2025 21:06, David Heidelberg wrote:
>>>>> +	aliases {
>>>>> +		mmc0 = &mmc_0; /* eMMC */
>>>>> +		mmc1 = &mmc_1; /* WiFi */
>>>>> +	};
>>>>> +
>>>>> +	bmp180_vdda_reg: regulator-bmp180-vdda {
>>>>> +		compatible = "regulator-fixed";
>>>>> +		regulator-name = "BMP180_VDDA";
>>>>> +	};
>>>> something-something-regulator (all occurences within the DTS)
>>>>
>>>
>>> I don't understand this suggestion.
>>
>> oh right, let me clarify,
>>
>> the regulator name should end with -regulator postfix.
> 
> That is not a correct suggestion for none of the SoC trees. If you
> wanted to be consistent with old Exynos, then look at the sources - this
> is voltage-regulator. But if we are nitpicking on that, this should be
> either matching new code (regulator) or even the new style from DT bindings.

Oh, sorry, my bad.

> 
> You have never reviewed anything on samsung-soc, so I wonder if this is
> result of cc-ing this phone-devel. If that's the case, that list should
> be just ignored.
> 
> Please do not nitpick on such stuff, especially on things not being
> correct in terms of recommended style or bindings.

Ok, sure.

Please ignore my review.

David

> 
> 
> Best regards,
> Krzysztof


  reply	other threads:[~2025-12-15 20:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-15 15:05 [PATCH v3 0/3] Add support for exynos5250-manta (Google Nexus 10) Lukas Timmermann
2025-12-15 15:05 ` [PATCH v3 1/3] dt-bindings: ARM: samsung: Add Google Manta (Nexus 10) Lukas Timmermann
2025-12-15 15:05 ` [PATCH v3 2/3] ARM: dts: exynos: " Lukas Timmermann
2025-12-15 18:53   ` David Heidelberg
2025-12-15 19:33     ` Krzysztof Kozlowski
2025-12-15 20:06       ` David Heidelberg
2025-12-15 20:33         ` Krzysztof Kozlowski
2025-12-15 20:53           ` David Heidelberg [this message]
2025-12-17  8:22   ` Krzysztof Kozlowski
2025-12-15 15:05 ` [PATCH v3 3/3] ARM: samsung: exynos5250: Allow CPU1 to boot Lukas Timmermann
2025-12-18 19:19   ` Henrik Grimler
2025-12-16 13:11 ` [PATCH v3 0/3] Add support for exynos5250-manta (Google Nexus 10) Rob Herring
2025-12-17  8:18 ` Krzysztof Kozlowski

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=5c780cb5-d605-4568-bb53-e0fc0885f6a0@ixit.cz \
    --to=david@ixit.cz \
    --cc=alim.akhtar@samsung.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=linux@timmermann.space \
    --cc=phone-devel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=tb@a-marquet.fr \
    /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