All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, Kevin Hilman <khilman@ti.com>
Subject: Re: OMAP3530 with no TWL4030 power controller
Date: Mon, 06 Feb 2012 16:54:38 -0700	[thread overview]
Message-ID: <4F30683E.2030509@mlbassoc.com> (raw)
In-Reply-To: <20120206234531.GW1426@atomide.com>

On 2012-02-06 16:45, Tony Lindgren wrote:
> * Gary Thomas<gary@mlbassoc.com>  [120206 09:14]:
>> I have an OMAP3530 (DM3730) board which uses a very simple
>> power controller (TPS65910A1).  This controller does not
>> support many of the power supplies, etc, that are common
>> on the TWL4030 and similar devices.
>>
>> I'm using Linux 3.0.  How can I remove the reliance on the
>> TWL devices?  Simply disabling PM in my configuration isn't
>> enough - that generates a bunch of undefined references.
>> Also, there are many places where power supply stuff is
>> accessed, outside of PM, in particular DSS2 which has a
>> terrible time.  Here's what I get when I disabled PM and
>> REGULATOR support:
>
> Yes it should be possible to support other PMIC other than
> TWL chips too.. What you're seeing is a bug.

This will be a bit more of a change than just another PMIC since
this device isn't much of a power manager (other than at the very
lowest level to handle power up sequencing, etc).  It's good to
hear that it _should_ work and I look forward to ideas on how
to _make_ it work.

For now, I've left PM and REGULATOR enabled so I can at least
build the kernel and with just a few changes, I can get the
kernel to boot to a prompt.  I do need to work out the uglyness
of what I've had to do though :-)

Thanks

>
>> arch/arm/mach-omap2/built-in.o: In function `omap_set_pwrdm_state':
>> /local/linux-3.0/arch/arm/mach-omap2/pm.c:122: undefined reference to `pwrdm_read_next_pwrst'
>> /local/linux-3.0/arch/arm/mach-omap2/pm.c:126: undefined reference to `pwrdm_read_pwrst'
>> /local/linux-3.0/arch/arm/mach-omap2/pm.c:127: undefined reference to `pwrdm_read_pwrst'
>> /local/linux-3.0/arch/arm/mach-omap2/pm.c:133: undefined reference to `pwrdm_wait_transition'
>> /local/linux-3.0/arch/arm/mach-omap2/pm.c:138: undefined reference to `pwrdm_set_next_pwrst'
>> /local/linux-3.0/arch/arm/mach-omap2/pm.c:153: undefined reference to `pwrdm_set_lowpwrstchange'
>> /local/linux-3.0/arch/arm/mach-omap2/pm.c:159: undefined reference to `pwrdm_wait_transition'
>> /local/linux-3.0/arch/arm/mach-omap2/pm.c:160: undefined reference to `pwrdm_state_switch'
>> arch/arm/mach-omap2/built-in.o: In function `omap_hwmod_get_context_loss_count':
>> /local/linux-3.0/arch/arm/mach-omap2/omap_hwmod.c:2638: undefined reference to `pwrdm_get_context_loss_count'
>> arch/arm/mach-omap2/built-in.o: In function `_clkdm_clk_hwmod_disable':
>> /local/linux-3.0/arch/arm/mach-omap2/clockdomain.c:895: undefined reference to `pwrdm_clkdm_state_switch'
>> arch/arm/mach-omap2/built-in.o: In function `clkdm_allow_idle':
>> /local/linux-3.0/arch/arm/mach-omap2/clockdomain.c:786: undefined reference to `pwrdm_clkdm_state_switch'
>> arch/arm/mach-omap2/built-in.o: In function `_clkdm_clk_hwmod_enable':
>> /local/linux-3.0/arch/arm/mach-omap2/clockdomain.c:869: undefined reference to `pwrdm_wait_transition'
>> /local/linux-3.0/arch/arm/mach-omap2/clockdomain.c:870: undefined reference to `pwrdm_clkdm_state_switch'
>> arch/arm/mach-omap2/built-in.o: In function `_clkdm_register':
>> /local/linux-3.0/arch/arm/mach-omap2/clockdomain.c:79: undefined reference to `pwrdm_lookup'
>> /local/linux-3.0/arch/arm/mach-omap2/clockdomain.c:93: undefined reference to `pwrdm_add_clkdm'
>> arch/arm/mach-omap2/built-in.o: In function `omap2_clk_disable_unused':
>> /local/linux-3.0/arch/arm/mach-omap2/clock.c:442: undefined reference to `pwrdm_clkdm_state_switch'
>> arch/arm/mach-omap2/built-in.o: In function `omap2_init_common_infrastructure':
>> /local/linux-3.0/arch/arm/mach-omap2/io.c:355: undefined reference to `omap3xxx_voltagedomains_init'
>> /local/linux-3.0/arch/arm/mach-omap2/io.c:356: undefined reference to `omap3xxx_powerdomains_init'
>>
>>
>> Any ideas?  I'd like to keep my changes to the kernel to
>> a minimum,
>
> Sounds like there should be empty functions for the prdm_* functions
> in this case. Kevin might have some patches to fix this already.
>
> Regards,
>
> Tony

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

  reply	other threads:[~2012-02-06 23:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06 17:44 OMAP3530 with no TWL4030 power controller Gary Thomas
2012-02-06 23:45 ` Tony Lindgren
2012-02-06 23:54   ` Gary Thomas [this message]
2012-02-07 10:53     ` Grazvydas Ignotas
2012-02-07 22:55 ` Kevin Hilman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F30683E.2030509@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.