ARM: omap2: twl-common update
Hi Tony,
I have rebased the branch on 3.9-rc3 tag.
Is it still possible to send this for 3.9?
Regards,
Péter
---
The following changes since commit a937536b868b8369b98967929045f1df54234323:
Linux 3.9-rc3 (2013-03-17 15:59:32 -0700)
are available in the git repository at:
git://gitorious.org/omap-audio/linux-audio.git peter/upstream/for-tony
for you to fetch changes up to 282f21df32df9a01c66d68e7009150ffc69e4e0c:
omap2: twl-common: Add default power configuration (2013-03-18 11:08:12 +0100)
----------------------------------------------------------------
Matthias Brugger (1):
omap2: twl-common: Add default power configuration
arch/arm/mach-omap2/twl-common.c | 38 ++++++++++++++++++++++++++++++++++++++ arch/arm/mach-omap2/twl-common.h | 1 + 2 files changed, 39 insertions(+)
--
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
Quoted 4 lines · Peter Ujfalusi
Hi Tony,
I have rebased the branch on 3.9-rc3 tag.
Is it still possible to send this for 3.9?
Let's see if we can still get this in. It's getting a bit late for v3.9, so I'll apply this into a separate branch from other fixes omap-for-v3.9-rc3/fix-twl-reboot branch just in case it's considered too intrusive for the -rc.
Regards,
Tony
Quoted 15 lines
Regards,
Péter
---
The following changes since commita937536b868b8369b98967929045f1df54234323:Linux 3.9-rc3 (2013-03-17 15:59:32 -0700)
are available in the git repository at:
git://gitorious.org/omap-audio/linux-audio.gitpeter/upstream/for-tonyfor you to fetch changes up to
282f21df32df9a01c66d68e7009150ffc69e4e0c:omap2: twl-common: Add default power configuration (2013-03-18 11:08:12 +0100)
Quoted 7 lines
----------------------------------------------------------------
Matthias Brugger (1):
omap2: twl-common: Add default power configurationarch/arm/mach-omap2/twl-common.c | 38 ++++++++++++++++++++++++++++++++++++++ arch/arm/mach-omap2/twl-common.h | 1 + 2 files changed, 39 insertions(+)
--
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
Quoted 10 lines · Tony Lindgren
Quoted 4 lines · Peter Ujfalusi
Hi Tony,
I have rebased the branch on 3.9-rc3 tag.
Is it still possible to send this for 3.9?Let's see if we can still get this in. It's getting a bit late for v3.9, so I'll apply this into a separate branch from other fixes omap-for-v3.9-rc3/fix-twl-reboot branch just in case it's considered too intrusive for the -rc.
Sorry just noticed that this one adds:
Section mismatch in reference from the variable omap3_power_pdata to the (unknown reference) .init.data:(unknown) The variable omap3_power_pdata references
the (unknown reference) __initdata (unknown)
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console
Is it safe to make it __initdata, or should also other power_pdata have their __initdata flags removed if used by the drivers?
Regards,
Tony
Hi Tony,
Quoted 11 lines · Tony Lindgren
Sorry just noticed that this one adds:
Section mismatch in reference from the variable
omap3_power_pdatato the (unknown reference) .init.data:(unknown) The variableomap3_power_pdatareferences
the (unknown reference)__initdata(unknown)
If the reference is valid then annotate the
variable with __init* or__refdata(seelinux/init.h) or name the variable:*_template,*_timer,*_sht,*_ops,*_probe,*_probe_one,*_consoleIs it safe to make it
__initdata, or should also otherpower_pdatahave their__initdataflags removed if used by the drivers?
We could make the whole stack of struct for the omap3_power_pdata as __initdata since the driver (mfd/twl4030-power) is bool.
I resend the patch and update the branch (and rebase on -rc4) at the same time.
Signature · 5 lines
Péter -- 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
Quoted 12 lines · Peter Ujfalusi
Hi Tony,
Quoted 9 lines · Tony Lindgren
Sorry just noticed that this one adds:
Section mismatch in reference from the variable
omap3_power_pdatato the (unknown reference) .init.data:(unknown) The variableomap3_power_pdatareferences
the (unknown reference)__initdata(unknown)
If the reference is valid then annotate the
variable with __init* or__refdata(seelinux/init.h) or name the variable:*_template,*_timer,*_sht,*_ops,*_probe,*_probe_one,*_console
Quoted 5 lines
Quoted 2 lines
Is it safe to make it
__initdata, or should also otherpower_pdatahave their__initdataflags removed if used by the drivers?We could make the whole stack of struct for the
omap3_power_pdataas__initdatasince the driver (mfd/twl4030-power) is bool.
What if you rebind the driver via sysfs unbind/bind?
Regards,
Tony