From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) (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 3sz3Rt4RVXzDt39 for ; Wed, 19 Oct 2016 05:26:17 +1100 (AEDT) Received: from pps.filterd (m0098419.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id u9IIO99u108410 for ; Tue, 18 Oct 2016 14:26:14 -0400 Received: from e38.co.us.ibm.com (e38.co.us.ibm.com [32.97.110.159]) by mx0b-001b2d01.pphosted.com with ESMTP id 265rnd0yyx-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Tue, 18 Oct 2016 14:26:13 -0400 Received: from localhost by e38.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 18 Oct 2016 12:26:13 -0600 Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e38.co.us.ibm.com (192.168.1.138) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Tue, 18 Oct 2016 12:26:09 -0600 Received: from b03cxnp07029.gho.boulder.ibm.com (b03cxnp07029.gho.boulder.ibm.com [9.17.130.16]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id 24C2C19D803F for ; Tue, 18 Oct 2016 12:25:35 -0600 (MDT) Received: from b03ledav003.gho.boulder.ibm.com (b03ledav003.gho.boulder.ibm.com [9.17.130.234]) by b03cxnp07029.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id u9IIQ8cw13107708 for ; Tue, 18 Oct 2016 11:26:09 -0700 Received: from b03ledav003.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 491A36A042 for ; Tue, 18 Oct 2016 12:26:09 -0600 (MDT) Received: from [9.10.223.169] (unknown [9.10.223.169]) by b03ledav003.gho.boulder.ibm.com (Postfix) with ESMTP id 0DCC76A03C for ; Tue, 18 Oct 2016 12:26:09 -0600 (MDT) Subject: Re: I2C device driver names To: OpenBMC Maillist References: <491b910f-a8ab-e70f-4055-928fbd4a7b1f@linux.vnet.ibm.com> From: Matt Spinler Date: Tue, 18 Oct 2016 13:26:43 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <491b910f-a8ab-e70f-4055-928fbd4a7b1f@linux.vnet.ibm.com> Content-Type: multipart/alternative; boundary="------------B164DB46DD5E6959774E6EF3" X-TM-AS-GCONF: 00 X-Content-Scanned: Fidelis XPS MAILER x-cbid: 16101818-0028-0000-0000-000005D67E41 X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00005935; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000187; SDB=6.00769880; UDB=6.00368914; IPR=6.00546315; BA=6.00004815; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00013031; XFM=3.00000011; UTC=2016-10-18 18:26:11 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 16101818-0029-0000-0000-00003022AAE2 Message-Id: <507f5e66-bb82-3959-7110-4b43a3637b16@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-10-18_09:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1609300000 definitions=main-1610180303 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: Tue, 18 Oct 2016 18:26:19 -0000 This is a multi-part message in MIME format. --------------B164DB46DD5E6959774E6EF3 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hello, I am taking a closer look at how to model the pca9552 LED driver in the machine readable workbook and device tree. In the system, it will be used both for LEDs and for general purpose GPIOs. I see there is both a pca955x driver and a pca963x driver. The 955x one has no documentation in the bindings directory. The 963x one has documentation, but doesn't mention anything about how to handle GPIOs, nor am I sure that a 9552 is register compatible with the 16 LED 963x chip anyway. Does anyone here have any experience describing this chip in the device tree? Thanks. On 10/7/2016 3:08 PM, Matt Spinler wrote: > > Thanks. I opened the following issues: > > Power supply: https://github.com/openbmc/openbmc/issues/651 > > MAX31785: https://github.com/openbmc/openbmc/issues/652 > > UCD90160: https://github.com/openbmc/openbmc/issues/653 > > RX8900CE: https://github.com/openbmc/openbmc/issues/654 > > > > On 10/6/2016 7:24 PM, Milton Miller II wrote: >> >> On 10/06/2016 about 06:43PM somewhere, Joel Stanley > > wrote: >> > >> >On Fri, Oct 7, 2016 at 7:14 AM, Matt Spinler >> >> >> 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 trying to build, >> >with >> >> firmware requirements to access them. I took a stab at the names. >> >Could >> >> someone doublecheck them and maybe comment on if a driver is >> >missing, or >> >> maybe if some upcoming work is known that will include it? I >> >didn't have >> >> much luck finding a lot of these in the >> >Documentation/devicetree/bindings >> >> directories. >> >> Unique to the i2c subsystem, 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 fan controller: max,max31785 >> >> Maxim for the vendor? see >> Documentation/devicetree/bindings/vendor-prefixes.txt >> >> > >> >Doesn't appear to be an upstream driver. Please open a ticket. >> > >> >> >> >> BMP280: bosch,bmp280 >> > >> >Supported by the iio bmp280 driver. >> > >> >> >> >> TMP4523A temp sensor: ti,tmp423 >> > >> >Supported by the tmp421 hwmon driver. >> > >> >> >> >> TMP275 temp sensor: ti,tmp275 >> > >> >Documentation/devicetree/bindings/i2c/trivial-devices.txt >> > >> >Supported by the lm75 hwmon driver. >> > >> >> pca9552 IO expander: nxp,pca9552 >> > >> >This appears to be a LED driver? >> > >> >There's a LED device driver called leds-pca955x. >> >> There is also a gpio driver for pca955[4567] in pca953x.c. >> >> > >> >> >> >> UCD90160 power sequencer: ti,ucd90160 >> > >> >A kernel driver called ucd9000 appears to support similar chips. >> >Please open a ticket. >> > >> >> >> >> RX8900CE RTC: epson,rx8900ce >> > >> >No upstream driver. Please open a ticket. >> > >> >> >> >> 24c64 EEPROM: atmel,24c64 >> > >> >LGTM. >> > >> >Cheers, >> > >> >Joel >> > >> >> >> >> There are also a handful of regulators, but so far I haven't heard >> >of any >> >> requirements to access them. >> >> >> >> Thanks. >> >> >> > > > > _______________________________________________ > openbmc mailing list > openbmc@lists.ozlabs.org > https://lists.ozlabs.org/listinfo/openbmc --------------B164DB46DD5E6959774E6EF3 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

Hello,

I am taking a closer look at how to model the pca9552 LED driver in the machine readable workbook and device tree.   In the system, it will be used both for LEDs and for general purpose GPIOs. 

I see there is both a pca955x driver and a pca963x driver.  The 955x one has no documentation in the bindings directory.  The 963x one has documentation, but doesn't mention anything about how to handle GPIOs, nor am I sure that a 9552 is register compatible with the 16 LED 963x chip anyway.

Does anyone here have any experience describing this chip in the device tree?

Thanks.

On 10/7/2016 3:08 PM, Matt Spinler wrote:

Thanks.  I opened the following issues:

Power supply:  https://github.com/openbmc/openbmc/issues/651

MAX31785: https://github.com/openbmc/openbmc/issues/652

UCD90160: https://github.com/openbmc/openbmc/issues/653

RX8900CE: https://github.com/openbmc/openbmc/issues/654



On 10/6/2016 7:24 PM, Milton Miller II wrote:

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@linux.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 trying to build,
>with
>> firmware requirements to access them. I took a stab at the names.
>Could
>> someone doublecheck them and maybe comment on if a driver is
>missing, or
>> maybe if some upcoming work is known that will include it? I
>didn't have
>> much luck finding a lot of these in the
>Documentation/devicetree/bindings
>> directories.

Unique to the i2c subsystem, 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 fan controller: max,max31785

Maxim for the vendor? see
Documentation/devicetree/bindings/vendor-prefixes.txt

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

There is also a gpio driver for pca955[4567] in pca953x.c.

>
>>
>> UCD90160 power sequencer: ti,ucd90160
>
>A kernel driver called ucd9000 appears to support similar chips.
>Please open a ticket.
>
>>
>> RX8900CE RTC: epson,rx8900ce
>
>No upstream driver. Please open a ticket.
>
>>
>> 24c64 EEPROM: atmel,24c64
>
>LGTM.
>
>Cheers,
>
>Joel
>
>>
>> There are also a handful of regulators, but so far I haven't heard
>of any
>> requirements to access them.
>>
>> Thanks.






_______________________________________________
openbmc mailing list
openbmc@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/openbmc

--------------B164DB46DD5E6959774E6EF3--