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 Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 20607C4725D for ; Fri, 19 Jan 2024 11:18:44 +0000 (UTC) Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.97.1) (envelope-from ) id 1rQmsl-000000007Ps-0AZh; Fri, 19 Jan 2024 06:17:55 -0500 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1rQmsZ-000000007Pa-0sMK for kernelnewbies@kernelnewbies.org; Fri, 19 Jan 2024 06:17:53 -0500 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id D0EF43200AE9; Fri, 19 Jan 2024 06:17:24 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Fri, 19 Jan 2024 06:17:25 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h=cc :cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm3; t=1705663044; x=1705749444; bh=i+clb9GPOM cdKo0RfyTv+xmmbczvVA6u+5364Ogw4eU=; b=Z6WoYNgcUJF4rCZJFUdFcOJ4nr hIeuemjiqAlYhwbdp7hrX+V9UGR3En8rcAt4FdkrEe04X3GJFePy3fsQRcTWcCNj MTUlFM9AWA36t1I0y/R42+PtdOUqgwEmBtS3aIV2Hbkp2EQiPpFaTEpWrj1peXfW RQbtNLrVUIero+jhC8+8M0TGzBD5uGZMHTpzLZQWGoWl8FrLVbd4hggKDibRAjIS GWpKuYc92ZPuKRLmV8LSsFE8iFHDR0tsh+7eTvs25ZHEs/qu+OpwPZ74CZWiro3H jan3Kyma9qtlCRjAAjDdygBx3mQPo1/OK0gRSS1+/fNIyZCFxySWW0RyT5tA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; t=1705663044; x=1705749444; bh=i+clb9GPOMcdKo0RfyTv+xmmbczv VA6u+5364Ogw4eU=; b=EGCg0BBfIahKUrdmZFeEFPK/vQodGR8hSV99iOAwCZnB jRkqmPSV5JQajwPEGJGwEmVKOja7m6nnupJmgoWsRa+LKfS505E/37i943VHjL+G ug5FqIatlwHyfYquj2eX5OTrdJmbv/qi0/jUDhDRI54aptW29pO7CYBwqyKCRbNh dhH1qqmOxMsJn8pL8DVIJktOUcGfc0KPOnfnAOLPabrBV12/8OlbinnR/7A6rh+T NfKx0iMbLELU8lxakSmWTJZ1yrALOyIdTKtgliUCoz4JlQnrXZcaVfTEBUq04aq6 16J8b9nXKEE2re9PSRhaqNcAJKd0duh4PibcXbuzjA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdektddgvdehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvvefukfhfgggtuggjsehttd ertddttddvnecuhfhrohhmpefirhgvghcumffjuceoghhrvghgsehkrhhorghhrdgtohhm qeenucggtffrrghtthgvrhhnpeehgedvvedvleejuefgtdduudfhkeeltdeihfevjeekje euhfdtueefhffgheekteenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgr ihhlfhhrohhmpehgrhgvgheskhhrohgrhhdrtghomh X-ME-Proxy: Feedback-ID: i787e41f1:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 19 Jan 2024 06:17:23 -0500 (EST) Date: Fri, 19 Jan 2024 12:17:20 +0100 From: Greg KH To: Kirill Yatsenko Subject: Re: Generic USB LED HID driver Message-ID: <2024011939-geologist-manual-8471@gregkh> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Cc: kernelnewbies@kernelnewbies.org X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org On Fri, Jan 19, 2024 at 11:21:51AM +0100, Kirill Yatsenko wrote: > Hello, > > I'm trying to find the Linux kernel driver in the tree that implements the > HID LED usage table. > The only driver that I've found is the hid-led.c. However, it seems to > support only specific devices. > > The device with which I'm trying to interface is the custom-made board with > atxmega and some LEDS connected to it. > Currently, the communication is done through the vendor-specific HID > protocol. > The custom USB HID kernel module is implemented to communicate with the > device. Why not do this from userspace using libusb or the generic hid userspace api? Why do you need a kernel driver? thanks, greg k-h _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies