From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3A1332D0C7E; Mon, 21 Jul 2025 12:13:18 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1753099999; cv=none; b=i1E1RfhuwWPtNe0yJWe9roIDPwbgvWYmGN7qnr+Wv+eCqnql4+1xPtRrOp+5yfHAnajFcxZ9X5cId5FfMgoRjbkAl65GhO+1iCOGsKOWWdcjaNTswr6zBUNPwkSdQq7LeCpYbMMDW+kKWXxSsz/5YTCUarC/0Q52TxJmg1CSrTo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1753099999; c=relaxed/simple; bh=u8UTmNNVfas1iThMeHBfFi6Lpp2ebrw8WQiuOJvC1Ow=; h=Mime-Version:Content-Type:Date:Message-Id:Subject:Cc:To:From: References:In-Reply-To; b=WfZcEOnXQWiahHBA4CCqTnpZKbwK7tf2k9bbASy32Dn1yvIYAaekAkBM9yfO3GW1Z2xhAkPaTvek+6b8sNCrshFrvMMYHgw8gYyWgYpdrTDkDPsciGhgjadA3IVrEf6YBHR+tWg3FFBZnTFA4uWq644takqbMKcVicGsZn2yeYE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=c3noD053; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="c3noD053" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 37ECCC4CEF4; Mon, 21 Jul 2025 12:13:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1753099998; bh=u8UTmNNVfas1iThMeHBfFi6Lpp2ebrw8WQiuOJvC1Ow=; h=Date:Subject:Cc:To:From:References:In-Reply-To:From; b=c3noD0534WoM16ejSp+tS6w7M8GrQwMxtJesCf2swGjVeniYVy326zSP5SPzC3g0Y lFppHPRt4GW4qmvjQpDIUH+c9cqhyT8WkO/DQNVlw01Cq9sHsMP/tqCkFvpT3Glq2v LfS430ETT4AsQsx/gne7uAqY67PJalzhUzeeUbXPxZ/BXyiicXjEvFULbM5hL6ioqO 6yJf1fiAoPMRFQvswAQJlQVobgeK0hIfVVpMsffvDI0gQ01pxOuPeaDoEUlOMV26Ii 73kgvgDAkAr614feE/zrqPcKp32nQ/LcXhy/XzhmK1jznJziYjy4S586WlOQiXzn9U cbkyjSbkLnT4A== Precedence: bulk X-Mailing-List: rust-for-linux@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Mon, 21 Jul 2025 14:13:14 +0200 Message-Id: Subject: Re: [PATCH 2/3] device: rust: expand documentation for Device Cc: "Greg KH" , , , , , , , , , , , To: "Alice Ryhl" From: "Danilo Krummrich" References: <20250717224806.54763-1-dakr@kernel.org> <20250717224806.54763-3-dakr@kernel.org> <2025072125-twine-curling-db0b@gregkh> In-Reply-To: On Mon Jul 21, 2025 at 2:07 PM CEST, Alice Ryhl wrote: > The connection is that to request an irq you must have a &Device, > so if you can only obtain a &Device to a bus device, then that > means that you can never request an irq for a class device. As mentioned in my other reply, a class device never owns resources of a "r= eal" device such as an IRQ. A USB device, which represents a real device on a bus, is a bus device, in = your example the class device is the input device.