diff options
| author | Tony Lindgren <tony@atomide.com> | 2017-02-14 10:26:03 -0800 |
|---|---|---|
| committer | Tony Lindgren <tony@atomide.com> | 2017-02-14 10:26:03 -0800 |
| commit | 179125085bd4ca70e8e028913193a93653bd12f7 (patch) | |
| tree | 6521cdeedb877576f29f2b5ae49a1185353fed1d /net | |
| parent | 1ea6af3216b092ec97129ac81bd95cf254c4b140 (diff) | |
| download | op-kernel-dev-179125085bd4ca70e8e028913193a93653bd12f7.zip op-kernel-dev-179125085bd4ca70e8e028913193a93653bd12f7.tar.gz | |
ARM: OMAP3: Fix smartreflex platform data regression
Commit d9d9cec02835 ("ARM: OMAP2+: Remove legacy data from hwmod for
omap3") dropped platform data that should no longer be used as we're
booting with device tree. It turns out that smartreflex is still
using platform data and produces the following errors during probe:
smartreflex smartreflex.0: invalid resource
smartreflex smartreflex.0: omap_sr_probe: ioremap fail
smartreflex: probe of smartreflex.0 failed with error -22
smartreflex smartreflex.1: invalid resource
smartreflex smartreflex.1: omap_sr_probe: ioremap fail
smartreflex: probe of smartreflex.1 failed with error -22
Let's fix the regression by adding back the smartreflex hwmod data.
The long term is to update the smartreflex driver to use device tree
based probing.
Fixes: d9d9cec02835 ("ARM: OMAP2+: Remove legacy data from hwmod
for omap3")
Reported-by: Adam Ford <aford173@gmail.com>
Tested-by: Adam Ford <aford173@gmail.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions
