[PATCH v2 3/8] ARM: OMAP2+: hwmod: reorganize and document the setup process
Cousson, Benoit
b-cousson at ti.com
Thu Apr 19 04:22:34 EDT 2012
Hi Paul,
On 4/19/2012 10:17 AM, Paul Walmsley wrote:
...
> static int __init omap_hwmod_setup_all(void)
> {
> - int r;
> -
> - if (!mpu_oh) {
> - pr_err("omap_hwmod: %s: MPU initiator hwmod %s not yet registered\n",
> - __func__, MPU_INITIATOR_NAME);
> - return -EINVAL;
> - }
> -
> - r = omap_hwmod_for_each(_populate_mpu_rt_base, NULL);
> -
> - r = omap_hwmod_for_each(_init_clocks, NULL);
> - WARN(IS_ERR_VALUE(r),
> - "omap_hwmod: %s: _init_clocks failed\n", __func__);
> + _ensure_mpu_hwmod_is_setup(NULL);
>
> + omap_hwmod_for_each(_init, NULL);
> omap_hwmod_for_each(_setup, NULL);
Does it make sense to iterate twice? Cannot we just iterate over a _init
+ _setup single call?
Regards,
Benoit
More information about the linux-arm-kernel
mailing list