This is my fault most likely ... the goal at the driver level was indeed
to init with a known default config, but obviously if people think a
different solution is better there's no reason not to change it!
K.
On 05/05/17 20:39, Vipul Rahane wrote:
I do not know the reason why it is done the way it is but I think you are
right, the reason might have been to initialize with a default config.
On May 4, 2017, at 3:45 PM, Jacob Rosenthal <jakerosent...@gmail.com> wrote:
On Thu, May 4, 2017 at 3:39 PM, Vipul Rahane <vi...@runtime.io> wrote:
I have been thinking about calling the driver initialization function
directly from the bsp
Can you comment on why you're not yet init in the BSP? Im thinking power
issues, which is another conversation I started in another thread. Maybe if
the goal was to init with a config that was as low power as possible maybe
its ok to do so in the BSP?
May I know what do you mean by the following ? Isn’t it currently that way.
Shouldnt these BSPs have dependencies on the drivers either way, if only
when the _PRESENT flag is on
Regards,
Vipul Rahane
