From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3sqqz46ZzLzDrL1 for ; Fri, 7 Oct 2016 11:24:48 +1100 (AEDT) Received: from pps.filterd (m0098409.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id u970OMNO067355 for ; Thu, 6 Oct 2016 20:24:46 -0400 Received: from e34.co.us.ibm.com (e34.co.us.ibm.com [32.97.110.152]) by mx0a-001b2d01.pphosted.com with ESMTP id 25wu5jyedg-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Thu, 06 Oct 2016 20:24:46 -0400 Received: from localhost by e34.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 6 Oct 2016 18:24:45 -0600 Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e34.co.us.ibm.com (192.168.1.134) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Thu, 6 Oct 2016 18:24:44 -0600 X-IBM-Helo: d03dlp01.boulder.ibm.com X-IBM-MailFrom: miltonm@us.ibm.com X-IBM-RcptTo: openbmc@lists.ozlabs.org Received: from b03cxnp07028.gho.boulder.ibm.com (b03cxnp07028.gho.boulder.ibm.com [9.17.130.15]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 43B5F1FF0025 for ; Thu, 6 Oct 2016 18:24:24 -0600 (MDT) Received: from b03ledav003.gho.boulder.ibm.com (b03ledav003.gho.boulder.ibm.com [9.17.130.234]) by b03cxnp07028.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id u970Oh3p14287186 for ; Thu, 6 Oct 2016 17:24:43 -0700 Received: from b03ledav003.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 696306A03C for ; Thu, 6 Oct 2016 18:24:43 -0600 (MDT) Received: from d50lp33.co.us.ibm.com (unknown [9.17.249.38]) by b03ledav003.gho.boulder.ibm.com (Postfix) with ESMTPS id 541806A03B for ; Thu, 6 Oct 2016 18:24:43 -0600 (MDT) Received: from localhost by d50lp33.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 6 Oct 2016 18:24:43 -0600 Received: from smtp.notes.na.collabserv.com (192.155.248.81) by d50lp33.co.us.ibm.com (192.168.2.144) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128/128) Thu, 6 Oct 2016 18:24:41 -0600 Received: from localhost by smtp.notes.na.collabserv.com with smtp.notes.na.collabserv.com ESMTP for from ; Fri, 7 Oct 2016 00:24:40 -0000 Received: from us1a3-smtp04.a3.dal06.isc4sb.com (10.106.154.237) by smtp.notes.na.collabserv.com (10.106.227.88) with smtp.notes.na.collabserv.com ESMTP; Fri, 7 Oct 2016 00:24:38 -0000 Received: from us1a3-mail79.a3.dal09.isc4sb.com ([10.142.3.136]) by us1a3-smtp04.a3.dal06.isc4sb.com with ESMTP id 2016100700243800-503608 ; Fri, 7 Oct 2016 00:24:38 +0000 In-Reply-To: Subject: Re: I2C device driver names From: "Milton Miller II" To: Joel Stanley Cc: Matt Spinler , OpenBMC Maillist Date: Fri, 7 Oct 2016 00:24:38 +0000 MIME-Version: 1.0 Sensitivity: Importance: Normal X-Priority: 3 (Normal) References: , X-Mailer: IBM iNotes ($HaikuForm 835.3) | IBM Domino Build V851SAAS_09122016_FP8 October 03, 2016 X-LLNOutbound: False X-Disclaimed: 48227 X-TNEFEvaluated: 1 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8 x-cbid: 16100700-0016-0000-0000-000004DCDD42 X-IBM-ISS-SpamDetectors: Score=0.410169; BY=0.280102; FL=0; FP=0; FZ=0; HX=0; KW=0; PH=0; SC=0.410169; ST=0; TS=0; UL=0; ISC= X-IBM-ISS-DetailInfo: BY=3.00005865; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000186; SDB=6.00765244; UDB=6.00365632; UTC=2016-10-07 00:24:39 x-cbparentid: 16100700-7094-0000-0000-000001D3508B X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused X-TM-AS-GCONF: 00 X-Content-Scanned: Fidelis XPS MAILER X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00005865; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000186; SDB=6.00765244; UDB=6.00365632; IPR=6.00541097; BA=6.00004791; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00012898; XFM=3.00000011; UTC=2016-10-07 00:24:44 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused Message-Id: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-10-06_10:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=1 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1609300000 definitions=main-1610070005 X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Oct 2016 00:24:49 -0000
On 10/06/2016 about 06:43PM somewhere, Joel Stanley <joel@jms.id.au> wrote= :
>
>On Fri, Oct 7, 2016 at 7:14 AM, Matt Spinler
><mspinler@l= inux.vnet.ibm.com> wrote:
>> Hi,
>>
>> As= part of my work to generate a device tree from the machine
>readable=
>> workbook XML, I need to create I2C device entries, which have = the
>compatible
>> properties that need to be filled in.
= >>
>> The following parts are present in the system I'm tryi= ng to build,
>with
>> firmware requirements to access them. = I took a stab at the names.
>Could
>> someone doublecheck t= hem and maybe comment on if a driver is
>missing, or
>> mayb= e if some upcoming work is known that will include it? I
>didn't hav= e
>> much luck finding a lot of these in the
>Documentation/= devicetree/bindings
>> directories.

Unique to the i2c subsy= stem, i2c devices will also match when
the vendor is different but the = chip name portion matches.

>
>If they're not in the kernel = tree it could mean there is not a driver
>for them, or that they are = supported as part of the trivial device
>bindings.
>
>>= ;
>> PMBus Power supplies: ?
>>
>> MAX31785 fa= n controller: max,max31785

Maxim for the vendor? see
Documentat= ion/devicetree/bindings/vendor-prefixes.txt

>
>Doesn't appe= ar to be an upstream driver. Please open a ticket.
>
>>
&= gt;> BMP280: bosch,bmp280
>
>Supported by the iio bmp280 dr= iver.
>
>>
>> TMP4523A temp sensor: ti,tmp423
&= gt;
>Supported by the tmp421 hwmon driver.
>
>>
>= ;> TMP275 temp sensor: ti,tmp275
>
>Documentation/devicetree= /bindings/i2c/trivial-devices.txt
>
>Supported by the lm75 hwmo= n driver.
>
>> pca9552 IO expander: nxp,pca9552
>
= >This appears to be a LED driver?
>
>There's a LED device dr= iver called leds-pca955x.

There is also a gpio driver for pca955[456= 7] in pca953x.c.

>
>>
>> UCD90160 power sequenc= er: ti,ucd90160
>
>A kernel driver called ucd9000 appears to su= pport similar chips.
>Please open a ticket.
>
>>
&g= t;> RX8900CE RTC: epson,rx8900ce
>
>No upstream driver. Ple= ase open a ticket.
>
>>
>> 24c64 EEPROM: atmel,24c= 64
>
>LGTM.
>
>Cheers,
>
>Joel
><= br>>>
>> There are also a handful of regulators, but so far = I haven't heard
>of any
>> requirements to access them.
&= gt;>
>> Thanks.