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 C6729C54EE9 for ; Tue, 13 Sep 2022 18:06:46 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231820AbiIMSGp (ORCPT ); Tue, 13 Sep 2022 14:06:45 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51422 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231838AbiIMSG1 (ORCPT ); Tue, 13 Sep 2022 14:06:27 -0400 Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5253E70E7F; Tue, 13 Sep 2022 10:09:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1663088984; x=1694624984; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=1LkvIeAXL1BK+1/xVWZdecSTR4YLdwGpQFhRg4i+kzA=; b=TpOr/kLi1kOqe3aWncsw1/zOkhO3RE56/ZFHk7cJ6EXiYUQZzMNSaSpA Iiby+kkynhvftYW1crZltBWnlfZOKT1VSltETW1EyOnq8E40iGRJx2rFE aR1qZoc03T52AmCu+jb26VxBje5hb4borJBfO3cX5D9u5/Ac7h/APpQet oUkzQ5/8/jJRdhUWO9Z+/lBKu5Lngo656VJQ4QSDqGydjBP2TrWesO2r/ BYb4/DFqN7LqsMT8JQFvQPCuRfAU8TFh5vbXJlAErMNPyFc+RBSagOoeO emPY4+mBZHkfrCb8vRU7bMjxyFy4q2ulXfzPJAhFkd/B3X/L505Z4hPD6 g==; X-IronPort-AV: E=McAfee;i="6500,9779,10469"; a="277929433" X-IronPort-AV: E=Sophos;i="5.93,313,1654585200"; d="scan'208";a="277929433" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Sep 2022 10:09:42 -0700 X-IronPort-AV: E=Sophos;i="5.93,313,1654585200"; d="scan'208";a="567662661" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga003-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Sep 2022 10:09:39 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1oY9Ne-001qr0-2D; Tue, 13 Sep 2022 20:07:26 +0300 Date: Tue, 13 Sep 2022 20:07:26 +0300 From: Andy Shevchenko To: Kent Gibson Cc: Bartosz Golaszewski , Linus Walleij , Viresh Kumar , linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/2] gpiolib: cdev: export the consumer's PID Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Wed, Sep 14, 2022 at 12:17:39AM +0800, Kent Gibson wrote: > On Tue, Sep 13, 2022 at 05:58:32PM +0200, Bartosz Golaszewski wrote: > > On Tue, Sep 13, 2022 at 4:55 PM Kent Gibson wrote: ... > > We'd need of course first expose that info like: > > > > gpio chip:gpiochip2 lines:0,3,4,7 > > > > Does that make sense? > > Makes sense to me, though I don't claim to know anything about fdinfo > field formatting. > > e.g. I also see fdinfo fields like this: > > eventfd-count: 0 > eventfd-id: 1 > > so > > gpio-chip: gpiochip2 > gpio-lines: 0,3,4,7 > > might be ok too. Always think about two or more GPIO chips in the same process with 1 or more lines requested from each of them. -- With Best Regards, Andy Shevchenko