From: Dirk Brandewie <dirk.j.brandewie(a)intel.com> Change-Id: I55c2c8132172e841214e53be76545b5c84ba1a3c Signed-off-by: Dirk Brandewie <dirk.j.brandewie(a)intel.com> --- drivers/gpio/gpio_dw.c | 26

From: Dirk Brandewie <dirk.j.brandewie(a)intel.com> Change-Id: Ib989e2a45b7c97728b79b4908d6d0aa8d0957999 Signed-off-by: Dirk Brandewie <dirk.j.brandewie(a)intel.com> --- drivers/gpio/gpio_dw.c | 24

On 02/29/2016 07:22 AM, D'alton, Alexandre wrote: Please post in-line it makes it way easier to keep the context right. > There are 2 aon counters: > > Aon counter => monotinic counter without

Exactly ! --------------------------------------------------------------------- Intel Corporation SAS (French simplified joint stock company) Registered headquarters: "Les Montalets"- 2, rue de

Anas please fix you email client to set in-reply-to: correctly so threading work correctly. Agreed we need to have a common facility. So the logging driver could bind to the appropriate

I agree this sounds awkward. Why aren't the component themselves providing a kconfig option that can be tweaked on a per-component

+1 Said the same thing although not as well in my response you dan and I must have been typing at the same time :-)

General feedback inline below.

I think he got that from scs.h, which uses 'val' and 'bit'. Maybe we should rename 'val' to 'raw' there as well.

Yes, I tried to be consistent with scs.h. I agree with Daniel, 'raw' is more meaningful. -- Maciek Borzecki

+1 This sounds more scalable, basically removes the need for defining a domain and using the levels to do the selection of how verbose messages are for each domain. Anas >

Makes sense. I think we should also add another 'MCU family' level of hierarchy. We would have then: arch/ arm/ soc/ stm32/ stm32f1xx/ <soc specific> stm32f2xx/

Hi Anas, Can you please confirm if you want me to progress this RFC (since it's more convenient to have the VARIANT set, rather than specifying CROSS_COMPILE each time)? If so, what if any changes

The peripherals utilizing UART were required to register their own ISR rountines. This means that all those peripherals drivers need to know which IRQ line is attached to a UART controller, and

Hello, FYI, in thunderdome we have also created a log system solving some of the problems you mention in your RFC. Here are my 2 cents following our experience: - In our implementation we now

Hi Fabien, Very good point. We also experienced it with networking drivers where debugging in the middle or RX/TX just kills timing. This would need to be addressed, but besides this log macros

Hi Hugo, Yes, please do submit. Regards, Anas