Received: by 2002:a05:6a10:c604:0:0:0:0 with SMTP id y4csp4278619pxt; Wed, 11 Aug 2021 02:09:32 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzD6tr9anNBMICAjSCWvUzfZtproWJER3VlvbMCsAOcVunwVy+tZZL0xv5Cdm1BpZx4uVYi X-Received: by 2002:a50:a69e:: with SMTP id e30mr9923487edc.332.1628672972329; Wed, 11 Aug 2021 02:09:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1628672972; cv=none; d=google.com; s=arc-20160816; b=kgggt72vZYJQqTuIiFNDrafNLdScvN92rUk0TtvxgK+xU3ps98GkL/2WmIXW92iSbo h23VmUufL/9l+5Gz1cKU1zJOH2+qZyTgN1Z8vx4upd6l9Hx4wKPdvoANowNc0Z18cY+X bH4FC6i1spSvJaAwsRDx23DNIZACq3DmmNbQe9/HuB+t7Ga9mD9nWsMPZtugfrL8jgLs w3zb2yMg1xac6BJ4AAVE3RroFq9KdGIhgL/h96ideEza1ZaZSYcxWzwuN3M2nRgtnMVe zuitHZjDAVRmkkqLBZ5LuuKTUtC5LiYWmKN3oyP6C0gsznjw6Q7uj1QCQCxbZZugMdEN xpuQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=nXImNaPYSJcTWXG5pUrQJAdTevxv3v68JOuuy7T3ttA=; b=yyNg3HD4qYW3TlGz0UGh1IEaG8c5JAkXw0VF3jWfgxgYX8BLhkCyN1tXHp2opYc+gL 6fvK1+PbKJFZmZEShP1Pv66J/t5OTyWGrZaT5nNd1Z8ppggjXFgX9as/sU0VsSLg2SVW 2/zNWK18ctitC2bb4mnRdaq/xNqDdq92fTpZG+TfG5jw6bcfS7948b6nKFflYgcICMUT 3TAiGXC/ID6+8axqBYriSvd2nvBZCpQaS5OpBviJIDMQx1pqw7t2cNzvND6yRLndzlLc CXLLNZwuf7Wpv5psXQJJDy5NioXUtXHhbF8UT7o+cfdSENmJWvNlGGZQUQHMVmGh2Tcf W83Q== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id y16si6755252edq.352.2021.08.11.02.09.09; Wed, 11 Aug 2021 02:09:32 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236320AbhHKJGL (ORCPT + 99 others); Wed, 11 Aug 2021 05:06:11 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37038 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235282AbhHKJGI (ORCPT ); Wed, 11 Aug 2021 05:06:08 -0400 Received: from metis.ext.pengutronix.de (metis.ext.pengutronix.de [IPv6:2001:67c:670:201:290:27ff:fe1d:cc33]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 381F0C0613D3 for ; Wed, 11 Aug 2021 02:05:45 -0700 (PDT) Received: from ptx.hi.pengutronix.de ([2001:67c:670:100:1d::c0]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mDkB9-0002B3-8x; Wed, 11 Aug 2021 11:05:39 +0200 Received: from localhost ([127.0.0.1]) by ptx.hi.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1mDkB8-0001Be-GU; Wed, 11 Aug 2021 11:05:38 +0200 Message-ID: <6d396b18455a228719ac4ffeeddcca20b0aa0184.camel@pengutronix.de> Subject: Re: [PATCH V1 1/4] bindings: nvmem: introduce "reverse-data" property From: Jan =?ISO-8859-1?Q?L=FCbbe?= To: Joakim Zhang , "srinivas.kandagatla@linaro.org" , "robh+dt@kernel.org" , "shawnguo@kernel.org" Cc: "devicetree@vger.kernel.org" , dl-linux-imx , "kernel@pengutronix.de" , "linux-kernel@vger.kernel.org" Date: Wed, 11 Aug 2021 11:05:38 +0200 In-Reply-To: References: <20210810073510.18218-1-qiangqing.zhang@nxp.com> <20210810073510.18218-2-qiangqing.zhang@nxp.com> <17daf0f387dff8145559df6a983b0a222c100514.camel@pengutronix.de> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.40.3 (by Flathub.org) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SA-Exim-Connect-IP: 2001:67c:670:100:1d::c0 X-SA-Exim-Mail-From: jlu@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2021-08-11 at 08:06 +0000, Joakim Zhang wrote: > > > -----Original Message----- > > From: Joakim Zhang > > Sent: 2021年8月11日 16:05 > > To: Jan Lübbe ; srinivas.kandagatla@linaro.org; > > robh+dt@kernel.org; shawnguo@kernel.org > > Cc: devicetree@vger.kernel.org; dl-linux-imx ; > > kernel@pengutronix.de; linux-kernel@vger.kernel.org > > Subject: RE: [PATCH V1 1/4] bindings: nvmem: introduce "reverse-data" > > property > > > > > > > -----Original Message----- > > > From: Jan Lübbe > > > Sent: 2021年8月10日 23:14 > > > To: Joakim Zhang ; > > > srinivas.kandagatla@linaro.org; robh+dt@kernel.org; > > > shawnguo@kernel.org > > > Cc: devicetree@vger.kernel.org; dl-linux-imx ; > > > kernel@pengutronix.de; linux-kernel@vger.kernel.org > > > Subject: Re: [PATCH V1 1/4] bindings: nvmem: introduce "reverse-data" > > > property > > > > > > On Tue, 2021-08-10 at 15:35 +0800, Joakim Zhang wrote: > > > > Introduce "reverse-data" property for nvmem provider to reverse buffer. > > > > > > > > Signed-off-by: Joakim Zhang > > > > --- > > > > Documentation/devicetree/bindings/nvmem/nvmem.yaml | 5 +++++ > > > > 1 file changed, 5 insertions(+) > > > > > > > > diff --git a/Documentation/devicetree/bindings/nvmem/nvmem.yaml > > > > b/Documentation/devicetree/bindings/nvmem/nvmem.yaml > > > > index b8dc3d2b6e92..bc745083fc64 100644 > > > > --- a/Documentation/devicetree/bindings/nvmem/nvmem.yaml > > > > +++ b/Documentation/devicetree/bindings/nvmem/nvmem.yaml > > > > @@ -61,6 +61,11 @@ patternProperties: > > > > description: > > > > Size in bit within the address range specified by reg. > > > > > > > > + reverse-data: > > > > + $ref: /schemas/types.yaml#/definitions/flag > > > > + description: > > > > + Reverse the data that read from the storage device. > > > > > > I'd prefer if it was more explicit that the *bytes* will be reversed. > > > Otherwise a reader might think that this is reversing on the *bit* level. > > > > Make sense, how about 'reverse-byte-order'? > > Sorry, 'reverse-bytes-order'. 'reverse-byte-order' sounds better to me, but I'm not a native English speaker. I'd be fine with either, though. Thanks Jan