mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kishon Vijay Abraham I <kishon@ti.com>
To: Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-sunxi@googlegroups.com>
Cc: Maxime Ripard <maxime.ripard@bootlin.com>,
	Chen-Yu Tsai <wens@csie.org>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Jagan Teki <jagan@openedev.com>,
	Hans de Goede <hdegoede@redhat.com>
Subject: Re: [PATCH] phy: sun4i-usb: Make sure to disable PHY0 passby for peripheral mode
Date: Wed, 17 Apr 2019 11:02:58 +0530	[thread overview]
Message-ID: <63a12a83-8ea8-40de-d086-9971c93d57f6@ti.com> (raw)
In-Reply-To: <30b3c2548772d13f54284fcf16ed941de88f72cc.camel@bootlin.com>



On 15/04/19 4:47 PM, Paul Kocialkowski wrote:
> Hi,
> 
> Le jeudi 14 mars 2019 à 14:05 +0100, Paul Kocialkowski a écrit :
>> On platforms where the MUSB and HCI controllers share PHY0, PHY passby
>> is required when using the HCI controller with the PHY, but it must be
>> disabled when the MUSB controller is used instead.
>>
>> Without this, PHY0 passby is always enabled, which results in broken
>> peripheral mode on such platforms (e.g. H3/H5).
>>
>> Fixes: ba4bdc9e1dc0 ("PHY: sunxi: Add driver for sunxi usb phy")
> 
> Does anyone have feedback about this? I was hoping to get it merged
> rather soon since it pretty much fixes USB gadget on H3/R40/V3/V3s.

merged now, thanks.

-Kishon
> 
> Cheers,
> 
> Paul
> 
>> Signed-off-by: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
>> ---
>>  drivers/phy/allwinner/phy-sun4i-usb.c | 4 ++++
>>  1 file changed, 4 insertions(+)
>>
>> diff --git a/drivers/phy/allwinner/phy-sun4i-usb.c b/drivers/phy/allwinner/phy-sun4i-usb.c
>> index 5163097b43df..7b23920e0068 100644
>> --- a/drivers/phy/allwinner/phy-sun4i-usb.c
>> +++ b/drivers/phy/allwinner/phy-sun4i-usb.c
>> @@ -551,6 +551,7 @@ static void sun4i_usb_phy0_id_vbus_det_scan(struct work_struct *work)
>>  	struct sun4i_usb_phy_data *data =
>>  		container_of(work, struct sun4i_usb_phy_data, detect.work);
>>  	struct phy *phy0 = data->phys[0].phy;
>> +	struct sun4i_usb_phy *phy = phy_get_drvdata(phy0);
>>  	bool force_session_end, id_notify = false, vbus_notify = false;
>>  	int id_det, vbus_det;
>>  
>> @@ -607,6 +608,9 @@ static void sun4i_usb_phy0_id_vbus_det_scan(struct work_struct *work)
>>  			mutex_unlock(&phy0->mutex);
>>  		}
>>  
>> +		/* Enable PHY0 passby for host mode only. */
>> +		sun4i_usb_phy_passby(phy, !id_det);
>> +
>>  		/* Re-route PHY0 if necessary */
>>  		if (data->cfg->phy0_dual_route)
>>  			sun4i_usb_phy0_reroute(data, id_det);

      reply	other threads:[~2019-04-17  5:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-14 13:05 Paul Kocialkowski
2019-04-15 11:17 ` Paul Kocialkowski
2019-04-17  5:32   ` Kishon Vijay Abraham I [this message]

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=63a12a83-8ea8-40de-d086-9971c93d57f6@ti.com \
    --to=kishon@ti.com \
    --cc=hdegoede@redhat.com \
    --cc=jagan@openedev.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=maxime.ripard@bootlin.com \
    --cc=paul.kocialkowski@bootlin.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=wens@csie.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

all inboxes | Powered by JetHome®