From: Jean Pihet j-pi...@ti.com
Remove the device dependent code (ex. cpu_is_xxx()) and settings
from the driver code and instead pass them via the platform
data. This allows a clean separation of the driver code and the platform
code, as required by the move of the platform header files to
Hi Kevin,
On Wed, Oct 3, 2012 at 12:21 AM, Kevin Hilman
khil...@deeprootsystems.com wrote:
Hi Jean,
Jean Pihet jean.pi...@newoldbits.com writes:
Remove the device dependent settings (cpu_is_xxx(), IP fck etc.)
from the driver code and pass them instead via the platform
data.
This allows a
From: Jean Pihet j-pi...@ti.com
Remove the device dependent code (ex. cpu_is_xxx()) and settings
from the driver code and instead pass them via the platform
data. This allows a clean separation of the driver code and the platform
code, as required by the move of the platform header files to
jean.pi...@newoldbits.com writes:
From: Jean Pihet j-pi...@ti.com
Remove the device dependent code (ex. cpu_is_xxx()) and settings
from the driver code and instead pass them via the platform
data. This allows a clean separation of the driver code and the platform
code, as required by the
From: Jean Pihet j-pi...@ti.com
Remove the device dependent code (ex. cpu_is_xxx()) and settings
from the driver code and instead pass them via the platform
data. This allows a clean separation of the driver code and the platform
code, as required by the move of the platform header files to
Kevin,
On Wed, Oct 3, 2012 at 4:29 PM, Kevin Hilman
khil...@deeprootsystems.com wrote:
jean.pi...@newoldbits.com writes:
From: Jean Pihet j-pi...@ti.com
Remove the device dependent code (ex. cpu_is_xxx()) and settings
from the driver code and instead pass them via the platform
data. This
Hi Jean,
Jean Pihet jean.pi...@newoldbits.com writes:
Remove the device dependent settings (cpu_is_xxx(), IP fck etc.)
from the driver code and pass them instead via the platform
data.
This allows a clean separation of the driver code and the platform
code, as required by the move of the
Hi Tony,
On Fri, Sep 21, 2012 at 9:07 PM, Tony Lindgren t...@atomide.com wrote:
* Jean Pihet jean.pi...@newoldbits.com [120920 23:31]:
On Fri, Sep 21, 2012 at 12:15 AM, Tony Lindgren t...@atomide.com wrote:
You should be able to make this even simpler and not have to pass
the clock name
Remove the device dependent settings (cpu_is_xxx(), IP fck etc.)
from the driver code and pass them instead via the platform
data.
This allows a clean separation of the driver code and the platform
code, as required by the move of the platform header files to
include/linux/platform_data.
Hi Tony,
On Fri, Sep 21, 2012 at 12:15 AM, Tony Lindgren t...@atomide.com wrote:
Hi,
* Jean Pihet jean.pi...@newoldbits.com [120920 07:48]:
--- a/drivers/power/avs/smartreflex.c
+++ b/drivers/power/avs/smartreflex.c
@@ -131,14 +131,11 @@ static void sr_set_clk_length(struct omap_sr *sr)
* Jean Pihet jean.pi...@newoldbits.com [120920 23:31]:
On Fri, Sep 21, 2012 at 12:15 AM, Tony Lindgren t...@atomide.com wrote:
You should be able to make this even simpler and not have to pass
the clock name around at all. Just do:
syc_ck = clk_get(NULL, fck);
...
The problem is that
Remove the device dependent settings (cpu_is_xxx(), IP fck etc.)
from the driver code and pass them instead via the platform
data.
This allows a clean separation of the driver code and the platform
code.
Signed-off-by: Jean Pihet j-pi...@ti.com
---
arch/arm/mach-omap2/sr_device.c | 14
Hi,
* Jean Pihet jean.pi...@newoldbits.com [120920 07:48]:
--- a/drivers/power/avs/smartreflex.c
+++ b/drivers/power/avs/smartreflex.c
@@ -131,14 +131,11 @@ static void sr_set_clk_length(struct omap_sr *sr)
struct clk *sys_ck;
u32 sys_clk_speed;
- if (cpu_is_omap34xx())
13 matches
Mail list logo