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 X-Spam-Level: X-Spam-Status: No, score=-10.7 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 46052C1B0E3 for ; Fri, 11 Dec 2020 08:14:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 19F0623EB2 for ; Fri, 11 Dec 2020 08:14:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2395269AbgLKINu (ORCPT ); Fri, 11 Dec 2020 03:13:50 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43144 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389126AbgLKINl (ORCPT ); Fri, 11 Dec 2020 03:13:41 -0500 Received: from mail-lj1-x244.google.com (mail-lj1-x244.google.com [IPv6:2a00:1450:4864:20::244]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B504FC0613CF for ; Fri, 11 Dec 2020 00:13:00 -0800 (PST) Received: by mail-lj1-x244.google.com with SMTP id f24so9850885ljk.13 for ; Fri, 11 Dec 2020 00:13:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7VoXnCBthI2L/2T3Qana/I/DjOclhIB0/A35c/8G8Po=; b=mUq4n+bJwCZqwf4PRpv9TSTHLn5Xh6AZxE3lMXQ4ciL18s5orA99dqvWnn7wTo2aPM ilUo+uRzl7qZO2wwCgl/41qrAZm9TuIx5hqfcp+b4MaWADO9pSYo8JNuQ2GPoMjL4RRM mV9oY+FKvwCDWjRuusoE8PlyrGiUeqePIM0+DR3LWpMAsEND/nYsuYvc/hduFjLWY1n/ HTD9aZNRUvof5nPHL5CN5tWG+vvdtZ+Np1aUb9R/6sZG6XBHtheDpYQ5BwuZjh08OtZu ksEh29nDYnWFQj5F2sXzMySjhLZUm5EqIvPEAu6I2ddc+aBpzicZThurRD023Lq3tArf o79A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7VoXnCBthI2L/2T3Qana/I/DjOclhIB0/A35c/8G8Po=; b=cufE8qTtfI3ypq74OtXpjci6Cs8uV2XjGL+zxNTrIkSoyrHV6qEzVFXJEkSJ/Fa9nl tUBYf6kwMrLn0J9bLBdihtLyAPBGPKD/Bz7SUZrXcY8mqQf7A5/HNOAxaRnz1+18C5QW FpOB49T9+8IX3NuMuSrJv39dhk/y6rb9uX7qAjkkL9wRqvAea2LR/I2pULat3RaDKGkK uQXwj2n0GItFaf9y1/9FsnxBZICx3cyKvHVXdobJ9RK+bFfZB1MPrwsKTfO3mFR9TIv1 vZDbn0HahB6U4rLAubdilTenXd50ExMc2vGe2AKu6iEK31z61A5m726U/ZPCaWS+qfmP ys3w== X-Gm-Message-State: AOAM530cbfEuMmg4X8ZAK833bQknk8NvhwD5n3+W4nrjC+F3YZvIDFIA Yyx+G3onnjTE9XeY12g/kz44D2uKx8OfjVDAD8SdeQ== X-Google-Smtp-Source: ABdhPJxWdWW3zxwdcNB575NyJ4L2g2+cRdR3mY7ME+FqxN3f0TeXt3uzd+Mb9qPY6xHM3BwWTSwfFHObZ+sgW3lHWNE= X-Received: by 2002:a05:651c:205b:: with SMTP id t27mr1220648ljo.368.1607674379166; Fri, 11 Dec 2020 00:12:59 -0800 (PST) MIME-Version: 1.0 References: <3bed61807fff6268789e7d411412fbc5cd6ffe2a.1607507863.git.hns@goldelico.com> In-Reply-To: <3bed61807fff6268789e7d411412fbc5cd6ffe2a.1607507863.git.hns@goldelico.com> From: Linus Walleij Date: Fri, 11 Dec 2020 09:12:48 +0100 Message-ID: Subject: Re: [PATCH] spi: dt-bindings: clarify CS behavior for spi-cs-high and gpio descriptors To: "H. Nikolaus Schaller" Cc: Mark Brown , Rob Herring , linux-spi , "open list:GPIO SUBSYSTEM" , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , "linux-kernel@vger.kernel.org" , Discussions about the Letux Kernel , kernel@pyra-handheld.com, Maxime Ripard , Sven Van Asbroeck , Lukas Wunner , Laurent Pinchart , Andreas Kemnade Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Wed, Dec 9, 2020 at 11:01 AM H. Nikolaus Schaller wrote: > Behavior of CS signal in combination of spi-cs-high and gpio descriptors > is not clearly defined and documented. So clarify the documentation > > Cc: linus.walleij@linaro.org > Cc: linux-gpio@vger.kernel.org > Signed-off-by: H. Nikolaus Schaller This is good because it is helpful to users. Reviewed-by: Linus Walleij In cases like this I would actually consider to write a bit in the bindings saying "this is inconsistent because we screwed up so be careful", standard bodies usually try to avoid that kind of statements because they have all kind of prestige involved with their work, but we don't so we can just as well admit it. Yours, Linus Walleij