Received: by 2002:a05:6a10:7420:0:0:0:0 with SMTP id hk32csp3581995pxb; Mon, 21 Feb 2022 00:59:57 -0800 (PST) X-Google-Smtp-Source: ABdhPJzez5umIClxLAB20lc+iJV3Z8OKXB6Utq4zjUPg8jV1Mx6hw/+tG125Zyybu4TzXZK5IcH7 X-Received: by 2002:a50:f115:0:b0:410:ef0d:5bdd with SMTP id w21-20020a50f115000000b00410ef0d5bddmr20103511edl.125.1645433996748; Mon, 21 Feb 2022 00:59:56 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645433996; cv=none; d=google.com; s=arc-20160816; b=m9+X+3BHd9RCpxTAE2ssgvUZ2Rf/6QSgpsNe50DOY+Rtzy2ER+dgieqML80fgXSYlG K+Fg/lPMyDm9FF8fv0T/iyXOtfR4vicU0u8rSBjB14zfcVS2YZwQypv3189wr+8VzuY6 4sjolale4kHq2eu3l9vhBkBANAddd5A+puLWrVV/eBoTtwkx1q/E/q2vOnjtAslMWmSu 5fW0DRj26EVxdO95/WdAzoVwj+P0me4pmzi+IYg77xnK+fsKSKGuylA0+Dlzf0Tuc5zM 2/lPxvIvG2NWIv/qDUfC0YosQNXEW3xabfYr4wFmSVuhzx3Q5tEfUGyNCaTZmFIOPSrJ UzbA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:message-id:user-agent:references:in-reply-to :subject:cc:to:from:date:content-transfer-encoding:mime-version :dkim-signature; bh=CYxJg6RXHwuQQPHgm7btkpehETiBp1YmrUpCpg1PZHg=; b=yZWLrlcgqXgmTAggmRzYessPdPRCcQPa0oHM/yZ/uoZGqD0oEhlgjMYfNNDaqmDs3t cnbkRt5FEMdHNjcg/Pdq66YxQNgwSzhe/VqELQJ+eQVgfY0svG9t/4i93mke0S4RnPzr 9UqvJcZ23bEV1pWxmuKLQ58hwh46kRb5pyMO45tM292lypGpmBC0kYNd484nMsKYY3+5 JN/HTqEAGouydSowISn+XdzWZe/7pw/fOtRw/WJha8rhvrMs7qzSJODoqdwt2knJfsxy EXroryNFbZuO6MV4Pa6lRdMRQACFGSgHjibEK5TvqGDD3VbMHIIz6IWp6AXo4jr7BLZL ITXQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@walle.cc header.s=mail2016061301 header.b=SmDq0SK5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id fj2si9480314ejc.998.2022.02.21.00.59.29; Mon, 21 Feb 2022 00:59:56 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@walle.cc header.s=mail2016061301 header.b=SmDq0SK5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346468AbiBUHpB (ORCPT + 99 others); Mon, 21 Feb 2022 02:45:01 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:48964 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1344588AbiBUHpA (ORCPT ); Mon, 21 Feb 2022 02:45:00 -0500 Received: from ssl.serverraum.org (ssl.serverraum.org [176.9.125.105]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 979FB2196; Sun, 20 Feb 2022 23:44:37 -0800 (PST) Received: from ssl.serverraum.org (web.serverraum.org [172.16.0.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ssl.serverraum.org (Postfix) with ESMTPSA id BA42C2223A; Mon, 21 Feb 2022 08:44:35 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walle.cc; s=mail2016061301; t=1645429475; 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=CYxJg6RXHwuQQPHgm7btkpehETiBp1YmrUpCpg1PZHg=; b=SmDq0SK53YoVS9qM7butDx4U4t9guXFj6hquSPFA6/Q7Cd9xxqpQT8lxQcQhwMawAvCoKO yB4iq/kf6bsLDi1j/XEvL1wtdzpM/ajbmDRu37+xBVtrar6+9P93R/JXKT/JCDRAwXSNz6 1oEpPYgWdDnKfVwT4qgTtvZbNDybl7E= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 21 Feb 2022 08:44:35 +0100 From: Michael Walle To: Tudor Ambarus Cc: p.yadav@ti.com, broonie@kernel.org, miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com, linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org, nicolas.ferre@microchip.com, zhengxunli@mxic.com.tw, jaimeliao@mxic.com.tw Subject: Re: [PATCH 0/4] spi-mem: Allow specifying the byte order in DTR mode In-Reply-To: <20220218145900.1440045-1-tudor.ambarus@microchip.com> References: <20220218145900.1440045-1-tudor.ambarus@microchip.com> User-Agent: Roundcube Webmail/1.4.12 Message-ID: <44f655d027b49b87065915f6ba2744d2@walle.cc> X-Sender: michael@walle.cc X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 2022-02-18 15:58, schrieb Tudor Ambarus: > Fortunately there are controllers > that can swap back the bytes at runtime, fixing the endiannesses. > Provide > a way for the upper layers to specify the byte order in DTR mode. Are there any patches for the atmel-quadspi yet? What happens if the controller doesn't support it? Will there be a software fallback? -michael