Re: [PATCH 2/4] gpiolib: Add code to support "active low" GPIOs

2017-05-24 Thread Nikita Yushchenko
> IMHO, whether any of likes it or not, OF_GPIO_ACTIVE_LOW is an > existing feature and the only technical question is if it should be > supported by Barebox on per-driver basis or if there should be a > central API for it. > > Sascha, are you still OK with me proceeding with making and using an >

Re: [PATCH 2/4] gpiolib: Add code to support "active low" GPIOs

2017-05-24 Thread Andrey Smirnov
On Wed, May 24, 2017 at 11:16 AM, Trent Piepho wrote: > On Wed, 2017-05-24 at 10:26 +0300, Nikita Yushchenko wrote: >> First point is that words "active high" (or "active low") have very >> clear meaning. And situation when chip's signal is active low, but one >> has to write "active high" in sign

Re: [PATCH 2/4] gpiolib: Add code to support "active low" GPIOs

2017-05-24 Thread Trent Piepho
On Wed, 2017-05-24 at 10:26 +0300, Nikita Yushchenko wrote: > First point is that words "active high" (or "active low") have very > clear meaning. And situation when chip's signal is active low, but one > has to write "active high" in signal definition to make things working, > is not something I w

Re: Stable branches resurrected

2017-05-24 Thread Ian Abbott
On 24/05/17 08:36, Sascha Hauer wrote: Hi All, v2017.05.0 contains some nasty bugs. This led me to the idea to resurrect the stable branches. I created stable/v2017.05 and also released v2017.05.1. Please update to this one if you are using v2017.05.0. Experience shows that very few people semm

Stable branches resurrected

2017-05-24 Thread Sascha Hauer
Hi All, v2017.05.0 contains some nasty bugs. This led me to the idea to resurrect the stable branches. I created stable/v2017.05 and also released v2017.05.1. Please update to this one if you are using v2017.05.0. Experience shows that very few people semm to test the master branch, but that I ge

Re: [PATCH 2/4] gpiolib: Add code to support "active low" GPIOs

2017-05-24 Thread Nikita Yushchenko
> I am not sure I really see a problem with the situation you describe > and why you'd want to change device tree description (perhaps because > I don't know all of the details). I agree, that, depending on you > personal preferences, one might find it annoying that driver uses > physical values, b

Re: [PATCH 3/4] gpiolib: Add support for GPIO "hog" nodes

2017-05-24 Thread Sascha Hauer
On Tue, May 23, 2017 at 04:25:03PM -0700, Andrey Smirnov wrote: > On Mon, May 22, 2017 at 11:52 PM, Nikita Yushchenko > wrote: > >> + ret = of_property_read_u32(chip_np, "#gpio-cells", &gpio_cells); > >> + if (ret) > >> + return ret; > >> + > >> + if (WARN_ON(gpio_cells !=

[PATCH] Makefile: Speed up evaluation of ld options

2017-05-24 Thread Sascha Hauer
Since "333ff7b1e4 Fix linking with new ld, based on u-boot" the build with multiple images became unreasonable slow. This is because the ld-option macro was evaluated once for each image. Fix this by exporting and using LDFLAGS_barebox from the main Makefile. Signed-off-by: Sascha Hauer --- Make