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 CE57DC38142 for ; Mon, 23 Jan 2023 09:38:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230172AbjAWJiO (ORCPT ); Mon, 23 Jan 2023 04:38:14 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38838 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231489AbjAWJiN (ORCPT ); Mon, 23 Jan 2023 04:38:13 -0500 Received: from mail-yb1-xb34.google.com (mail-yb1-xb34.google.com [IPv6:2607:f8b0:4864:20::b34]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1B27CCA01 for ; Mon, 23 Jan 2023 01:38:11 -0800 (PST) Received: by mail-yb1-xb34.google.com with SMTP id p188so13997664yba.5 for ; Mon, 23 Jan 2023 01:38:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=5+6RKzh8/Lt7v29Nl9d79EntHpnCiB9/8mqrAnMy3gQ=; b=WeH++WcLNYyMKGf2E2zv8fRfVxHuz1bBP6rzSLVY/1sA+qMk5VJv9VqFdFfHmMkHx2 3TK4on2ONCWbxtooazRn2zlREFQzvisCf1eiU9DfFoS7s1KNn3gLVJSZB+RYQNAJyQ6Z 25IRNyNFjJp2poy8ZKVK8DiXNeUk7ETBAlJrru3Yk77C3FFx3LSSTX4JSh2HOruHWKFE QqJF1GCJsqsO9oK3BF4LekiCTQfo19tlHGwzkA74mlDwM+/x5OS3GK9EV7aTPwNIPS+7 7YBFDa3F0wBfOA84nLvJAh0siJapfjp8BLjl8jcXfMw9zhyH4NBJ+oriZ8GXZrda4ee7 77Gw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=5+6RKzh8/Lt7v29Nl9d79EntHpnCiB9/8mqrAnMy3gQ=; b=OrtXB5FPuJYJwv7SV5ZPbAefjt3HInNQuYRlXWRNYbcQ53lh+MFIQO785wbmvBkII/ MX/v0SPJUaMj6dqC+q6ZXTi1UgAVX2pw4q0m1uK7ITuB/tP8Ft6SXvPv/nw8kKMPj2AU PGkKD6dUharIh1dO3ffscvuuCrOYM8GOuzbYhAIXGkaXPYIkmu7AQDkeFUUFxtcAalme BUn2DIhwh5IaktzXENlO4XrEPkEh1Qv+jzgfwCWHqs4785dXRcP9ylzIHmbsoA2ihMPe dYiPMqWwi3E3ucMD81+sfLlB+EsOqyDeBOJqi9ULExgpn3U6L+RW1OSaUJwffR99zWHH 9QpQ== X-Gm-Message-State: AFqh2krSrKcE++Z4ulYYrLgAuhKWd3RsdE7qxk2GP/bxm2lujjaAwxKH CoUNX6xh0N0a+HLe5zv25ncPI0bJz/66BMRVApJ6IcX3khOpooHb X-Google-Smtp-Source: AMrXdXuyGc4+CKGV7sHJ9YCNKzHlgrK8Jcq0Xwvkw40LgTEpzAUjXXmlBpQFuOBcJuWIcbR2wsacTUkpk9GeEMJ6a50= X-Received: by 2002:a5b:4d2:0:b0:707:473f:b763 with SMTP id u18-20020a5b04d2000000b00707473fb763mr2791131ybp.158.1674466690342; Mon, 23 Jan 2023 01:38:10 -0800 (PST) MIME-Version: 1.0 References: <20230118-mt8365-spi-support-v1-2-842a21e50494@baylibre.com> <20230120082054.610626-1-michael@walle.cc> In-Reply-To: <20230120082054.610626-1-michael@walle.cc> From: Alexandre Mergnat Date: Mon, 23 Jan 2023 10:37:58 +0100 Message-ID: Subject: Re: [PATCH 2/2] spi: spidev: add new mediatek support To: Michael Walle 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 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org Le ven. 20 janv. 2023 =C3=A0 09:20, Michael Walle a =C3= =A9crit : > > 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]. > Hi Michael, Yes I want to expose the SPI on the pin header for two reasons: - It's an Evaluation Kit board, I believe exposing SPI helps new customers to try/understand it. - This board will join the KernelCI soon, this setup will help to do SPI non regression tests for a fixed default configuration. AFAII from [1] , you can easily modify the current spidev@0 (If you don't want to keep userspace interface) or simply add (in the DTS or overlay) another node foo@1 with a different compatible (and so on) according to the chip you plug on the header pin. Regards, Alex [1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tre= e/Documentation/devicetree/bindings/spi/spi-controller.yaml