public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: tessolveupstream@gmail.com
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v10 5/5] arm64: dts: qcom: talos-evk: Add support for QCS615 talos evk board
Date: Tue, 6 Jan 2026 13:00:19 +0530	[thread overview]
Message-ID: <31907a16-1737-4269-92f3-ea998d684396@gmail.com> (raw)
In-Reply-To: <kfjogrtbwpk7mkg4fq2vyve6k6nwccguyxupdwhrcknf3qnahm@xyd545je6u77>



On 06-01-2026 03:43, Dmitry Baryshkov wrote:
> On Sun, Jan 04, 2026 at 07:16:20PM +0530, tessolveupstream@gmail.com wrote:
>>
>>
>> On 30-12-2025 20:21, Konrad Dybcio wrote:
>>> On 12/30/25 2:02 PM, Sudarshan Shetty wrote:
>>>> Add the device tree for the QCS615-based Talos EVK platform. The
>>>> platform is composed of a System-on-Module following the SMARC
>>>> standard, and a Carrier Board.
>>>>
>>>> The Carrier Board supports several display configurations, HDMI and
>>>> LVDS. Both configurations use the same base hardware, with the display
>>>> selection controlled by a DIP switch.
>>>
>>> [...]
>>>
>>>> +		pinctrl-names = "default";
>>>> +		pinctrl-0 = <&wifi_reg_en_pins_state>;
>>>
>>> property-n
>>> property-names
>>>
>>> consistently, please
>>>
>>
>> I didn’t fully understand your comment.
>> Could you please elaborate a bit more so I can make the
>> necessary changes correctly. >> +		regulator-boot-on;
> 
> What is the order of these two properties in most of the other DT files?
> What is the order of them in your patch?
>

I got your point now. I will rearrange the order of the properties
to be consistent with other DT files in the next patch series.
 
>>>> +		regulator-always-on;
>>>> +	};
> 


  reply	other threads:[~2026-01-06  7:29 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-30 13:02 [PATCH v10 0/5] Add Qualcomm Technologies, Inc. Talos EVK SMARC support Sudarshan Shetty
2025-12-30 13:02 ` [PATCH v10 1/5] dt-bindings: arm: qcom: talos-evk: Add QCS615 Talos EVK SMARC platform Sudarshan Shetty
2025-12-30 15:03   ` Krzysztof Kozlowski
2026-01-04 13:11     ` tessolveupstream
2026-01-05  7:12       ` Krzysztof Kozlowski
2026-01-07  6:58         ` tessolveupstream
2026-01-07  7:20           ` Krzysztof Kozlowski
2026-01-07 11:17             ` Konrad Dybcio
2026-01-14  6:53               ` tessolveupstream
2025-12-30 13:02 ` [PATCH v10 2/5] dt-bindings: backlight: gpio-backlight: allow multiple GPIOs Sudarshan Shetty
2026-01-05 15:52   ` Bjorn Andersson
2025-12-30 13:02 ` [PATCH v10 3/5] backlight: gpio: add support for multiple GPIOs for backlight control Sudarshan Shetty
2026-01-05 15:38   ` Bjorn Andersson
2026-01-07  5:57     ` tessolveupstream
2026-01-07  8:12       ` Dmitry Baryshkov
2025-12-30 13:02 ` [PATCH v10 4/5] arm64: dts: qcom: talos: Fix inconsistent USB PHY node naming Sudarshan Shetty
2025-12-30 14:42   ` Dmitry Baryshkov
2026-01-07  8:23   ` yuanjiey
2026-01-08  4:51     ` tessolveupstream
2025-12-30 13:02 ` [PATCH v10 5/5] arm64: dts: qcom: talos-evk: Add support for QCS615 talos evk board Sudarshan Shetty
2025-12-30 14:45   ` Dmitry Baryshkov
2025-12-30 14:51   ` Konrad Dybcio
2026-01-04 13:46     ` tessolveupstream
2026-01-05 22:13       ` Dmitry Baryshkov
2026-01-06  7:30         ` tessolveupstream [this message]
2026-01-08  7:36       ` tessolveupstream
2026-01-08  8:36         ` Konrad Dybcio
2026-01-08 13:02           ` tessolveupstream
2026-01-08 13:06             ` Konrad Dybcio
2026-01-07  8:37   ` yuanjiey
2026-01-08  9:29     ` tessolveupstream
2026-01-08 13:14       ` Konrad Dybcio
2026-01-09  7:21         ` tessolveupstream

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=31907a16-1737-4269-92f3-ea998d684396@gmail.com \
    --to=tessolveupstream@gmail.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.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