On 08/06/2010 02:24 AM, Gopinath, Thara wrote:
-----Original Message-----
From: Menon, Nishanth
Sent: Friday, August 06, 2010 3:54 AM
To: linux-omap
Cc: Menon, Nishanth; Kevin Hilman; Gopinath, Thara
Subject: [PM-SR][PATCH 06/12] omap3: sr: device: fail sr_dev_init should return
error
sr_dev_init should return error on error conditions
Cc: Kevin Hilman<[email protected]>
Cc: Thara Gopinath<[email protected]>
Signed-off-by: Nishanth Menon<[email protected]>
---
arch/arm/mach-omap2/sr_device.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-omap2/sr_device.c b/arch/arm/mach-omap2/sr_device.c
index 6f70da6..8fb60d8 100644
--- a/arch/arm/mach-omap2/sr_device.c
+++ b/arch/arm/mach-omap2/sr_device.c
@@ -162,7 +162,7 @@ static int sr_dev_init(struct omap_hwmod *oh, void *user)
__func__, i + 1);
i++;
kfree(sr_data);
- return 0;
+ return -ENODATA;
}
sr_set_nvalues(sr_dev_data, sr_data);
od = omap_device_build(name, i, oh, sr_data, sizeof(*sr_data),
@@ -172,6 +172,7 @@ static int sr_dev_init(struct omap_hwmod *oh, void *user)
pr_warning("%s: Could not build omap_device for %s: %s.\n\n",
__func__, name, oh->name);
kfree(sr_data);
+ return PTR_ERR(od);
}
NAK for this change.
This API is called from omap_hwmod_for_each_by_class for every smartreflex
module.
If This API returns an error omap_hwmod_for_each_by_class will exit without
looping over
rest of the smartreflex modules. This means a error for one smartreflex module
will prevent
rest of the smartreflex modules to be initialized. We do not want this. Hence
this API returns 0
for non-availability of data for a smartreflex module.
why do we want this behavior(aka continue with as many modules as you
can enable)? h/wmod data structure are NOT meant to be corrupted if they
are, what guarentee do we have that the rest of the sr module data
structures have the right hwmods(even if they passed device_build?).. if
they are, what is the point in enabling SR in half the domains - we
should flag this as an error to developer and get him to fix it instead
of encouraging this slipping by half a dozen developers as only sr_l3
failed or something similar..
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
