All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neal Liu <neal_liu@aspeedtech.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Felipe Balbi <balbi@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>,
	Cai Huoqing <caihuoqing@baidu.com>,
	Tao Ren <rentao.bupt@gmail.com>,
	Julia Lawall <julia.lawall@inria.fr>,
	kernel test robot <lkp@intel.com>,
	Sasha Levin <sashal@kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>
Cc: BMC-SW <BMC-SW@aspeedtech.com>
Subject: RE: [PATCH v3 2/4] usb: aspeed-vhub: fix remote wakeup failure in iKVM use case
Date: Mon, 27 Dec 2021 02:07:02 +0000	[thread overview]
Message-ID: <HK0PR06MB3202796B4DDF471856149B1480429@HK0PR06MB3202.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <HK0PR06MB3202051E7C15E84006DF55C0807B9@HK0PR06MB3202.apcprd06.prod.outlook.com>

> -----Original Message-----
> From: Neal Liu
> Sent: Monday, December 20, 2021 10:23 AM
> To: Benjamin Herrenschmidt <benh@kernel.crashing.org>; Felipe Balbi
> <balbi@kernel.org>; Greg Kroah-Hartman <gregkh@linuxfoundation.org>; Joel
> Stanley <joel@jms.id.au>; Andrew Jeffery <andrew@aj.id.au>; Cai Huoqing
> <caihuoqing@baidu.com>; Tao Ren <rentao.bupt@gmail.com>; Julia Lawall
> <julia.lawall@inria.fr>; kernel test robot <lkp@intel.com>; Sasha Levin
> <sashal@kernel.org>; linux-usb@vger.kernel.org; linux-kernel@vger.kernel.org;
> linux-arm-kernel@lists.infradead.org; linux-aspeed@lists.ozlabs.org
> Cc: BMC-SW <BMC-SW@aspeedtech.com>
> Subject: RE: [PATCH v3 2/4] usb: aspeed-vhub: fix remote wakeup failure in
> iKVM use case
> 
> > -----Original Message-----
> > From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> > Sent: Tuesday, December 14, 2021 10:36 AM
> > To: Neal Liu <neal_liu@aspeedtech.com>; Felipe Balbi
> > <balbi@kernel.org>; Greg Kroah-Hartman <gregkh@linuxfoundation.org>;
> > Joel Stanley <joel@jms.id.au>; Andrew Jeffery <andrew@aj.id.au>; Cai
> > Huoqing <caihuoqing@baidu.com>; Tao Ren <rentao.bupt@gmail.com>; Julia
> > Lawall <julia.lawall@inria.fr>; kernel test robot <lkp@intel.com>;
> > Sasha Levin <sashal@kernel.org>; linux-usb@vger.kernel.org;
> > linux-kernel@vger.kernel.org; linux-arm-kernel@lists.infradead.org;
> > linux-aspeed@lists.ozlabs.org
> > Cc: BMC-SW <BMC-SW@aspeedtech.com>
> > Subject: Re: [PATCH v3 2/4] usb: aspeed-vhub: fix remote wakeup
> > failure in iKVM use case
> >
> > On Thu, 2021-12-09 at 02:37 +0000, Neal Liu wrote:
> > > I'm confused. Signaling Wakeup when wakeup_en is set if it has any
> > > ep activities is not exactly what you said?
> > >
> > > wakeup_en is set only if host allows this device have wakeup
> > > capability and bus being suspended.
> > >
> > > Normal ep activities would not write the MMIO because wakeup_en is
> > > not set.
> >
> > Hrm... I didn't think wakeup_en was limited to the bus being
> > suspended, but maybe I misremember, it's been a while.
> >
> > Cheers,
> > Ben.
> >
> 
> wakeup_en is only set in the case of host set USB_DEVICE_REMOTE_WAKEUP
> feature to vhub devices.
> I think this behavior only occurs during host is going to suspend, and set this
> feature to any device which can wakeup itself before sleep.
> Thanks
> 
> -Neal
> 
Would you like to test it if you have some free time.
Please feel free for any feedback.

-Neal


WARNING: multiple messages have this Message-ID (diff)
From: Neal Liu <neal_liu@aspeedtech.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Felipe Balbi <balbi@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>,
	Cai Huoqing <caihuoqing@baidu.com>,
	Tao Ren <rentao.bupt@gmail.com>,
	Julia Lawall <julia.lawall@inria.fr>,
	kernel test robot <lkp@intel.com>,
	Sasha Levin <sashal@kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	 "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>
Cc: BMC-SW <BMC-SW@aspeedtech.com>
Subject: RE: [PATCH v3 2/4] usb: aspeed-vhub: fix remote wakeup failure in iKVM use case
Date: Mon, 27 Dec 2021 02:07:02 +0000	[thread overview]
Message-ID: <HK0PR06MB3202796B4DDF471856149B1480429@HK0PR06MB3202.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <HK0PR06MB3202051E7C15E84006DF55C0807B9@HK0PR06MB3202.apcprd06.prod.outlook.com>

