mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>
To: John Keeping <john@metanate.com>,
	Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>
Cc: Felipe Balbi <balbi@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb: dwc2: Implement set_selfpowered()
Date: Wed, 5 Feb 2020 12:05:37 +0000	[thread overview]
Message-ID: <326e87da-1ac6-33de-1d6f-5ba4852c7e99@synopsys.com> (raw)
In-Reply-To: <20200205115656.3c698385.john@metanate.com>

Hi,

On 2/5/2020 3:56 PM, John Keeping wrote:
> Hi Minas,
> 
> On Wed, 5 Feb 2020 07:59:48 +0000
> Minas Harutyunyan <Minas.Harutyunyan@synopsys.com> wrote:
> 
>> On 2/4/2020 7:29 PM, John Keeping wrote:
>>> dwc2 always reports as self-powered in response to a device status
>>> request.  Implement the set_selfpowered() operations so that the gadget
>>> can report as bus-powered when appropriate.
>>>
>>> This is modelled on the dwc3 implementation.
>>>
>>> Signed-off-by: John Keeping <john@metanate.com>
>>

Acked-by: Minas Harutyunyan <hminas@synopsys.com>

>> Good catch. Just one concern. Your patch partially fix my patch this is
>> why I think you need to add Fixes tag otherwise it can create merge
>> conflict if your patch will be merged to next earlier than my.
> 
> I don't think this is actually a fix for your patch, it's a separate fix
> which happens to touch the same code.
> 
> Since dwc2 has never supported the set_selfpowered() operation, I'm not
> really sure if this counts as a bugfix or a feature.
> 
> I'm happy to re-send with a fixes tag if you think it's necessary, but I
> don't think it's accurate in this case - your patch did not introduce a
> bug here :-)
> 
> 
> Regards,
> John
> 
>>> ---
>>>    drivers/usb/dwc2/gadget.c | 24 +++++++++++++++++++++++-
>>>    1 file changed, 23 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/usb/dwc2/gadget.c b/drivers/usb/dwc2/gadget.c
>>> index 2717f4401b97..76c0a5242175 100644
>>> --- a/drivers/usb/dwc2/gadget.c
>>> +++ b/drivers/usb/dwc2/gadget.c
>>> @@ -1646,7 +1646,8 @@ static int dwc2_hsotg_process_req_status(struct dwc2_hsotg *hsotg,
>>>    
>>>    	switch (ctrl->bRequestType & USB_RECIP_MASK) {
>>>    	case USB_RECIP_DEVICE:
>>> -		status = 1 << USB_DEVICE_SELF_POWERED;
>>> +		status = hsotg->gadget.is_selfpowered <<
>>> +			 USB_DEVICE_SELF_POWERED;
>>>    		status |= hsotg->remote_wakeup_allowed <<
>>>    			  USB_DEVICE_REMOTE_WAKEUP;
>>>    		reply = cpu_to_le16(status);
>>> @@ -4530,6 +4531,26 @@ static int dwc2_hsotg_gadget_getframe(struct usb_gadget *gadget)
>>>    	return dwc2_hsotg_read_frameno(to_hsotg(gadget));
>>>    }
>>>    
>>> +/**
>>> + * dwc2_hsotg_set_selfpowered - set if device is self/bus powered
>>> + * @gadget: The usb gadget state
>>> + * @is_selfpowered: Whether the device is self-powered
>>> + *
>>> + * Set if the device is self or bus powered.
>>> + */
>>> +static int dwc2_hsotg_set_selfpowered(struct usb_gadget *gadget,
>>> +				      int is_selfpowered)
>>> +{
>>> +	struct dwc2_hsotg *hsotg = to_hsotg(gadget);
>>> +	unsigned long flags;
>>> +
>>> +	spin_lock_irqsave(&hsotg->lock, flags);
>>> +	gadget->is_selfpowered = !!is_selfpowered;
>>> +	spin_unlock_irqrestore(&hsotg->lock, flags);
>>> +
>>> +	return 0;
>>> +}
>>> +
>>>    /**
>>>     * dwc2_hsotg_pullup - connect/disconnect the USB PHY
>>>     * @gadget: The usb gadget state
>>> @@ -4621,6 +4642,7 @@ static int dwc2_hsotg_vbus_draw(struct usb_gadget *gadget, unsigned int mA)
>>>    
>>>    static const struct usb_gadget_ops dwc2_hsotg_gadget_ops = {
>>>    	.get_frame	= dwc2_hsotg_gadget_getframe,
>>> +	.set_selfpowered	= dwc2_hsotg_set_selfpowered,
>>>    	.udc_start		= dwc2_hsotg_udc_start,
>>>    	.udc_stop		= dwc2_hsotg_udc_stop,
>>>    	.pullup                 = dwc2_hsotg_pullup,
>>>    
> 

  reply	other threads:[~2020-02-05 12:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 15:29 John Keeping
2020-02-05  7:59 ` Minas Harutyunyan
2020-02-05 11:56   ` John Keeping
2020-02-05 12:05     ` Minas Harutyunyan [this message]
2020-02-05 16:36 ` Felipe Balbi
2020-02-05 16:44   ` John Keeping
2020-02-06 18:34     ` Felipe Balbi

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=326e87da-1ac6-33de-1d6f-5ba4852c7e99@synopsys.com \
    --to=minas.harutyunyan@synopsys.com \
    --cc=balbi@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=john@metanate.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.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 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®