[PATCH v8 14/16] ARM: dts: Introduce STM32F429 MCU
Maxime Coquelin
mcoquelin.stm32 at gmail.com
Wed May 13 04:45:36 PDT 2015
2015-05-12 23:21 GMT+02:00 Arnd Bergmann <arnd at arndb.de>:
> On Saturday 09 May 2015 09:53:56 Maxime Coquelin wrote:
>> +#include <dt-bindings/mfd/stm32f4-rcc.h>
>> +
>>
>
> Can you find a way to avoid this dependency?
>
> Maybe you can change the bindings so that the numbers you pass as
> arguments to the reset and clock specifiers reflect the numbers that
> the hardware use?
If I understand correctly, you prefer the way I did in v7 [0]?
I don't have a strong opinion on this. Either way is fine to me.
I changed the bindings in the v8 after discussions with Daniel
Thompson, who is implementing the clock driver part of the RCC IP.
He proposed we used common defines, because each peripheral has a
reset line and a clock gate.
Both reset and clock are represented as a single bit, with only the
base offset differing between clock and reset.
You can have a look at chapter 6 of the reference manual [1] if you
find some time.
Having common defines between clocks and reset make sense to me, but I
also understand your point of avoiding dependencies.
Maybe I can revert back to v7 bindings for now, and then we can
reconsider using common defines when Daniel will send the clock
patches.
Note that doing that won't break the DT binary compatibility, as the
raw reset values, or the ones from defines are the same.
Daniel, could you share an example of the bindings you would use for the clocks?
Kind regards,
Maxime
>
> Arnd
[0]: http://lkml.iu.edu/hypermail/linux/kernel/1504.3/04523.html
[1]: http://www.st.com/web/en/resource/technical/document/reference_manual/DM00031020.pdf
More information about the linux-arm-kernel
mailing list