[riot-devel] Status of new I2C API
hauke.petersen at fu-berlin.de
Mon Feb 26 10:11:35 CET 2018
fixup to my previous mail: the new proposed API is better presented in
On 02/26/2018 10:07 AM, Hauke Petersen wrote:
> Hi everyone,
> sorry for the late reply. The remodeling of the I2C (master) API
> should indeed be tackled ASAP (as every newly merged implementation
> just adds to the work)... But this is not new and I/we have been
> talking about this for ages now...
> I won't be able to drive this nor to spend time on this. It would be
> great, if anyone else could step up and take the lead. @Dylon: is this
> maybe a job for you?!
> The current state:
> - tracking issue: #6577 
> - new interface proposal: #4926 
> - first thoughts on automated, HIL-style test setup:  (see mostly
> The former idea was, to rename the 'legacy' i2c functions (as proposed
> in #6575 ), merge the new API and then rework all the
> implementations and device drivers in a step-by-step manner. But with
> more thoughts and recent experiences, the way to proceed is probably
> using the feature-branch approach as recently done for for the new
> ietif remodeling.
> So the steps that I see are:
> 1. finish the work on the testing setup , as in-depth testing is
> the key for the remodeling (lessons learned from the SPI remodeling...)
> 2. implement the proposed interface  on some more (restricted)
> target platforms (e.g. nrf52 TWIM) to verify, that the API details do
> actually work on all the CPUs that we support...
> 3. rewrite existing periph drivers, adapt device drivers, and test
> everything thoroughly. This will take significant time and effort!
>  https://github.com/RIOT-OS/RIOT/issues/6577
>  https://github.com/RIOT-OS/RIOT/pull/4926
>  https://github.com/RIOT-OS/RIOT/pull/6575
> On 02/07/2018 01:15 PM, Dylan Laduranty wrote:
>> Dear RIOTers and maintainers,
>> I would like to know the current status of the new I2C master API.
>> It's been a long time since we heard about it. I'm willing to work on
>> it and maybe others are also interested.
>> I'm fully aware that such a big rework will take some times and a lot
>> of efforts but this task has to be done.
>> Would it be useful to create a task force ?
>> What do you think ?
>> Dylan Laduranty
>> devel mailing list
>> devel at riot-os.org
> devel mailing list
> devel at riot-os.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the devel