All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Peter Geis <pgwipeout@gmail.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
	linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	Michael Riesch <michael.riesch@wolfvision.net>,
	Johan Jonker <jbx6244@gmail.com>, Rob Herring <robh@kernel.org>,
	Ondrej Jirman <megous@megous.com>
Subject: Re: [PATCH v3 0/8] phy-rockchip-inno-usb2: support rk356x usb2phy
Date: Thu, 23 Dec 2021 16:55:19 +0530	[thread overview]
Message-ID: <YcRcn17RMRGsLr5M@matsya> (raw)
In-Reply-To: <20211215210252.120923-1-pgwipeout@gmail.com>

On 15-12-21, 16:02, Peter Geis wrote:
> Good Afternoon,
> 
> This is my series to support the usb2 phy devices on the rk356x.
> The rk356x phy has a single muxed interrupt and has moved the usb2phy
> nodes out of the grf and into their own nodes.
> The phy needs to tie back into the grf for register control, similar to
> the rv1108.
> By moving the phys into their own nodes, they now have full
> #address_cells = 2 register addresses, but they still reside below the 32bit
> mmio range.
> 
> This driver series only supports the host configuration for the rk356x.
> I have have tested it on the following:
> rk3566 - Pine64 Quartz64 Model A
> rk3399 - Pine64 Rockpro64
> 
> Please provide feedback and comments as you see fit.

Applied patches 2-6 to phy-next

Thanks

-- 
~Vinod

-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vkoul@kernel.org>
To: Peter Geis <pgwipeout@gmail.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
	linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	Michael Riesch <michael.riesch@wolfvision.net>,
	Johan Jonker <jbx6244@gmail.com>, Rob Herring <robh@kernel.org>,
	Ondrej Jirman <megous@megous.com>
Subject: Re: [PATCH v3 0/8] phy-rockchip-inno-usb2: support rk356x usb2phy
Date: Thu, 23 Dec 2021 16:55:19 +0530	[thread overview]
Message-ID: <YcRcn17RMRGsLr5M@matsya> (raw)
In-Reply-To: <20211215210252.120923-1-pgwipeout@gmail.com>

On 15-12-21, 16:02, Peter Geis wrote:
> Good Afternoon,
> 
> This is my series to support the usb2 phy devices on the rk356x.
> The rk356x phy has a single muxed interrupt and has moved the usb2phy
> nodes out of the grf and into their own nodes.
> The phy needs to tie back into the grf for register control, similar to
> the rv1108.
> By moving the phys into their own nodes, they now have full
> #address_cells = 2 register addresses, but they still reside below the 32bit
> mmio range.
> 
> This driver series only supports the host configuration for the rk356x.
> I have have tested it on the following:
> rk3566 - Pine64 Quartz64 Model A
> rk3399 - Pine64 Rockpro64
> 
> Please provide feedback and comments as you see fit.

Applied patches 2-6 to phy-next

Thanks

-- 
~Vinod

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vkoul@kernel.org>
To: Peter Geis <pgwipeout@gmail.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
	linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	Michael Riesch <michael.riesch@wolfvision.net>,
	Johan Jonker <jbx6244@gmail.com>, Rob Herring <robh@kernel.org>,
	Ondrej Jirman <megous@megous.com>
Subject: Re: [PATCH v3 0/8] phy-rockchip-inno-usb2: support rk356x usb2phy
Date: Thu, 23 Dec 2021 16:55:19 +0530	[thread overview]
Message-ID: <YcRcn17RMRGsLr5M@matsya> (raw)
In-Reply-To: <20211215210252.120923-1-pgwipeout@gmail.com>

On 15-12-21, 16:02, Peter Geis wrote:
> Good Afternoon,
> 
> This is my series to support the usb2 phy devices on the rk356x.
> The rk356x phy has a single muxed interrupt and has moved the usb2phy
> nodes out of the grf and into their own nodes.
> The phy needs to tie back into the grf for register control, similar to
> the rv1108.
> By moving the phys into their own nodes, they now have full
> #address_cells = 2 register addresses, but they still reside below the 32bit
> mmio range.
> 
> This driver series only supports the host configuration for the rk356x.
> I have have tested it on the following:
> rk3566 - Pine64 Quartz64 Model A
> rk3399 - Pine64 Rockpro64
> 
> Please provide feedback and comments as you see fit.

Applied patches 2-6 to phy-next

Thanks

-- 
~Vinod

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vkoul@kernel.org>
To: Peter Geis <pgwipeout@gmail.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
	linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	Michael Riesch <michael.riesch@wolfvision.net>,
	Johan Jonker <jbx6244@gmail.com>, Rob Herring <robh@kernel.org>,
	Ondrej Jirman <megous@megous.com>
