Received: by 2002:a25:868d:0:0:0:0:0 with SMTP id z13csp255484ybk; Sat, 9 May 2020 01:54:06 -0700 (PDT) X-Google-Smtp-Source: APiQypJZwbwZt7WjCAcZ8NV2Ihi6xrsTiMMzCQ8N/VCaYOGIWZv2ubVrdvCJUV179fqyRHzzfMF0 X-Received: by 2002:a50:8dc2:: with SMTP id s2mr5717761edh.318.1589014446082; Sat, 09 May 2020 01:54:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1589014446; cv=none; d=google.com; s=arc-20160816; b=zLkM9BUxTJtExDUlMvFl/kstFq1bhafvahsA0p6DJ22HUB+hgsymtQCDb/vZKPWGj0 GGSMYgMG68BjTFITr22zKuFj9cJGaTZz882jpSKXhcZ8iZ3quX7l5/nRfGzTHVMIq6OZ hWmRBUWMbv8HxeUlimCmfTSmWhtRTiA00CTjXx+iN+V95OJEtK6OEnunesg699w7JpWf eArXeJQOvq0Hzt0dredup6oFF+8KzlgrucMYQLS+xaED2J4gCj7NGK6P8szN6NxzYSzA wEQld9dLAso+ateLR9i2Lbk2pYsIg34l+qH8reFtODfkfvWMCg7nxcLLbDR0aelukc4o lqpQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=UX4id79YvnLmpwLxSRzdIBRSmF4fESpagRYbUVxzdds=; b=GmVqoyJpuFkMYdD9i3lNoFxuP2QcijVMigeEULf6gsrPSeglvyARiTKQox/XQhpF6W qAT65AQlTZil63kc2I+6oOY+SRi1zz5SHRVJfvHWgVkPHYD5P1XN00W6yqSDNmMy1OSr A7x+vr4gdZ3LYyloWtGKHn/fiHaLLu1WpTFKyNM8ruDzIFN1EVFLx8VngzIlLNjnv5JO 6aE4FuoraUyW+gsrBn15JIq6R+Mns2SpZGqowN6IeMYJLv+kXyAujD6E1feJzcEEXVOd A+zcl+9Hbe5d2771MBG0/5B4aM6ux/GORpIgv50GfvcBnPpRSeVwSbc5X5B+jQqcx0tk 5n7g== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@metafoo.de header.s=default2002 header.b=k4Hx7HSW; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=metafoo.de Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id bi20si2537031edb.233.2020.05.09.01.53.42; Sat, 09 May 2020 01:54:06 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=fail header.i=@metafoo.de header.s=default2002 header.b=k4Hx7HSW; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=metafoo.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726948AbgEIIwU (ORCPT + 99 others); Sat, 9 May 2020 04:52:20 -0400 Received: from www381.your-server.de ([78.46.137.84]:56354 "EHLO www381.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725930AbgEIIwS (ORCPT ); Sat, 9 May 2020 04:52:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=metafoo.de; s=default2002; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=UX4id79YvnLmpwLxSRzdIBRSmF4fESpagRYbUVxzdds=; b=k4Hx7HSWchDhaD3UM7WhRDZFA4 /E1yaBZNGr67a2zrz/z27HEbSOBpyBa/eSTjHNPV0WUmk7UkuGwfFzqA+c9MJLldEk4k9Quhr/zsY 6C4f+pb/41QuLwSh/RYvOXuNhEMm2Wxp+nh0S5cwtXvsY6JgVeufXOkGttz1qci3B+LVU2K4nC5N4 x2ufxZYtLg1HuH8lUDQCDXKuK6ZBBOn0BiYPWYrTgmEbz3O4XrbR5vW6R8ZZyNBh+GPflWecTaYwh FFeJQb0cui89jf9cFFNch8XXmWnMikD4qJ5EAxtATY2xWSm68S8Ir5Zsr+6mYjCAeNnGZzJ9v8NFO Zvn9WYOA==; Received: from sslproxy01.your-server.de ([78.46.139.224]) by www381.your-server.de with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from ) id 1jXLDT-0000KF-5C; Sat, 09 May 2020 10:52:15 +0200 Received: from [82.135.71.55] (helo=[192.168.178.20]) by sslproxy01.your-server.de with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jXLDS-0000wq-Tj; Sat, 09 May 2020 10:52:15 +0200 Subject: Re: [RFC PATCH 00/14] iio: buffer: add support for multiple buffers To: Alexandru Ardelean , linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org Cc: jic23@kernel.org References: <20200508135348.15229-1-alexandru.ardelean@analog.com> From: Lars-Peter Clausen Message-ID: Date: Sat, 9 May 2020 10:52:14 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <20200508135348.15229-1-alexandru.ardelean@analog.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Authenticated-Sender: lars@metafoo.de X-Virus-Scanned: Clear (ClamAV 0.102.2/25806/Fri May 8 14:16:19 2020) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 5/8/20 3:53 PM, Alexandru Ardelean wrote: > [...] > What I don't like, is that iio:device3 has iio:buffer3:0 (to 3). > This is because the 'buffer->dev.parent = &indio_dev->dev'. > But I do feel this is correct. > So, now I don't know whether to leave it like that or symlink to shorter > versions like 'iio:buffer3:Y' -> 'iio:device3/bufferY'. > The reason for naming the IIO buffer devices to 'iio:bufferX:Y' is > mostly to make the names unique. It would have looked weird to do > '/dev/buffer1' if I would have named the buffer devices 'bufferX'. > > So, now I'm thinking of whether all this is acceptable. > Or what is acceptable? > Should I symlink 'iio:device3/iio:buffer3:0' -> 'iio:device3/buffer0'? > What else should I consider moving forward? > What means forward? > Where did I leave my beer? Looking at how the /dev/ devices are named I think we can provide a name that is different from the dev_name() of the device. Have a look at device_get_devnode() in drivers/base/core.c. We should be able to provide the name for the chardev through the devnode() callback. While we are at this, do we want to move the new devices into an iio subfolder? So iio/buffer0:0 instead of iio:buffer0:0?