Skip to contentSkip to conversation

OMAP: device: make rt_va easily avaialable to drivers

PATCH New Omar Ramirez Luna 3 participants 4 messages Dec 8, 2010 – Dec 10, 2010

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 OMAP: device: make rt_va easily avaialable to drivers

Patch "OMAP: hwmod/device: add omap_{device, hwmod}_get_mpu_rt_va"[1], introduces omap_device_get_rt_va which is meant to be called by drivers to retrieve the _mpu_rt_va, however this function receives a pointer to an omap_device; since there is no practical way for a driver to get this parameter without fiddling with pdev and container_of macro, and omap_device code already does this, it is better for it to handle this case.

Also moved header declaration to appear in the set of functions to be used by drivers, as per the comment there.

[1] http://marc.info/?l=linux-omap&m=127808467703366&w=2

---
 arch/arm/plat-omap/include/plat/omap_device.h |    3 +--
 arch/arm/plat-omap/omap_device.c              |    8 ++++++--
 2 files changed, 7 insertions(+), 4 deletions(-)
arch/arm/plat-omap/include/plat/omap_device.h +1 -2
index 28e2d1a..1877c1a 100644
@@ -80,6 +80,7 @@ struct omap_device {
 int omap_device_enable(struct platform_device *pdev);
 int omap_device_idle(struct platform_device *pdev);
 int omap_device_shutdown(struct platform_device *pdev);
+void __iomem *omap_device_get_rt_va(struct platform_device *pdev);
 
 /* Core code interface */
 
@@ -101,8 +102,6 @@ struct omap_device *omap_device_build_ss(const char *pdev_name, int pdev_id,
 int omap_device_register(struct omap_device *od);
 int omap_early_device_register(struct omap_device *od);
 
-void __iomem *omap_device_get_rt_va(struct omap_device *od);
-
 /* OMAP PM interface */
 int omap_device_align_pm_lat(struct platform_device *pdev,
 			     u32 new_wakeup_lat_limit);
arch/arm/plat-omap/omap_device.c +6 -2
index abe933c..9d11195 100644
@@ -681,7 +681,7 @@ struct powerdomain *omap_device_get_pwrdm(struct omap_device *od)
 
 /**
  * omap_device_get_mpu_rt_va - return the MPU's virtual addr for the hwmod base
- * @od: struct omap_device *
+ * @pdev: struct platform_device *
  *
  * Return the MPU's virtual address for the base of the hwmod, from
  * the ioremap() that the hwmod code does.  Only valid if there is one
@@ -690,8 +690,12 @@ struct powerdomain *omap_device_get_pwrdm(struct omap_device *od)
  * otherwise, passes along the return value from
  * omap_hwmod_get_mpu_rt_va().
  */
-void __iomem *omap_device_get_rt_va(struct omap_device *od)
+void __iomem *omap_device_get_rt_va(struct platform_device *pdev)
 {
+	struct omap_device *od;
+
+	od = _find_by_pdev(pdev);
+
 	if (od->hwmods_cnt != 1)
 		return NULL;
 
Signature · 1 line
1.7.1
#1 lore raw

PATCH 1/1 OMAP: device: make rt_va easily avaialable to drivers

Quoted 8 lines · Omar Ramirez Luna

Patch "OMAP: hwmod/device: add omap_{device, hwmod}_get_mpu_rt_va"[1], introduces omap_device_get_rt_va which is meant to be called by drivers to retrieve the _mpu_rt_va, however this function receives a pointer to an omap_device; since there is no practical way for a driver to get this parameter without fiddling with pdev and container_of macro, and omap_device code already does this, it is better for it to handle this case.

Quoted 6 lines

Also moved header declaration to appear in the set of functions to be used by drivers, as per the comment there.

[1] http://marc.info/?l=linux-omap&m=127808467703366&w=2

Looks right, since all the other driver-accessible functions take a platform_device pointer, not an omap_device pointer.

However, I thing the subject/shortlog should be clearer. IMO, this patch makes the API more consistent rather than making it easier. Also, subject prefix should be preferrably 'OMAP: omap_device:'.

Kevin

Quoted 52 lines
---
 arch/arm/plat-omap/include/plat/omap_device.h |    3 +--
 arch/arm/plat-omap/omap_device.c              |    8 ++++++--
 2 files changed, 7 insertions(+), 4 deletions(-)
arch/arm/plat-omap/include/plat/omap_device.h +1 -2
index 28e2d1a..1877c1a 100644
@@ -80,6 +80,7 @@ struct omap_device {
 int omap_device_enable(struct platform_device *pdev);
 int omap_device_idle(struct platform_device *pdev);
 int omap_device_shutdown(struct platform_device *pdev);
+void __iomem *omap_device_get_rt_va(struct platform_device *pdev);
 
 /* Core code interface */
 
@@ -101,8 +102,6 @@ struct omap_device *omap_device_build_ss(const char *pdev_name, int pdev_id,
 int omap_device_register(struct omap_device *od);
 int omap_early_device_register(struct omap_device *od);
 
-void __iomem *omap_device_get_rt_va(struct omap_device *od);
-
 /* OMAP PM interface */
 int omap_device_align_pm_lat(struct platform_device *pdev,
 			     u32 new_wakeup_lat_limit);
arch/arm/plat-omap/omap_device.c +6 -2
index abe933c..9d11195 100644
@@ -681,7 +681,7 @@ struct powerdomain *omap_device_get_pwrdm(struct omap_device *od)
 
 /**
  * omap_device_get_mpu_rt_va - return the MPU's virtual addr for the hwmod base
- * @od: struct omap_device *
+ * @pdev: struct platform_device *
  *
  * Return the MPU's virtual address for the base of the hwmod, from
  * the ioremap() that the hwmod code does.  Only valid if there is one
@@ -690,8 +690,12 @@ struct powerdomain *omap_device_get_pwrdm(struct omap_device *od)
  * otherwise, passes along the return value from
  * omap_hwmod_get_mpu_rt_va().
  */
-void __iomem *omap_device_get_rt_va(struct omap_device *od)
+void __iomem *omap_device_get_rt_va(struct platform_device *pdev)
 {
+	struct omap_device *od;
+
+	od = _find_by_pdev(pdev);
+
 	if (od->hwmods_cnt != 1)
 		return NULL;
#2 lore raw

PATCH 1/1 OMAP: device: make rt_va easily avaialable to drivers

Quoted 17 lines · Kevin Hilman
Quoted 8 lines · Omar Ramirez Luna

Patch "OMAP: hwmod/device: add omap_{device, hwmod}_get_mpu_rt_va"[1], introduces omap_device_get_rt_va which is meant to be called by drivers to retrieve the _mpu_rt_va, however this function receives a pointer to an omap_device; since there is no practical way for a driver to get this parameter without fiddling with pdev and container_of macro, and omap_device code already does this, it is better for it to handle this case.

Quoted 6 lines

Also moved header declaration to appear in the set of functions to be used by drivers, as per the comment there.

[1] http://marc.info/?l=linux-omap&m=127808467703366&w=2

Quoted 8 lines

Looks right, since all the other driver-accessible functions take a platform_device pointer, not an omap_device pointer.

However, I thing the subject/shortlog should be clearer. ?IMO, this patch makes the API more consistent rather than making it easier. Also, subject prefix should be preferrably 'OMAP: omap_device:'.

I saw few patches following the convention "OMAP: device" that's why I followed that one, I will change the subject/changelog according to your suggestions.

Thanks,

Omar

#3 lore raw

PATCH 1/1 OMAP: device: make rt_va easily avaialable to drivers

In reply to Omar Ramirez Luna
Quoted 8 lines · Omar Ramirez Luna

Patch "OMAP: hwmod/device: add omap_{device, hwmod}_get_mpu_rt_va"[1], introduces omap_device_get_rt_va which is meant to be called by drivers to retrieve the _mpu_rt_va, however this function receives a pointer to an omap_device; since there is no practical way for a driver to get this parameter without fiddling with pdev and container_of macro, and omap_device code already does this, it is better for it to handle this case.

Quoted 7 lines

Also moved header declaration to appear in the set of functions to be used by drivers, as per the comment there.

[1] http://marc.info/?l=linux-omap&m=127808467703366&w=2

---

Quoted 60 lines

?arch/arm/plat-omap/include/plat/omap_device.h | ? ?3 +-- ?arch/arm/plat-omap/omap_device.c ? ? ? ? ? ? ?| ? ?8 ++++++-- ?2 files changed, 7 insertions(+), 4 deletions(-)

arch/arm/plat-omap/include/plat/omap_device.h +1 -0
index 28e2d1a..1877c1a 100644
@@ -80,6 +80,7 @@ struct omap_device {
 ?int omap_device_enable(struct platform_device *pdev);
 ?int omap_device_idle(struct platform_device *pdev);
 ?int omap_device_shutdown(struct platform_device *pdev);
+void __iomem *omap_device_get_rt_va(struct platform_device *pdev);
 

?/* Core code interface */

arch/arm/plat-omap/include/plat/omap_device.h +0 -2
@@ -101,8 +102,6 @@ struct omap_device *omap_device_build_ss(const char *pdev_name, int pdev_id,
 ?int omap_device_register(struct omap_device *od);
 ?int omap_early_device_register(struct omap_device *od);
 
-void __iomem *omap_device_get_rt_va(struct omap_device *od);
-

?/* OMAP PM interface */
?int omap_device_align_pm_lat(struct platform_device *pdev, ? ? ? ? ? ? ? ? ? ? ? ? ? ? u32 new_wakeup_lat_limit);

arch/arm/plat-omap/omap_device.c +0 -0
index abe933c..9d11195 100644
@@ -681,7 +681,7 @@ struct powerdomain *omap_device_get_pwrdm(struct omap_device *od)
 

?/**
?* omap_device_get_mpu_rt_va - return the MPU's virtual addr for the hwmod base
- * @od: struct omap_device *
+ * @pdev: struct platform_device *
?*
?* Return the MPU's virtual address for the base of the hwmod, from ?* the ioremap() that the hwmod code does. ?Only valid if there is one

arch/arm/plat-omap/omap_device.c +0 -0
@@ -690,8 +690,12 @@ struct powerdomain *omap_device_get_pwrdm(struct omap_device *od)

?* otherwise, passes along the return value from
?* omap_hwmod_get_mpu_rt_va().
?*/

arch/arm/plat-omap/omap_device.c +1 -1
-void __iomem *omap_device_get_rt_va(struct omap_device *od)
+void __iomem *omap_device_get_rt_va(struct platform_device *pdev)

?{
+ ? ? ? struct omap_device *od;

arch/arm/plat-omap/omap_device.c +3 -0
+
+ ? ? ? od = _find_by_pdev(pdev);
+

? ? ? ?if (od->hwmods_cnt != 1)
? ? ? ? ? ? ? ?return NULL;

--
1.7.1

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo at vger.kernel.org
More majordomo info at ?http://vger.kernel.org/majordomo-info.html