From owner-freebsd-hackers@freebsd.org  Sat Jul 18 05:01:40 2020
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.nyi.freebsd.org (Postfix) with ESMTP id EB6EF35D353
 for <freebsd-hackers@mailman.nyi.freebsd.org>;
 Sat, 18 Jul 2020 05:01:40 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from mail.turbocat.net (turbocat.net [88.99.82.50])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 4B7wnb5xhSz3ZWT;
 Sat, 18 Jul 2020 05:01:39 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from hps2020.home.selasky.org (unknown [178.17.145.105])
 (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
 (No client certificate requested)
 by mail.turbocat.net (Postfix) with ESMTPSA id A6E65260AA7;
 Sat, 18 Jul 2020 07:01:31 +0200 (CEST)
Subject: Re: Question on structure of USB (specifically USB Serial) stack
To: "Brian Mcgovern (bmcgover)" <bmcgover@cisco.com>,
 Ian Lepore <ian@freebsd.org>,
 "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>
References: <BL0PR11MB34425EBBCF3E674E6A7766E1C57F0@BL0PR11MB3442.namprd11.prod.outlook.com>
 <c20edccb-616b-aedf-6a60-e4857341f2fb@selasky.org>
 <82c1e5cede57ced764bfc3a33c75cc0b36a67660.camel@freebsd.org>
 <BL0PR11MB344286D12DDD48451E274141C57F0@BL0PR11MB3442.namprd11.prod.outlook.com>
From: Hans Petter Selasky <hps@selasky.org>
Message-ID: <4504811e-9eed-d3a1-8d5e-561f7f3ce837@selasky.org>
Date: Sat, 18 Jul 2020 07:01:07 +0200
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101
 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <BL0PR11MB344286D12DDD48451E274141C57F0@BL0PR11MB3442.namprd11.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Rspamd-Queue-Id: 4B7wnb5xhSz3ZWT
X-Spamd-Bar: --
Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none;
 spf=pass (mx1.freebsd.org: domain of hps@selasky.org designates 88.99.82.50 as
 permitted sender) smtp.mailfrom=hps@selasky.org
X-Spamd-Result: default: False [-2.17 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[];
 RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[];
 FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3];
 TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+a:mail.turbocat.net];
 MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[selasky.org];
 ARC_NA(0.00)[]; NEURAL_SPAM_SHORT(0.09)[0.091];
 NEURAL_HAM_LONG(-1.01)[-1.011]; TO_MATCH_ENVRCPT_SOME(0.00)[];
 NEURAL_HAM_MEDIUM(-0.95)[-0.953]; FROM_EQ_ENVFROM(0.00)[];
 R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+];
 ASN(0.00)[asn:24940, ipnet:88.99.0.0/16, country:DE];
 RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.33
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Jul 2020 05:01:41 -0000

On 2020-07-17 01:18, Brian Mcgovern (bmcgover) wrote:
> What I'm hoping to do is pin some USB devices with FTDI interfaces to more consistent name, similar to /dev/usb, based on the tree of struct usb_device entries and their respective addresses.

You might get some ideas how to get struct usb_device inside ucom, by 
looking at this differential revision:

https://reviews.freebsd.org/D21886

Basically you need to make a new API which is passed the uaa->device 
pointer. Then no void * casting will be needed.

--HPS