All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <mani@kernel.org>
To: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
Cc: Vinod Koul <vkoul@kernel.org>,
	 Neil Armstrong <neil.armstrong@linaro.org>,
	Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	 linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,  linux-arm-msm@vger.kernel.org,
	linux-usb@vger.kernel.org,
	 Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: Re: [PATCH v7 0/5] Modify interrupt handling for eUSB2 Phy targets
Date: Mon, 12 Oct 2026 19:01:03 +0530	[thread overview]
Message-ID: <aszg7Us_ACMMiM9N@debian> (raw)
In-Reply-To: <20260905-eusb2-interrupt-v7-v7-0-820cf5377a70@oss.qualcomm.com>

On Sat, Sep 05, 2026 at 08:59:04PM +0530, Krishna Kurapati wrote:
> eUSB2 targets handle wakeup interrupts differently depending on device
> speed when operating in host mode.
> 
> According to the eUSB2 specification, remote wakeup signaling in host
> mode is detected via different data-line assertions based on the
> connected device speed.
> 
> When a low-speed device is connected, the host repeater drives eD+ to
> logic '1' upon detecting a K-state on the USB lines during remote wakeup
> (eUSB2 specification, Section 5.5.14).
> 
> When a full-speed or high-speed device is connected, the host repeater
> drives eD- to logic '1' upon detecting a K-state on the USB line during
> remote wakeup (eUSB2 specification, Sections 5.5.15 and 5.5.18).
> 
> Since the eUSB2 PHY's "DP" and "DM" interrupt lines monitor the eD+ and
> eD- line states, configure the wakeup interrupts accordingly
> 
> Add support for a new phy "type" attribute to be set by eusb2 phy drivers
> and be read by consumers (in this case usb controller) and act accordingly
> 
> Changes pushed on top of usb-testing branch. And v7 is only compile tested.
> 

I believe the merge strategy is to merge all the patches through PHY tree. If
anyone feel otherwise, please yell at me.

- Mani

-- 
மணிவண்ணன் சதாசிவம்

-- 
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: Manivannan Sadhasivam <mani@kernel.org>
To: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
Cc: Vinod Koul <vkoul@kernel.org>,
	 Neil Armstrong <neil.armstrong@linaro.org>,
	Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	 linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,  linux-arm-msm@vger.kernel.org,
	linux-usb@vger.kernel.org,
	 Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: Re: [PATCH v7 0/5] Modify interrupt handling for eUSB2 Phy targets
Date: Mon, 12 Oct 2026 19:01:03 +0530	[thread overview]
Message-ID: <aszg7Us_ACMMiM9N@debian> (raw)
In-Reply-To: <20260905-eusb2-interrupt-v7-v7-0-820cf5377a70@oss.qualcomm.com>

On Sat, Sep 05, 2026 at 08:59:04PM +0530, Krishna Kurapati wrote:
> eUSB2 targets handle wakeup interrupts differently depending on device
> speed when operating in host mode.
> 
> According to the eUSB2 specification, remote wakeup signaling in host
> mode is detected via different data-line assertions based on the
> connected device speed.
> 
> When a low-speed device is connected, the host repeater drives eD+ to
> logic '1' upon detecting a K-state on the USB lines during remote wakeup
> (eUSB2 specification, Section 5.5.14).
> 
> When a full-speed or high-speed device is connected, the host repeater
> drives eD- to logic '1' upon detecting a K-state on the USB line during
> remote wakeup (eUSB2 specification, Sections 5.5.15 and 5.5.18).
> 
> Since the eUSB2 PHY's "DP" and "DM" interrupt lines monitor the eD+ and
> eD- line states, configure the wakeup interrupts accordingly
> 
> Add support for a new phy "type" attribute to be set by eusb2 phy drivers
> and be read by consumers (in this case usb controller) and act accordingly
> 
> Changes pushed on top of usb-testing branch. And v7 is only compile tested.
> 

I believe the merge strategy is to merge all the patches through PHY tree. If
anyone feel otherwise, please yell at me.

- Mani

-- 
மணிவண்ணன் சதாசிவம்

  parent reply	other threads:[~2026-10-12 13:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-05 15:29 [PATCH v7 0/5] Modify interrupt handling for eUSB2 Phy targets Krishna Kurapati
2026-09-05 15:29 ` Krishna Kurapati
2026-09-05 15:29 ` [PATCH v7 1/5] dt-bindings: phy: Add PHY_TYPE_EUSB2 definition Krishna Kurapati
2026-09-05 15:29   ` Krishna Kurapati
2026-09-10 15:53   ` Manivannan Sadhasivam
2026-09-10 15:53     ` Manivannan Sadhasivam
2026-09-05 15:29 ` [PATCH v7 2/5] include: linux: phy: Add phy attribute "type" and associated helpers Krishna Kurapati
2026-09-05 15:29   ` Krishna Kurapati
2026-09-10 15:54   ` Manivannan Sadhasivam
2026-09-10 15:54     ` Manivannan Sadhasivam
2026-09-05 15:29 ` [PATCH v7 3/5] phy: snps-eusb2: Set phy type to EUSB2 Krishna Kurapati
2026-09-05 15:29   ` Krishna Kurapati
2026-09-10 15:55   ` Manivannan Sadhasivam
2026-09-10 15:55     ` Manivannan Sadhasivam
2026-09-05 15:29 ` [PATCH v7 4/5] phy: qcom: m31-eusb2: " Krishna Kurapati
2026-09-05 15:29   ` Krishna Kurapati
2026-09-10 15:56   ` Manivannan Sadhasivam
2026-09-10 15:56     ` Manivannan Sadhasivam
2026-09-05 15:29 ` [PATCH v7 5/5] usb: dwc3: qcom: Modify interrupt handling for eUSB2 Phy targets Krishna Kurapati
2026-09-05 15:29   ` Krishna Kurapati
2026-09-05 15:40   ` sashiko-bot
2026-09-05 15:40     ` sashiko-bot
2026-09-09 13:00   ` Konrad Dybcio
2026-09-09 13:00     ` Konrad Dybcio
2026-10-12 13:31 ` Manivannan Sadhasivam [this message]
2026-10-12 13:31   ` [PATCH v7 0/5] " Manivannan Sadhasivam
2026-10-13  8:39   ` Krishna Kurapati
2026-10-13  8:39     ` Krishna Kurapati

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=aszg7Us_ACMMiM9N@debian \
    --to=mani@kernel.org \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=krishna.kurapati@oss.qualcomm.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=robh@kernel.org \
    --cc=vkoul@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.