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=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no 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 BFA87C432C0 for ; Tue, 3 Dec 2019 16:39:04 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 916BD206EC for ; Tue, 3 Dec 2019 16:39:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1575391144; bh=HUL2+wzCcz0N4ZxqNAEEY4Hwqo2ACb+lRXYZkwg4Lm8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=XNfBSs4CYyWCZYjdu+NtF/rUAbQi1xMWkFh313PdMtmOGvrbdWtO6krK9kko6b6w1 gcp49x+OZDtGz4fk5xMj7l5GGjPTCZl8qZpjF0jN/ZP4PvuoRA4JPT0XATbwNJTWA1 X1x3LwZ/RezIjtV7iKksbZm5osk1Fwp+1AyJWfG0= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726395AbfLCQjE (ORCPT ); Tue, 3 Dec 2019 11:39:04 -0500 Received: from heliosphere.sirena.org.uk ([172.104.155.198]:51634 "EHLO heliosphere.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726186AbfLCQjE (ORCPT ); Tue, 3 Dec 2019 11:39:04 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sirena.org.uk; s=20170815-heliosphere; h=In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=7Kcuy/fn6cSz/SJB4bZWplLo8InyBESqnNDB0HH+CV8=; b=su4IqbsC0yREzmmrtcBG8C4NJ jwHmKeSMVKlOq7kOKOB6G4d6NJpXJO5ZFZIYz5JpTgyikZR9Y9xQIqAK2Hc8hiI8azARrelzowpyb VYvG+AQ0HD9EuV0UESrOcdBACQFiWJC5Fuyz/H10BlOsHdtazC3MxKaVLcsJv4ju1mAAg=; Received: from fw-tnat-cam1.arm.com ([217.140.106.49] helo=fitzroy.sirena.org.uk) by heliosphere.sirena.org.uk with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1icBCN-0003Hr-DU; Tue, 03 Dec 2019 16:38:51 +0000 Received: by fitzroy.sirena.org.uk (Postfix, from userid 1000) id E42A5D003B4; Tue, 3 Dec 2019 16:38:50 +0000 (GMT) Date: Tue, 3 Dec 2019 16:38:50 +0000 From: Mark Brown To: Jonathan Cameron Cc: "Ardelean, Alexandru" , "rodrigorsdc@gmail.com" , "Popa, Stefan Serban" , "kernel-usp@googlegroups.com" , "devel@driverdev.osuosl.org" , "linux-iio@vger.kernel.org" , "devicetree@vger.kernel.org" , "gregkh@linuxfoundation.org" , "lars@metafoo.de" , "pmeerw@pmeerw.net" , "Hennerich, Michael" , "linux-kernel@vger.kernel.org" , "knaack.h@gmx.de" Subject: Re: [PATCH v4] dt-bindings: iio: accel: add binding documentation for ADIS16240 Message-ID: <20191203163850.GN1998@sirena.org.uk> References: <20191123051927.5016-1-rodrigorsdc@gmail.com> <20191123114119.7b0c3447@archlinux> <20191201114032.1a972dda@archlinux> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Ll0BBk1HBk/f94B0" Content-Disposition: inline In-Reply-To: <20191201114032.1a972dda@archlinux> X-Cookie: Cleanliness is next to impossible. User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-iio-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-iio@vger.kernel.org --Ll0BBk1HBk/f94B0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Dec 01, 2019 at 11:40:32AM +0000, Jonathan Cameron wrote: > +CC Mark as we probably need a more general view point on > the question of whether SPI mode should be enforced by binding > or in the driver. Not sure I see the question here, I think I was missing a bit of the conversation? It's perfectly fine for a driver to specify a mode, if the hardware always uses some unusual mode then there's no sense in forcing every single DT to set the same mode. On the other hand if there's some configuration for the driver that was handling some board specific configuration that there's already some generic SPI support for setting then it seems odd to have a custom driver specific configuration mechanism. --Ll0BBk1HBk/f94B0 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAl3mj5oACgkQJNaLcl1U h9C/sgf/QxvazMVP9zm49jfiS4yHBJmRZeuDac6ZLwJIaSFBBjGWId42DRoQBXU+ 1gZ9GH+tgeT7lGT1w+JXAky7yrNuwA0ERHAOQ1TzT0VF9DKqY+omAYwzBNC1P3A/ pldGP1I/5VsTcsJLVQemowwMzsNo4i3QTDDr07ENM5HAM4IvGVmCwJEfcCy9/q/8 fCpigQGTQRkfA12KD+KnN/87eUKwV93DB3mQ/Hgo9HvE3/BWF7Ra8TvfPCt0EKlV NZQ4ohTyRRkuu8mwQnwJj5XhEAOa2+ueFH2WLhODhGDz58smKbv3cNASdq+t3Jg7 skZw6qsqmI38m+TAhRr33Kps+gZ8+g== =JKhy -----END PGP SIGNATURE----- --Ll0BBk1HBk/f94B0--