Received: by 2002:a05:6a10:2785:0:0:0:0 with SMTP id ia5csp213134pxb; Fri, 8 Jan 2021 03:02:38 -0800 (PST) X-Google-Smtp-Source: ABdhPJyb6CSTT614U8l2bKdf/p7Vz2fRw7uIBtKWcDoJL+0HS7MOsVzCNwoqVcN02Z0vGoU+LxLo X-Received: by 2002:aa7:d485:: with SMTP id b5mr4671621edr.214.1610103757698; Fri, 08 Jan 2021 03:02:37 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1610103757; cv=none; d=google.com; s=arc-20160816; b=HM2gTPgRHyJhbQCLZRVDT+cLJapuBiWOXkSXLOS5A5wQLUQ187srT+TiZtf3tJNQni d05+wEGdVUsVcjlb37r8RS1yZQ/SzbnK/R4MgYMjDyrALJU5SpdYMLUXEfgR39VKQhm5 iaLpV1SGkpTpEklW/b9tX4MXiMnlW2Rlpn4+sKeC2Zrc9Dv23EjP94XRnwjtGLBWLdE1 zTyQ9MG4jY4TGqYn0CwbwIGIrxADhb5BBANK+4eHM3yYRuTjypRCXst4nXCC2wZFpa+Y 6l3cMYBAMu/prR8U2nOkV6+13rhfL7RRTtWxIKRjNdfsNZSBaZlT/7HjEWGMFLiGSadv BhkA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:references :subject:cc:to:mime-version:user-agent:from:date:message-id :dkim-signature; bh=b8TjwQx2juGDT0sQZHOQEuzIta4ce4spRHp2FOYWyVg=; b=xC20psPg0Ic1R285V+3dtIodAzje/Re4rVeELBvZbgwA4O1H8Gd6zvpboQ9uzD3kxn lrdok3uyCamGqYLn0Iq23VN/C91IItalU7WiJ9VYtdzgNQsnlwBnd0p1eRgsntDedmz6 sjzHsQuEP3ftPoC4X7IHVu/KLbVpmDSKprhPSwds8O8oe+kuVrbfNn3CBfgK/NVtwvEa pnegbTyAs/bGPagzYkpEADkz+E7ZNl4dFlJj00giiOXp5cY1XDJc8Kasux6gk35VXdza LDDlO87bbgCc386AS18OnKq2eEVTJf7sl7r8MPKZrcPGTvLhejZCe6UXeuXyV9pU3Gf/ 2Uqg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=IMKP7ujg; 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=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id e26si3393551edy.255.2021.01.08.03.02.13; Fri, 08 Jan 2021 03:02:37 -0800 (PST) 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=pass header.i=@gmail.com header.s=20161025 header.b=IMKP7ujg; 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=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727270AbhAHLAl (ORCPT + 99 others); Fri, 8 Jan 2021 06:00:41 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50644 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725901AbhAHLAl (ORCPT ); Fri, 8 Jan 2021 06:00:41 -0500 Received: from mail-ej1-x634.google.com (mail-ej1-x634.google.com [IPv6:2a00:1450:4864:20::634]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ACA1DC0612F4 for ; Fri, 8 Jan 2021 03:00:00 -0800 (PST) Received: by mail-ej1-x634.google.com with SMTP id lt17so14022493ejb.3 for ; Fri, 08 Jan 2021 03:00:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=b8TjwQx2juGDT0sQZHOQEuzIta4ce4spRHp2FOYWyVg=; b=IMKP7ujgtr0mi63cQ+MSA4yJlU3LlrFA86t2c9jnc5pMCJNhPDXuGVB8/dy0/IcZ8Y c8RQnh3zEM+nV32jtxU2lW+NLZ4DFnsJdUo24KOJfrZhpmGNaeycf1sXZSmmLjq0AWYq vjx/De8a0S+3TP7THRN+tYMHfK969ROUTpJ0QUx++xvgPbkascjafz1EGJFG6H8Z4tYw 0g45u6X2t/TGzCXlWVVmT4yjTQNJAhjYl2/Ylz38tTV6d8ab59rLSeIZPe8jDyF/xsYn 1vc5BmPq0ujc0Udwtxni9E8KXrTGF5ik8rI5aKQnYp7ApZXHy8Y90Boa12WkMdUs+DEC a5oA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=b8TjwQx2juGDT0sQZHOQEuzIta4ce4spRHp2FOYWyVg=; b=nDGnZQ5cyssijsrN3V5Ca2OR5nzfAN4CW304Ykt5YjJqoL7rE2hJPWjio/dRFBna3X +obFPl9laKGP/MPIb38z3SF2J+2+PQmM5YLSjzvPXunwuEfi/MfigOgNHrlL6VHzekLn Gue54rXku39PC8g+64TVD50LXK1XUTz1UviK8AyFvQrDbzcNqNBmszpiWyG6vQN0f3GW QW2pf4KwATfMwT/VmuC6SuyifAdlBMrKy1JS17g1ZSHw5HmWVhFfjKgJhah3O0YYm3Ma KiY/roEtOBKjBSx5671Zi8L9mpbWdpt2bhh2m6S/SQy9hPvo2IP5M8TW0tZz8B1anUjh 7RiQ== X-Gm-Message-State: AOAM5308AB8oq5YjUyeNoxeLPXoO9A2X09Ixg12MfBP1dBIBWtmoDma6 O0J1LQ4r7W0kqOWVNI/DjpZ5/p29r0Q= X-Received: by 2002:a17:906:5952:: with SMTP id g18mr2146382ejr.506.1610103599421; Fri, 08 Jan 2021 02:59:59 -0800 (PST) Received: from [89.138.250.57] (89-138-250-57.bb.netvision.net.il. [89.138.250.57]) by smtp.gmail.com with ESMTPSA id qu21sm3389215ejb.95.2021.01.08.02.59.57 (version=TLS1 cipher=AES128-SHA bits=128/128); Fri, 08 Jan 2021 02:59:58 -0800 (PST) Message-ID: <5FF83B02.5000000@gmail.com> Date: Fri, 08 Jan 2021 12:59:14 +0200 From: Eli Billauer User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.12) Gecko/20100907 Fedora/3.0.7-1.fc12 Thunderbird/3.0.7 MIME-Version: 1.0 To: Greg KH CC: arnd@arndb.de, linux-kernel@vger.kernel.org Subject: Re: [PATCH] char: xillybus: Add driver for XillyUSB (Xillybus variant for USB) References: <20201213170503.59017-1-eli.billauer@gmail.com> <5FF5C31C.6050804@gmail.com> <5FF6EDED.40408@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, Greg. On 07/01/21 13:39, Greg KH wrote: > My point is, do NOT have different file names. Userspace should not > care about the backing transport layer of a device. > Regarding sound cards and such -- we agree perfectly. For a driver like XillyUSB, it's not necessarily clear what is correct formally. Either way, for XillyUSB the choice on this matter was practical. First thing, this is what users expect. Xillybus is an FPGA project, and its users are hardware oriented. They've spent time designing the FPGA logic, and the connection with the host has been part of the effort. As the connection via PCIe or USB is part of the design, they definitely see these as different things, and don't expect them to appear to be the same. Also, the application software is virtually always written specially for the project. Even if a specific hardware application is designed with both connection options possible (USB or PCIe), it will be very much desired to distinguish between them. For example, because odds are that the PCIe option will allow a much higher bandwidth capacity. Another thing is that it's quite possible that some users will connect an FPGA board to a host through USB and PCIe simultaneously. For example, when developing an FPGA to work with the USB variant, but at the same time using the PCIe variant for passing debug data. In this case, using the same namespace for both variants will cause confusion. So yes, calling the new XillyUSB device files xillyusb_* instead of xillybus_* may appear awkward. But I'm quite sure that no single user will ever thank me or anyone else for merging them. Maybe the formality is still important enough to do this anyhow...? Thanks and regards, Eli