From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Kees Cook <keescook@chromium.org>,
Maxim Schwalm <maxim.schwalm@gmail.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v2 3/3] ARM: tegra: Add device-tree for LG Optimus 4X HD (P880)
Date: Thu, 1 Feb 2024 11:22:09 +0100 [thread overview]
Message-ID: <1bcba074-0fd4-4f0d-997b-a0c8e5d881cb@linaro.org> (raw)
In-Reply-To: <CAPVz0n3VnEAxHviOF1RVzMybVEe=BdMcpPFpZXvpoU7HizTNog@mail.gmail.com>
On 01/02/2024 10:51, Svyatoslav Ryhel wrote:
> чт, 1 лют. 2024 р. о 11:22 Krzysztof Kozlowski
> <krzysztof.kozlowski@linaro.org> пише:
>>
>> On 01/02/2024 10:20, Svyatoslav Ryhel wrote:
>>> + pinmux@70000868 {
>>> + pinctrl-names = "default";
>>> + pinctrl-0 = <&state_default>;
>>> +
>>> + state_default: pinmux {
>>> + /* WLAN SDIO pinmux */
>>> + host_wlan_wake {
>>
>> Not much improved around this.
>>
>
> All existing tegra pinmux nodes are bind this way. Ask Thierry Reding
> about this pls.
What does it mean? Are you override node or not? If not, why it cannot
have proper name?
Best regards,
Krzysztof
prev parent reply other threads:[~2024-02-01 10:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 9:20 [PATCH v2 0/3] Tegra30: add support for LG tegra based phones Svyatoslav Ryhel
2024-02-01 9:20 ` [PATCH v2 1/3] dt-bindings: arm: tegra: Add LG Optimus Vu P895 and Optimus 4X P880 Svyatoslav Ryhel
2024-02-01 9:21 ` Krzysztof Kozlowski
2024-02-01 9:20 ` [PATCH v2 2/3] ARM: tegra: Add device-tree for LG Optimus Vu (P895) Svyatoslav Ryhel
2024-02-01 9:20 ` [PATCH v2 3/3] ARM: tegra: Add device-tree for LG Optimus 4X HD (P880) Svyatoslav Ryhel
2024-02-01 9:22 ` Krzysztof Kozlowski
2024-02-01 9:51 ` Svyatoslav Ryhel
2024-02-01 10:22 ` Krzysztof Kozlowski [this message]
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=1bcba074-0fd4-4f0d-997b-a0c8e5d881cb@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=keescook@chromium.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maxim.schwalm@gmail.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@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