Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Marek Vasut <marex@nabladev.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
	Fedor Ross <fedor.ross@ifm.com>,
	Christian Eggers <ceggers@arri.de>,
	Conor Dooley <conor+dt@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Markus Heidelberg <m.heidelberg@cab.de>,
	Rob Herring <robh@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
	devicetree@vger.kernel.org, imx@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 4/4] arm64: dts: imx8mn: Add ifm VHIP4 EvalBoard v1 and v2
Date: Tue, 30 Dec 2025 22:28:27 +0100	[thread overview]
Message-ID: <8df1ff09-a5be-418f-9723-3f64bf97eba8@nabladev.com> (raw)
In-Reply-To: <CAOMZO5Aa6iDg2u-sJu1yPZX8T2wE=QVzwSbxjZHo1bMwfDW5HQ@mail.gmail.com>

On 12/30/25 7:52 PM, Fabio Estevam wrote:
> On Tue, Dec 30, 2025 at 3:41 PM Marek Vasut <marex@nabladev.com> wrote:
> 
>> +&gpio4 {
>> +       /*
>> +        * Hog USB-nRESET high here, since neither U-Boot nor Linux
>> +        * has any support for USB Hub GPIO reset so far.
> 
> Which USB hub chip is used?
USB2512B , so I can use this.

Both temp sensor node names are also updated.

Thanks.

      reply	other threads:[~2025-12-30 21:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-30 18:40 [PATCH v3 1/4] dt-bindings: vendor-prefixes: Document ifm electronic gmbh Marek Vasut
2025-12-30 18:40 ` [PATCH v3 2/4] dt-bindings: arm: fsl: Document ifm VHIP4 EvalBoard v1 and v2 Marek Vasut
2025-12-30 18:41 ` [PATCH v3 3/4] arm64: dts: imx8mn: Add SNVS LPGPR Marek Vasut
2025-12-30 18:41 ` [PATCH v3 4/4] arm64: dts: imx8mn: Add ifm VHIP4 EvalBoard v1 and v2 Marek Vasut
2025-12-30 18:52   ` Fabio Estevam
2025-12-30 21:28     ` Marek Vasut [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=8df1ff09-a5be-418f-9723-3f64bf97eba8@nabladev.com \
    --to=marex@nabladev.com \
    --cc=ceggers@arri.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=fedor.ross@ifm.com \
    --cc=festevam@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=imx@lists.linux.dev \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.heidelberg@cab.de \
    --cc=robh@kernel.org \
    --cc=shawnguo@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