Re: [RFC PATCH 3/6] i2c: add device config helpers

Dobre, Antonel G <antonel.g.dobre@...>


I am in charge of development for the configuration tool mentioned by Vlad.

Our tool aims to help developers both for Zephyr and Linux manage device configurations on build time and ACPI, respectively. We plan on creating a small high-level description language in which developers state what components they need on what board, and together with some information like GPIO pin interrupts, bus addresses and/or ACPI properties we either create configuration code for Zephyr ( in the manner Vlad is describing in his patches ) or ACPI tables for Linux.

This tool will be made open source and available to everyone as soon as we have integrated all the features previously mentioned.

Tony Dobre

-----Original Message-----
From: Dogaru, Vlad
Sent: Tuesday, April 26, 2016 5:52 PM
To: Tomasz Bursztyka <tomasz.bursztyka(a)>; Dobre, Antonel G <antonel.g.dobre(a)>
Cc: devel(a)
Subject: Re: [devel] Re: Re: Re: [RFC PATCH 3/6] i2c: add device config helpers

On Mon, Apr 25, 2016 at 01:59:42PM +0200, Tomasz Bursztyka wrote:
Hi Vlad,

The configuration tool needs to generate config structures (see
devices.c in patch 6/6). These structures are device specific, but
the tool should be as generic as possible. Hard coding the struct
member name to "i2c_client" helps achieve that.

Thus, assuming the macros are correctly used, the config tool needs
only information such as "this device is connected to master I2C0,
address 0x76", to generate "I2C_CLIENT(I2C0, 0x76)". Allowing the
name to change would be an extra variable.
Ok, so it would be really great know a lot more about this tool.
Adding Tony, he can explain more about the tool.


Join to automatically receive all group messages.