From: Krzysztof Kozlowski <krzk@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alexander Stein <alexander.stein@ew.tq-group.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Oleksij Rempel <o.rempel@pengutronix.de>,
Matthias Kaehlcke <mka@chromium.org>,
Fabio Estevam <festevam@gmail.com>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 2/8] dt-bindings: net: asix,ax88178: document the AX88179
Date: Thu, 13 Aug 2026 11:50:44 +0200 [thread overview]
Message-ID: <20260813-macho-analytic-mandrill-c37ac1@quoll> (raw)
In-Reply-To: <20260810-msm8974-onboard-usb-v1-2-08a805768328@oss.qualcomm.com>
On Mon, Aug 10, 2026 at 03:42:33AM +0300, Dmitry Baryshkov wrote:
> The APQ8074 Dragonboard has an onboard ASIX AX88179 USB 3.0 Gigabit
> Ethernet controller whose RESET_N pin is wired to a PMIC GPIO, so the
> device has to be described in DT for the OS to release it from reset.
Would be nice if you checked other devices from this schema if they have
reset-gpios as well. I think they do (confirmed on AX88772 and
AX88772A), but having this explicit would spare us from validating it by
outselves.
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-08-13 9:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 0:42 [PATCH 0/8] usb: misc: onboard_usb_dev: support several devices Dmitry Baryshkov
2026-08-10 0:42 ` [PATCH 1/8] dt-bindings: usb: ti,usb8041: document the TUSB8040A hub Dmitry Baryshkov
2026-08-13 9:45 ` Krzysztof Kozlowski
2026-08-10 0:42 ` [PATCH 2/8] dt-bindings: net: asix,ax88178: document the AX88179 Dmitry Baryshkov
2026-08-13 9:50 ` Krzysztof Kozlowski [this message]
2026-08-10 0:42 ` [PATCH 3/8] dt-bindings: usb: document the Prolific PL2775 USB-SATA bridge Dmitry Baryshkov
2026-08-13 9:53 ` Krzysztof Kozlowski
2026-08-10 0:42 ` [PATCH 4/8] dt-bindings: usb: microchip,usb2514: document the USB4604 hub Dmitry Baryshkov
2026-08-13 9:53 ` Krzysztof Kozlowski
2026-08-10 0:42 ` [PATCH 5/8] usb: misc: onboard_usb_dev: add support for the TI TUSB8040A hub Dmitry Baryshkov
2026-08-10 0:42 ` [PATCH 6/8] usb: misc: onboard_usb_dev: add support for the ASIX AX88179 Dmitry Baryshkov
2026-08-10 0:42 ` [PATCH 7/8] usb: misc: onboard_usb_dev: add support for the Prolific PL2775 Dmitry Baryshkov
2026-08-10 0:42 ` [PATCH 8/8] usb: misc: onboard_usb_dev: add support for the SMSC USB4604 Dmitry Baryshkov
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=20260813-macho-analytic-mandrill-c37ac1@quoll \
--to=krzk@kernel.org \
--cc=alexander.stein@ew.tq-group.com \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=edumazet@google.com \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mka@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--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