> -----Original Message-----
> From: Neal Liu
> Sent: Monday, December 20, 2021 10:23 AM
> To: Benjamin Herrenschmidt <benh@kernel.crashing.org>; Felipe Balbi
> <balbi@kernel.org>; Greg Kroah-Hartman <gregkh@linuxfoundation.org>; Joel
> Stanley <joel@jms.id.au>; Andrew Jeffery <andrew@aj.id.au>; Cai Huoqing
> <caihuoqing@baidu.com>; Tao Ren <rentao.bupt@gmail.com>; Julia Lawall
> <julia.lawall@inria.fr>; kernel test robot <lkp@intel.com>; Sasha Levin
> <sashal@kernel.org>; linux-usb@vger.kernel.org; linux-kernel@vger.kernel.org;
> linux-arm-kernel@lists.infradead.org; linux-aspeed@lists.ozlabs.org
> Cc: BMC-SW <BMC-SW@aspeedtech.com>
> Subject: RE: [PATCH v3 2/4] usb: aspeed-vhub: fix remote wakeup failure in
> iKVM use case
> 
> > -----Original Message-----
> > From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> > Sent: Tuesday, December 14, 2021 10:36 AM
> > To: Neal Liu <neal_liu@aspeedtech.com>; Felipe Balbi
> > <balbi@kernel.org>; Greg Kroah-Hartman <gregkh@linuxfoundation.org>;
> > Joel Stanley <joel@jms.id.au>; Andrew Jeffery <andrew@aj.id.au>; Cai
> > Huoqing <caihuoqing@baidu.com>; Tao Ren <rentao.bupt@gmail.com>; Julia
> > Lawall <julia.lawall@inria.fr>; kernel test robot <lkp@intel.com>;
> > Sasha Levin <sashal@kernel.org>; linux-usb@vger.kernel.org;
> > linux-kernel@vger.kernel.org; linux-arm-kernel@lists.infradead.org;
> > linux-aspeed@lists.ozlabs.org
> > Cc: BMC-SW <BMC-SW@aspeedtech.com>
> > Subject: Re: [PATCH v3 2/4] usb: aspeed-vhub: fix remote wakeup
> > failure in iKVM use case
> >
> > On Thu, 2021-12-09 at 02:37 +0000, Neal Liu wrote:
> > > I'm confused. Signaling Wakeup when wakeup_en is set if it has any
> > > ep activities is not exactly what you said?
> > >
> > > wakeup_en is set only if host allows this device have wakeup
> > > capability and bus being suspended.
> > >
> > > Normal ep activities would not write the MMIO because wakeup_en is
> > > not set.
> >
> > Hrm... I didn't think wakeup_en was limited to the bus being
> > suspended, but maybe I misremember, it's been a while.
> >
> > Cheers,
> > Ben.
> >
> 
> wakeup_en is only set in the case of host set USB_DEVICE_REMOTE_WAKEUP
> feature to vhub devices.
> I think this behavior only occurs during host is going to suspend, and set this
> feature to any device which can wakeup itself before sleep.
> Thanks
> 
> -Neal
> 
Would you like to test it if you have some free time.
Please feel free for any feedback.

-Neal

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

  reply	other threads:[~2021-12-27  2:07 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08 10:05 [PATCH v3 0/4] Refactor Aspeed USB vhub driver Neal Liu
2021-12-08 10:05 ` Neal Liu
2021-12-08 10:05 ` [PATCH v3 1/4] usb: aspeed-vhub: add qualifier descriptor Neal Liu
2021-12-08 10:05   ` Neal Liu
2021-12-09  0:04   ` Benjamin Herrenschmidt
2021-12-09  0:04     ` Benjamin Herrenschmidt
2021-12-08 10:05 ` [PATCH v3 2/4] usb: aspeed-vhub: fix remote wakeup failure in iKVM use case Neal Liu
2021-12-08 10:05   ` Neal Liu
2021-12-09  0:05   ` Benjamin Herrenschmidt
2021-12-09  0:05     ` Benjamin Herrenschmidt
2021-12-09  2:37     ` Neal Liu
2021-12-09  2:37       ` Neal Liu
2021-12-14  2:35       ` Benjamin Herrenschmidt
2021-12-14  2:35         ` Benjamin Herrenschmidt
2021-12-20  2:22         ` Neal Liu
2021-12-20  2:22           ` Neal Liu
2021-12-27  2:07           ` Neal Liu [this message]
2021-12-27  2:07             ` Neal Liu
2022-01-10  6:29             ` Neal Liu
2022-01-10  6:29               ` Neal Liu
2021-12-13 14:01   ` Greg Kroah-Hartman
2021-12-13 14:01     ` Greg Kroah-Hartman
2021-12-08 10:05 ` [PATCH v3 3/4] usb: aspeed-vhub: fix ep0 OUT ack received wrong length issue Neal Liu
2021-12-08 10:05   ` Neal Liu
2021-12-08 10:05 ` [PATCH v3 4/4] usb: aspeed-vhub: support test mode feature Neal Liu
2021-12-08 10:05   ` Neal Liu
2021-12-09  0:06   ` Benjamin Herrenschmidt
2021-12-09  0:06     ` Benjamin Herrenschmidt
2021-12-08 12:21 ` [PATCH v3 0/4] Refactor Aspeed USB vhub driver Greg Kroah-Hartman
2021-12-08 12:21   ` Greg Kroah-Hartman
2021-12-09  2:39   ` Neal Liu
2021-12-09  2:39     ` Neal Liu

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=HK0PR06MB3202796B4DDF471856149B1480429@HK0PR06MB3202.apcprd06.prod.outlook.com \
    --to=neal_liu@aspeedtech.com \
    --cc=BMC-SW@aspeedtech.com \
    --cc=andrew@aj.id.au \
    --cc=balbi@kernel.org \
    --cc=benh@kernel.crashing.org \
    --cc=caihuoqing@baidu.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joel@jms.id.au \
    --cc=julia.lawall@inria.fr \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=rentao.bupt@gmail.com \
    --cc=sashal@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.