Subject: Re: [PATCH v3 0/8] phy-rockchip-inno-usb2: support rk356x usb2phy
Date: Thu, 23 Dec 2021 16:55:19 +0530	[thread overview]
Message-ID: <YcRcn17RMRGsLr5M@matsya> (raw)
In-Reply-To: <20211215210252.120923-1-pgwipeout@gmail.com>

On 15-12-21, 16:02, Peter Geis wrote:
> Good Afternoon,
> 
> This is my series to support the usb2 phy devices on the rk356x.
> The rk356x phy has a single muxed interrupt and has moved the usb2phy
> nodes out of the grf and into their own nodes.
> The phy needs to tie back into the grf for register control, similar to
> the rv1108.
> By moving the phys into their own nodes, they now have full
> #address_cells = 2 register addresses, but they still reside below the 32bit
> mmio range.
> 
> This driver series only supports the host configuration for the rk356x.
> I have have tested it on the following:
> rk3566 - Pine64 Quartz64 Model A
> rk3399 - Pine64 Rockpro64
> 
> Please provide feedback and comments as you see fit.

Applied patches 2-6 to phy-next

Thanks

-- 
~Vinod

  parent reply	other threads:[~2021-12-23 11:25 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 21:02 [PATCH v3 0/8] phy-rockchip-inno-usb2: support rk356x usb2phy Peter Geis
2021-12-15 21:02 ` Peter Geis
2021-12-15 21:02 ` Peter Geis
2021-12-15 21:02 ` Peter Geis
2021-12-15 21:02 ` [PATCH v3 1/8] dt-bindings: soc: rockchip: add rk3568-usb2phy-grf Peter Geis
2021-12-15 21:02   ` Peter Geis
2021-12-15 21:02   ` Peter Geis
2021-12-15 21:02 ` [PATCH v3 2/8] dt-bindings: phy: phy-rockchip-inno-usb2: add rk3568 documentation Peter Geis
2021-12-15 21:02   ` Peter Geis
2021-12-15 21:02   ` Peter Geis
2021-12-15 21:02   ` Peter Geis
2021-12-16 20:31   ` Rob Herring
2021-12-16 20:31     ` Rob Herring
2021-12-16 20:31     ` Rob Herring
2021-12-16 20:31     ` Rob Herring
2021-12-15 21:02 ` [PATCH v3 3/8] phy: phy-rockchip-inno-usb2: support #address_cells = 2 Peter Geis
2021-12-15 21:02   ` Peter Geis
2021-12-15 21:02   ` Peter Geis
2021-12-15 21:02   ` Peter Geis
2021-12-15 21:02 ` [PATCH v3 4/8] phy: phy-rockchip-inno-usb2: support standalone phy nodes Peter Geis
2021-12-15 21:02   ` Peter Geis
2021-12-15 21:02   ` Peter Geis
2021-12-15 21:02   ` Peter Geis
2021-12-15 21:02 ` [PATCH v3 5/8] phy: phy-rockchip-inno-usb2: support muxed interrupts Peter Geis
2021-12-15 21:02   ` Peter Geis
2021-12-15 21:02   ` Peter Geis
2021-12-15 21:02   ` Peter Geis
2021-12-15 21:02 ` [PATCH v3 6/8] phy: phy-rockchip-inno-usb2: add rk3568 support Peter Geis
2021-12-15 21:02   ` Peter Geis
2021-12-15 21:02   ` Peter Geis
2021-12-15 21:02   ` Peter Geis
2021-12-15 21:02 ` [PATCH v3 7/8] arm64: dts: rockchip: add usb2 nodes to rk3568 device tree Peter Geis
2021-12-15 21:02   ` Peter Geis
2021-12-15 21:02   ` Peter Geis
2021-12-15 21:02 ` [PATCH v3 8/8] arm64: dts: rockchip: add Quartz64-A usb2 support Peter Geis
2021-12-15 21:02   ` Peter Geis
2021-12-15 21:02   ` Peter Geis
2021-12-23 11:25 ` Vinod Koul [this message]
2021-12-23 11:25   ` [PATCH v3 0/8] phy-rockchip-inno-usb2: support rk356x usb2phy Vinod Koul
2021-12-23 11:25   ` Vinod Koul
2021-12-23 11:25   ` Vinod Koul
2021-12-28  0:48 ` (subset) " Heiko Stuebner
2021-12-28  0:48   ` Heiko Stuebner
2021-12-28  0:48   ` Heiko Stuebner
2021-12-28  0:48   ` Heiko Stuebner

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=YcRcn17RMRGsLr5M@matsya \
    --to=vkoul@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=jbx6244@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=megous@megous.com \
    --cc=michael.riesch@wolfvision.net \
    --cc=pgwipeout@gmail.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 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.