[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55E57575-B53F-495F-BDBC-E69E69752CDA@enpas.org>
Date: Tue, 20 Aug 2019 11:22:12 +0200
From: Max <max@...as.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
CC: Linux I2C <linux-i2c@...r.kernel.org>, linux-hwmon@...r.kernel.org,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
Jean Delvare <jdelvare@...e.com>,
Guenter Roeck <linux@...ck-us.net>,
Linux/m68k <linux-m68k@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>,
Bartosz Golaszewski <bgolaszewski@...libre.com>
Subject: Re: [PATCH v5 3/3] i2c/busses/i2c-icy: Add LTC2990 present on 2019 board revision
On August 20, 2019 11:18:36 AM GMT+02:00, Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
>Since commit d3e1b617ae20c459 ("i2c: allow specify device properties in
>i2c_board_info"), the properties could be provided by info->properties,
>too.
>However, according to the comments for device_add_properties(), this is
>valid only if there is a real firmware node present.
>
>If that is true, Max' use is correct, while e.g. commit
>6a7836ba7fb4abf6
>("ARM: imx: pca100: use device properties for at24 eeprom") isn't?
Yup, I saw that too. Any hints would be greatly appreciated!
Max
Powered by blists - more mailing lists