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 91CD6C25B50 for ; Mon, 23 Jan 2023 10:44:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231722AbjAWKoj (ORCPT ); Mon, 23 Jan 2023 05:44:39 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60096 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231668AbjAWKoi (ORCPT ); Mon, 23 Jan 2023 05:44:38 -0500 Received: from mail.3ffe.de (0001.3ffe.de [IPv6:2a01:4f8:c0c:9d57::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 528C412F17 for ; Mon, 23 Jan 2023 02:44:37 -0800 (PST) Received: from 3ffe.de (0001.3ffe.de [IPv6:2a01:4f8:c0c:9d57::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.3ffe.de (Postfix) with ESMTPSA id 9E6F641; Mon, 23 Jan 2023 11:44:30 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walle.cc; s=mail2022082101; t=1674470670; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=DFxG+3+AuEwK9dzCd11bJRVbzf/YkEZyr1PAY32IkjE=; b=VdV5rc8IrJMFjBa6mto/mGtQoXEGtCUqj8STBbOoayWmrEWIXIX88kYqpel7XFP2/KZel/ 36ppyAyqN1vpFgVr6YlGgYvLtfh2CpDJrOEkQFva0MEUflK4LsbL014Btz1/LN4I22+jvl l3Bkzz2K0VLMFH+8mBXQsLAW9uYsyOePaVgjB+zHj4Xcle7Dlf9gNTqpHgKeAU9GBHBAhL nKQFX61FWp9SiyEpdF7Ol8W8WqyZOdg9/R+rcpxDeVVqPp2E53pYMvrq74N9ulW1nkVcmi KDdXDCulaWhYCGpaesZFCzQkWH0BBiBPO0NREK33biEnVUjNCwZ6R3PrCIEUwg== MIME-Version: 1.0 Date: Mon, 23 Jan 2023 11:44:30 +0100 From: Michael Walle To: Alexandre Mergnat Cc: broonie@kernel.org, devicetree@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org, linux-spi@vger.kernel.org, matthias.bgg@gmail.com, robh+dt@kernel.org Subject: Re: [PATCH 2/2] spi: spidev: add new mediatek support In-Reply-To: References: <20230118-mt8365-spi-support-v1-2-842a21e50494@baylibre.com> <20230120082054.610626-1-michael@walle.cc> User-Agent: Roundcube Webmail/1.4.13 Message-ID: <2aa2ff64cfd3b5ccd1342873fffa6cb4@walle.cc> X-Sender: michael@walle.cc Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-spi@vger.kernel.org Hi, Am 2023-01-23 10:37, schrieb Alexandre Mergnat: > Le ven. 20 janv. 2023 à 09:20, Michael Walle a écrit > : >> >> From: Alexandre Mergnat >> >> > Add the "mediatek,genio" compatible string to support Mediatek >> > SPI controller on the genio boards. >> >> What is the use case of having the spidev? What if I want to >> connect a device with a linux driver to it? It seems like you >> just want to expose the SPI bus on the pin header. There was a >> similar discussion for a mikrobus connector [1]. >> > Yes I want to expose the SPI on the pin header for two reasons: Then "mediatek,genio" doesn't really describe the hardware, does it? If you read that linked thread, NXP was also trying exposing the SPI bus on a pin header. IMHO this is just misusing the userspace spi-dev. That being said, exposing something on a pinheader (or on a standardized connector) seems like a common thing and we should be working towards a good solution. I still think Robs proposal for the mikrobus connector makes also sense for your case. -michael