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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1C26AC4332F for ; Thu, 3 Nov 2022 07:47:33 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231290AbiKCHrc (ORCPT ); Thu, 3 Nov 2022 03:47:32 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42288 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230368AbiKCHr3 (ORCPT ); Thu, 3 Nov 2022 03:47:29 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3395A2ACB; Thu, 3 Nov 2022 00:47:28 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id 3149E68AA6; Thu, 3 Nov 2022 08:47:24 +0100 (CET) Date: Thu, 3 Nov 2022 08:47:24 +0100 From: Christoph Hellwig To: Luis Chamberlain Cc: Guillermo Rodriguez Garcia , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, Christoph Hellwig , Al Viro , Linus Torvalds , Matthew Wilcox , Kees Cook , Iurii Zaikin Subject: Re: fs: layered device driver to write to evdev Message-ID: <20221103074724.GA2685@lst.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Wed, Nov 02, 2022 at 05:04:11PM -0700, Luis Chamberlain wrote: > On Wed, Nov 02, 2022 at 02:14:24PM +0100, Guillermo Rodriguez Garcia wrote: > > I understand that device drivers should implement ->write_iter if they > > need to be written from kernel space, but evdev does not support this. > > What is the recommended way to have a layered device driver that can > > talk to evdev ? > > Shouldn't just writing write_iter support make this work? Writing to evdev just sound like a lot of troble. evdev is a tiny wrapper to expose the in-kernel input API to userspace. Anything in-kernel should just directly interact with the input subsystem.