All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Remmet <J.Remmet@phytec.de>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"upstream@lists.phytec.de" <upstream@lists.phytec.de>
Subject: Re: [PATCH] usb: typec: hd3ss3220: Check if regulator needs to be switched
Date: Mon, 26 Jan 2026 15:22:01 +0000	[thread overview]
Message-ID: <1c36ebc4-9a37-4e88-a39f-e6472c0df11b@phytec.de> (raw)
In-Reply-To: <aXd7EN9KAmtEHODq@kuha>

Am 26.01.26 um 15:32 schrieb Heikki Krogerus:
> Mon, Jan 26, 2026 at 01:06:36PM +0100, Jan Remmet kirjoitti:
>> Check regulator state as peripheral and detach can disable vbus.
>> Without this check we will try to disable the regulator twice if
>> we disconnect host and then connect as device.
>>
>> Signed-off-by: Jan Remmet <j.remmet@phytec.de>
>> ---
>> This is a fixup from
>> - Link to v1: https://lore.kernel.org/r/20260115-wip-jremmet-hd3ss3220_vbus-v1-1-b7d9adfbe346@phytec.de
>> To
>> - Link to v2: https://lore.kernel.org/r/20260123-wip-jremmet-hd3ss3220_vbus-v2-1-bcad313ce92b@phytec.de
> 
> I don't understand that, but I think you are fixing a commit in Greg's
> tree, right?
Yes
> 
> If that's the case, then you need the Fixes tag.

Sorry, I'm not familar with the workflow here. Should it be a "--fixup" 
git commit against the usb-next commit id?

Or
Fixes: 7e7025811579 ("usb: typec: hd3ss3220: Check if regulator needs to 
be switched")

In the commit message (again with commit sha from Greg's usb-next

Jan

> 
> thanks,
> 
>> ---
>>   drivers/usb/typec/hd3ss3220.c | 3 +++
>>   1 file changed, 3 insertions(+)
>>
>> diff --git a/drivers/usb/typec/hd3ss3220.c b/drivers/usb/typec/hd3ss3220.c
>> index a7c54aa8635f70d6979d98c95f80d4dac277fef2..3e39b800e6b5f4d0cbba957c0dd66c18f781ff38 100644
>> --- a/drivers/usb/typec/hd3ss3220.c
>> +++ b/drivers/usb/typec/hd3ss3220.c
>> @@ -208,6 +208,9 @@ static void hd3ss3220_regulator_control(struct hd3ss3220 *hd3ss3220, bool on)
>>   {
>>   	int ret;
>>   
>> +	if (regulator_is_enabled(hd3ss3220->vbus) == on)
>> +		return;
>> +
>>   	if (on)
>>   		ret = regulator_enable(hd3ss3220->vbus);
>>   	else
>>
>> ---
>> base-commit: 8acc379b664ec987dcc7eca25a5f5c4a9a4eb9c4
>> change-id: 20260126-wip-jremmet-hd3ss3220_vbus_split-946802479e89
>>
>> Best regards,
>> -- 
>> Jan Remmet <j.remmet@phytec.de>
> 


-- 
Mit freundlichen Grüßen / best regards
Jan Remmet

- Software Development -
PHYTEC Messtechnik GmbH
Barcelona-Allee 1
55129 Mainz
Germany
Tel.: +49 (0)6131 9221-53
Mail: j.remmet@pyhtec.de
Web: www.phytec.de

Sie finden uns auch auf: Facebook, LinkedIn, Xing, YouTube

PHYTEC Messtechnik GmbH | Barcelona-Allee 1 | 55129 Mainz, Germany
Geschäftsführer: Dipl.-Ing. Michael Mitezki, Dipl.-Ing. Bodo Huber, 
Dipl.-Ing. (FH) Marcus Lickes | Handelsregister Mainz HRB 4656 | 
Finanzamt Mainz | St.-Nr.: 26/665/00608, USt-ID: DE 149059855
This E-Mail may contain confidential or privileged information. If you 
are not the intended recipient (or have received this E-Mail in error) 
please notify the sender immediately and destroy this E-Mail. Any 
unauthorized copying, disclosure or distribution of the material in this 
E-Mail is strictly forbidden.

  reply	other threads:[~2026-01-26 15:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-26 12:06 [PATCH] usb: typec: hd3ss3220: Check if regulator needs to be switched Jan Remmet
2026-01-26 14:32 ` Heikki Krogerus
2026-01-26 15:22   ` Jan Remmet [this message]
2026-01-27 14:21     ` Greg Kroah-Hartman

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=1c36ebc4-9a37-4e88-a39f-e6472c0df11b@phytec.de \
    --to=j.remmet@phytec.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=krishna.kurapati@oss.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=upstream@lists.phytec.de \
    /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.