[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <978eb183-e45e-0465-d3f0-3ec363f01211@suse.com>
Date: Wed, 6 Oct 2021 20:36:02 +0200
From: Oliver Neukum <oneukum@...e.com>
To: Alan Stern <stern@...land.harvard.edu>,
Oliver Neukum <oneukum@...e.com>
CC: Dmitry Torokhov <dtor@...gle.com>, Rajat Jain <rajatja@...gle.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Thinh Nguyen <Thinh.Nguyen@...opsys.com>,
Mathias Nyman <mathias.nyman@...ux.intel.com>,
Andrew Lunn <andrew@...n.ch>,
Chris Chiu <chris.chiu@...onical.com>,
linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
levinale@...gle.com, bleung@...gle.com, rajatxjain@...il.com,
jsbarnes@...gle.com, pmalani@...gle.com
Subject: Re: [PATCH 2/2] usb: hub: Mark devices downstream a removable hub, as
removable
On 06.10.21 18:10, Alan Stern wrote:
> On Wed, Oct 06, 2021 at 11:37:58AM +0200, Oliver Neukum wrote:
>>
>> In theory yes. If your HC is removable by that logic every device is.
>> That renders the information content of 'removable' to zero. Everything
>> is removable.
> So we should add a new attribute. Call it "unpluggable", perhaps. It
> will say whether the device's immediate upstream link is
> hot-unpluggable. Then the device is removable if its parent is
> removable or if it is unpluggable.
Hi,
yes that would solve the issue. We are basically trying two press two
attributes
into one and that does not work.
Regards
' Oliver
Powered by blists - more mailing lists