Received: by 2002:ac0:8845:0:0:0:0:0 with SMTP id g63csp750619img; Thu, 28 Feb 2019 07:18:47 -0800 (PST) X-Google-Smtp-Source: AHgI3IaTV7+kLJQiX5Ozz3IOyhkQzYqgR4CYeHFcmvJYW+pCTd2WvK6TPQdKi3wyAHxWY5QEhORA X-Received: by 2002:a63:20a:: with SMTP id 10mr8943245pgc.346.1551367126940; Thu, 28 Feb 2019 07:18:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551367126; cv=none; d=google.com; s=arc-20160816; b=zp7C1fRgeEasTN365D7rgeajkhs5bQkrP4LbwElWTJT64oabcQxMqX5iDeREDNOBu1 7w8ELxfnle+83HMxe1BHCJtdVtCnuWxSjR4cneQmQMawY3/JU6fbucAi4vLQH8TFl7vM WWUUOtdlkt8emBa2s0L/06o2q/9Ki0uV0oS6dEi88vDEVZSbliacjNTS7X+xfv6JaG/B mY56331z64p6Hyx+Fz2aLqBZXY1M/AMkYLf5ZS9i3luRDJTJ1UGEwkVT1J40n7SFFUEk i52bHHoTWzxxDKFzlcF4qrDClb9hQbpjbZSVQSdybDrcIRg0zH8gfUBSXCSCngoD7wSH 0zKA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=r7as5UqgEs27F6SS8cdriQYBlVMXNeU/jvVZs93ylnU=; b=BbKcPyHMnAdI7fVGho59M/z6pputVhnme0vKxQZBJTBpZIW/LSG9YV8kHMYO101M3d eo+Zry87TPV6FZdjGgjmk4OiXsW5ZdekyVV9lwzT3btmJtBkLABuHPt8ItwUkRTtwHpx kZEfKW32s6T9egNpq/G2O/MW5h+a3VyxVxI+hjJOakou3M2+XrxjRqqunq7pgwXZydJw 16qvaBSAbu+Z/h5Mp2+s62mhxkMwQMhSwflIVHdZi43dbxind+c1SibadRkpNzyE/fBv TpAfiIdD5vfpUNh5TUI32lpubRRfQH1Z1P42Kc8K+CMPsU6EHWSPBb+z88E6zUI4hAR9 eaXw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@essensium-com.20150623.gappssmtp.com header.s=20150623 header.b=mGDSIwhB; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b2si13877661pfi.286.2019.02.28.07.18.31; Thu, 28 Feb 2019 07:18:46 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@essensium-com.20150623.gappssmtp.com header.s=20150623 header.b=mGDSIwhB; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388177AbfB1PQK (ORCPT + 99 others); Thu, 28 Feb 2019 10:16:10 -0500 Received: from mail-yw1-f66.google.com ([209.85.161.66]:40958 "EHLO mail-yw1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387974AbfB1PQI (ORCPT ); Thu, 28 Feb 2019 10:16:08 -0500 Received: by mail-yw1-f66.google.com with SMTP id c67so11300895ywa.7 for ; Thu, 28 Feb 2019 07:16:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=essensium-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=r7as5UqgEs27F6SS8cdriQYBlVMXNeU/jvVZs93ylnU=; b=mGDSIwhBDolaEvThgIaHMKCCgLEVO/6KaM14o/3Ipfxj//g1c30jiV6oEvq1P8ukNp rFozEB5XaOjIwhklWwc+M9fonZs4c6cDREkR6Bx6YIvwNHZY7fGDit1GGxhjF0FR3g9+ 59mw/qjudWAP2rusRzjOl2i0fRvlFUh2ybjcBlDeilZ5XxXLr3NBv7Ovmg2XInjb+T7z 6XhjetxWk0Qy0dLV5fTEFreLTIMAw0pwCmu/A+KG8F72MmEGbPMlktRSr1G3UVf8B08t 40oy7Em2pUiZKJd/7XGDM8xyo5l9h77C9W+zSdr2JFSxq6oIw1+aBjKCh2a8jTintey5 q/xQ== 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=r7as5UqgEs27F6SS8cdriQYBlVMXNeU/jvVZs93ylnU=; b=CZSwh1Eb6s/SPeuTWDX/pP9pLZaSmBigDd0Fxc2K2baLzpuFExu+/NaI07bSfnnbfc ARyRejHIysujINg56irntKwy44rnqq4IESnvKFOPVfRKIM1n9yBoTGybcKAgQGz4I/Nj VIji0nWjVjsa8vOOvK5oplr9RHW7VwuHdNWm6zje1/d8Xe8lDR/ZafrthXpXf/U3ulFI 7mX1TPJIwM+eUek+VtpnawRSwX+qBZ68nAwRRqeqJsUG61xdlpzxn/RJS1Z9dVgbTivD dUlgXeEL3pabTb5t4IlwIYrTL/iMMYd6WG85QZC/MMpx9Ollr4weAu3ChS5OAtwdb5Uw 6wxw== X-Gm-Message-State: APjAAAUmAlPBi5iw7vVkzzIKjGnTDZrt+X5xMCD9/ogX/KMH9DDPrcNr okh22zas/GXVOk1hMAacsEZzbIcwZJ8ozomCv7JUuQ== X-Received: by 2002:a25:c947:: with SMTP id z68mr1277326ybf.522.1551366967287; Thu, 28 Feb 2019 07:16:07 -0800 (PST) MIME-Version: 1.0 References: <20190226150214.19467-1-patrick.havelange@essensium.com> <20190227235947.GA27130@bogus> In-Reply-To: <20190227235947.GA27130@bogus> From: Patrick Havelange Date: Thu, 28 Feb 2019 16:15:55 +0100 Message-ID: Subject: Re: [PATCH v5 1/2] iio:temperature:max31856:Add device tree bind info To: Rob Herring Cc: Jonathan Cameron , Hartmut Knaack , Lars-Peter Clausen , Peter Meerwald-Stadler , Mark Rutland , Paresh Chaudhary , Matt Weber , linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 28, 2019 at 12:59 AM Rob Herring wrote: > > On Tue, Feb 26, 2019 at 04:02:13PM +0100, Patrick Havelange wrote: > > From: Paresh Chaudhary > > > > This patch added device tree binding info for MAX31856 driver. > > > > Signed-off-by: Paresh Chaudhary > > Signed-off-by: Matt Weber > > Signed-off-by: Patrick Havelange > > --- > > Changes > > v1 -> v2 > > [Matt > > - Removed comment block and added possibilities of > > thermocouple type in device tree binding doc. > > > > v2 -> v3 > > - Rebased > > > > v3 -> v4 > > - Removed one-shot property related information. > > - Used standard name 'temp-sensor' > > > > v4 -> v5 > > [Patrick > > - Rename thermocouple type to maxim,thermocouple-type for DT entry > > --- > > .../bindings/iio/temperature/max31856.txt | 29 +++++++++++++++++++ > > 1 file changed, 29 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/iio/temperature/max31856.txt > > > > diff --git a/Documentation/devicetree/bindings/iio/temperature/max31856.txt b/Documentation/devicetree/bindings/iio/temperature/max31856.txt > > new file mode 100644 > > index 000000000000..b4396069b8fa > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/iio/temperature/max31856.txt > > @@ -0,0 +1,29 @@ > > +Maxim MAX31856 thermocouple support > > + > > +https://datasheets.maximintegrated.com/en/ds/MAX31856.pdf > > + > > +Required properties: > > + - compatible: must be "maxim,max31856" > > + - reg: SPI chip select number for the device > > + - spi-max-frequency: As per datasheet max. supported freq is 5000000 > > + - spi-cpha: must be defined for max31856 to enable SPI mode 1 > > + - maxim,thermocouple-type: Type of thermocouple (By default is K-Type) > > + 0x00 : TYPE_B > > + 0x01 : TYPE_E > > + 0x02 : TYPE_J > > + 0x03 : TYPE_K (default) > > + 0x04 : TYPE_N > > + 0x05 : TYPE_R > > + 0x06 : TYPE_S > > + 0x07 : TYPE_T > > These appear to be standard types. Perhaps this should be a common > property instead? A remark on the v4 of the patch recommended to add a vendor prefix. It also mentioned that it could be done as a generic type with a translation layer for each driver. Maybe this generic type could be introduced in a separate patch, or when another driver also uses that kind of thermocouple-type, as there is no other use of it for the moment it seems. > > > + > > + Refer to spi/spi-bus.txt for generic SPI slave bindings. > > + > > + Example: > > + temp-sensor@0 { > > + compatible = "maxim,max31856"; > > + reg = <0>; > > + spi-max-frequency = <5000000>; > > + spi-cpha; > > + maxim,thermocouple-type = <0x03>; > > + }; > > -- > > 2.19.1 > >