From: Tony Lindgren <tony@atomide.com>
To: Julien Panis <jpanis@baylibre.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, vigneshr@ti.com, nm@ti.com
Subject: Re: [PATCH 0/3] Configure usb0 as peripheral on am335x boards
Date: Fri, 30 Jun 2023 10:20:47 +0300 [thread overview]
Message-ID: <20230630072047.GK14287@atomide.com> (raw)
In-Reply-To: <20230629-usb0-as-peripheral-v1-0-167f78a11746@baylibre.com>
Hi,
* Julien Panis <jpanis@baylibre.com> [230629 13:10]:
> This series configures usb0 dr_mode as 'peripheral' for am335x-evm,
> am335x-evmsk, and am335x-icev2. This USB port is mainly used for
> RNDIS and DFU.
Is this a mini-B connector? Just wondering if it was originally attempted
to be configured as OTG or how it ended up with a host configuration..
> Initially, a series was submitted to overlay dr_mode in u-boot specific
> device trees ('<board>-u-boot.dtsi'):
> https://lore.kernel.org/all/20230621-fix_usb_ether_init-v2-0-ff121f0e8d7a@baylibre.com/
>
> It was finally decided to modify linux device trees.
Do we need these as fixes? If so is there a fixes tag for these?
Regards,
Tony
next prev parent reply other threads:[~2023-06-30 7:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 13:09 [PATCH 0/3] Configure usb0 as peripheral on am335x boards Julien Panis
2023-06-29 13:09 ` [PATCH 1/3] ARM: dts: am335x-evm: Use usb0 as peripheral Julien Panis
2023-06-29 13:09 ` [PATCH 2/3] ARM: dts: am335x-evmsk: " Julien Panis
2023-06-29 13:09 ` [PATCH 3/3] ARM: dts: am335x-icev2: " Julien Panis
2023-06-30 7:20 ` Tony Lindgren [this message]
2023-06-30 8:30 ` [PATCH 0/3] Configure usb0 as peripheral on am335x boards Julien Panis
2023-06-30 19:40 ` Roger Quadros
2023-07-03 11:56 ` Julien Panis
2023-07-03 13:44 ` Roger Quadros
2023-07-03 14:14 ` Julien Panis
2023-07-03 15:27 ` Roger Quadros
2023-07-03 15:51 ` Julien Panis
2023-07-06 3:51 ` Tony Lindgren
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=20230630072047.GK14287@atomide.com \
--to=tony@atomide.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jpanis@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.