From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754690AbbIRWhY (ORCPT ); Fri, 18 Sep 2015 18:37:24 -0400 Received: from gproxy2-pub.mail.unifiedlayer.com ([69.89.18.3]:37393 "HELO gproxy2-pub.mail.unifiedlayer.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1754582AbbIRWhU (ORCPT ); Fri, 18 Sep 2015 18:37:20 -0400 X-Authority-Analysis: v=2.1 cv=EbVbHpWC c=1 sm=1 tr=0 a=J7Q474dc+DFtUK1fo70nSg==:117 a=J7Q474dc+DFtUK1fo70nSg==:17 a=cNaOj0WVAAAA:8 a=f5113yIGAAAA:8 a=dSbym95GAAAA:8 a=YvBuOYWDVJoA:10 a=VqAmlRBGTWEA:10 a=ff-B7xzCdYMA:10 a=BxgfbMJPAAAA:8 a=N6_MU2a_U_TmDZRrYYYA:9 a=ZwwjH5zGhIdR3I2s:21 a=settKSsMI3GAQho8:21 From: Constantine Shulyupin To: linux-kernel@vger.kernel.org (open list), devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS), lm-sensors@lm-sensors.org, Jean Delvare , Guenter Roeck , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala Subject: Please suggest proper format for DT properties. Date: Sat, 19 Sep 2015 01:36:43 +0300 Message-Id: <1442615803-17766-1-git-send-email-const@MakeLinux.com> X-Mailer: git-send-email 1.9.1 X-Identified-User: {1470:box668.bluehost.com:makelinu:makelinux.com} {sentby:smtp auth 84.229.245.43 authed with const@makelinux.com} Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, I am designing DT support for a hwmon chip. It has some sensors, each of them can be: - "disabled" - "thermal diode" - "thermistor" - "voltage" Four possible options for DT properties format. Option 1: Separated property for each sensor. Example nct7802 node: nct7802 { compatible = "nuvoton,nct7802"; reg = <0x2a>; nuvoton,sensor1-type = "thermistor"; nuvoton,sensor2-type = "disabled"; nuvoton,sensor3-type = "voltage"; }; Option 2: Array of strings for all sensors. nct7802 { compatible = "nuvoton,nct7802"; reg = <0x2a>; nuvoton,sensors-types = "thermistor", "disabled", "voltage"; }; Option 3: Sets of 4 cells. Borrowed from marvell,reg-init and broadcom,c45-reg-init. The first cell is the page address, the second a register address within the page, the third cell contains a mask to be ANDed with the existing register value, and the fourth cell is ORed with the result to yield the new register value. If the third cell has a value of zero, no read of the existing value is performed. Example nct7802 node: nct7802 { compatible = "nuvoton,nct7802"; reg = <0x2a>; nct7802,reg-init = <0 0x21 0 0x01 > // START = 1 <0 0x22 0x03 0x02>; // RTD1_MD = 2 }; Please suggest proper format for DT properties. Thanks Constantine PS: Datasheet: https://www.nuvoton.com/hq/products/cloud-computing/hardware-monitors/desktop-server-series/nct7802y/