Always in favour of removing code duplication! :)

This is a good functionality to add to the kernel I think. Two things though: 1. It should probably end up in the kernel directory: I don't think this is a 'misc' functionality. 2. I am not sure

Should be made configurable.

Hi Anas,

<snip> This sounds like the mBed approach. Whether you put the files in Zephyr main source tree or in some other Git repo you are still maintaining the files the same way, adding the file somewhere

Good enough for me. Will also add burst write. Bogdan

Same here. The sx9500 driver makes a burst write at init to set a bunch of configuration registers, so that's one user. Not sure about any others, though. Vlad

Don't think burst write is that common, but it may be useful if a driver wants to optimize write operations when configuring the chip. The functions I wrote are for 8-bit registers/addresses which

Hi Bogdan, I like the idea. It would help to factorize code in many places indeed! Btw, would it make sense to an i2c_reg_burst_write()? (would there be any use-case for such function

Hello all, This is a proposal to add an API for reading, writing and updating internal registers of I2C devices. This API would offer a simpler way of communicating with I2C devices that have

Hi Maciek,

Hi Tomasz, <tomasz.bursztyka(a)linux.intel.com> wrote: Yep, this actually saves a pointer and in fact is something I thought about but for some reason did not implement, anyway I will change to make

https://jira.zephyrproject.org/browse/ZEP-212 Carles

Hello Joakim, Your feedback is really appreciated.

Thanks for all the feedback -- it definitely looks that it is staying as people very actively rely on it, so I'll close the ticket but first I'll add the feedback to it for future reference in case

Right, but only because the implementation was done in such way. Frankly, if I used ST's libraries, it would have saved me a lot of time during porting. Instead, I followed the example set by

if you think doing this # make ZEPHYR_BASE=/path/to/source/tree BOARD=blah blah hundreds of times per day is more convenient than doing 'source zephyr-env.sh’ once a day per shell then we have a

Certainly, ZEPHYR_BASE is tree-specific (so could be the other in certain cases, but uncommon). I also do set it manually (in fact, as I said somewhere, I feed it to make's command line) This is the

I use it instead of polluting my .bashrc with zephyr stuff. Basically, your two export lines above go in there. I personally like that zephyr-env.sh exists: you just have to source it and your