From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2FB15C43331 for ; Sat, 7 Sep 2019 19:10:17 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0F1F721848 for ; Sat, 7 Sep 2019 19:10:17 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2404129AbfIGTKN (ORCPT ); Sat, 7 Sep 2019 15:10:13 -0400 Received: from netrider.rowland.org ([192.131.102.5]:48011 "HELO netrider.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1732774AbfIGTKN (ORCPT ); Sat, 7 Sep 2019 15:10:13 -0400 Received: (qmail 1746 invoked by uid 500); 7 Sep 2019 15:10:11 -0400 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 7 Sep 2019 15:10:11 -0400 Date: Sat, 7 Sep 2019 15:10:11 -0400 (EDT) From: Alan Stern X-X-Sender: stern@netrider.rowland.org To: Julius Werner cc: Greg KH , Oliver Neukum , USB Storage list , Dan Williams , Kernel development list , USB list Subject: Re: [PATCH] usb: storage: Add ums-cros-aoa driver In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-usb-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-usb@vger.kernel.org On Fri, 6 Sep 2019, Julius Werner wrote: > FWIW, I found a suitable workaround now to get my use case working > with existing kernels: I can do the mode switch from userspace, then > after the device reenumerates I can manually disable any interfaces I > don't like by writing 0 to their 'authorized' node, and then I write > the VID/PID to usb-storage/new_id. Okay, very good. > I still think it would be nice in general to be able to force a driver > to bind a specific device (rather than a VID/PID match), but it's not > a pressing need for me anymore. You _can_ do this currently, by writing the name of the interface to /sys/bus/usb/drivers/usb-storage/bind. But as you know, this doesn't work unless the VID & PID already match one of the driver's entries. Alan Stern