linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Peter Korsgaard <jacmet@sunsite.dk>
Cc: Kevin Hilman <khilman@linaro.org>,
	balbi@ti.com, Paul Walmsley <paul@pwsan.com>,
	linux-omap@vger.kernel.org, Tony Lindgren <tony@atomide.com>
Subject: Re: reset handling in am335x hwmod data
Date: Fri, 17 May 2013 13:19:23 -0500	[thread overview]
Message-ID: <20130517181922.GA4439@kahuna> (raw)
In-Reply-To: <87vc6hlbnz.fsf@dell.be.48ers.dk>

On 20:10-20130517, Peter Korsgaard wrote:
> >>>>> "Kevin" == Kevin Hilman <khilman@linaro.org> writes:
> 
>  >> In this case, we cannot reset that bank, otherwise Starter Kit will
>  >> never boot in mainline. Bad PCB design, I know, but it's not something
>  >> we can change now :-)
> 
>  Kevin> FWIW, we've seen this before (GPIO connected to PMIC reset is a
>  Kevin> fun one), and this is why we have omap_hwmod_no_setup_reset().
> 
> Yes, but there's no dts bindings for this, and from a quick test the
> reset handling happens before the device tree is probed.
I have the same issue with TPS62361 on Palmas -> GPIO controls the
voltage register supplying MPU, without any driver setting things up,
GPIO gets reset and obviously voltage value switches to an voltage where
device does not function.

Solution I am working on to solve this is [1]: snippet is part of a
patch that I am working on atm.

This is the right way to do it IMHO. Will allow the driver to exist when
HWMOD will be eventually replaced by some other framework.


[1]: http://pastebin.com/XPmAB1Zb

 
-- 
Regards,
Nishanth Menon

  reply	other threads:[~2013-05-17 18:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-21 15:32 reset handling in am335x hwmod data Peter Korsgaard
2012-12-23 20:58 ` Paul Walmsley
2013-01-10  7:50   ` Peter Korsgaard
2013-01-18 14:18     ` Peter Korsgaard
2013-01-22  2:53     ` Paul Walmsley
2013-05-17 13:50   ` Felipe Balbi
2013-05-17 13:53     ` Peter Korsgaard
2013-05-17 17:08     ` Kevin Hilman
2013-05-17 18:10       ` Peter Korsgaard
2013-05-17 18:19         ` Nishanth Menon [this message]
2013-05-20  6:38           ` Hiremath, Vaibhav
2013-05-20  6:55             ` Hiremath, Vaibhav
2013-05-20 15:06               ` Nishanth Menon
2013-05-20 17:47                 ` Hiremath, Vaibhav
2013-05-20 18:03                   ` Nishanth Menon
2013-05-20 18:20                     ` Hiremath, Vaibhav
2013-06-28 10:54                       ` Felipe Balbi
2013-07-02  4:37                         ` Hiremath, Vaibhav
2013-07-02 13:57                           ` Nishanth Menon

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=20130517181922.GA4439@kahuna \
    --to=nm@ti.com \
    --cc=balbi@ti.com \
    --cc=jacmet@sunsite.dk \
    --cc=khilman@linaro.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).