From: "John Rigby" <jcrigby@gmail.com>
To: "Pedro Luis D. L." <carcadiz@hotmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: LITE5200B Powerfail
Date: Tue, 19 Dec 2006 10:34:16 -0700 [thread overview]
Message-ID: <4b73d43f0612190934t53fdd35ap98243ba107eb446c@mail.gmail.com> (raw)
In-Reply-To: <4b73d43f0612151752x1602392ehe9933e71fa1ac456@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2409 bytes --]
According to the Lite5200B schematic
http://www.freescale.com/files/32bit/hardware_tools/schematics/lite5200BSCH.pdf
PSC2_4 is tied to a signal called PWR_DN_CTL_STS via a zero ohm resistor
R88. If you want to use PSC2_4 as something else you probably need to
remove R88.
On 12/15/06, John Rigby <jcrigby@gmail.com> wrote:
>
> Have you looked at the Lite5200B schematic to see where the signals in
> question go? Maybe you trying to drive something tied to ground high or
> vice-versa.
>
> On 12/15/06, Pedro Luis D. L. <carcadiz@hotmail.com> wrote:
> >
> > Hi all,
> >
> > I not pretty sure if this is the correct forum to ask for a solution but
> > I
> > know that some of you have worked on a driver to make PSCs in this board
> > work in an I2S mode.
> >
> > Have you ever have powerfail problems when writing the configuration
> > registers for this mode?
> >
> > I´ve delimited the problem:
> > - GPIO Port Config register stores without problems the value "111" in
> > bits
> > 25:27 (PSC2 to work in CODEC2 functionality with MCLK).
> > - When I write a "1" in PSC2->SICR register bit GenClk to ensure that
> > clock
> > and FrameSync are generated internally from MCLK the systems suffers a
> > powerfail and I suppose that´s consecuence or some kind of shortcircuit.
> > I´ve followed the same steps made by Bob Peterson in
> > http://ozlabs.org/pipermail/linuxppc-embedded/2005-September/020210.html
> > to write the configuration in the proper registers but I still suffer
> > the
> > powerfail when GenClk is activated or, if I activate that bit first,
> > when
> > Port Config is written.
> > I´m also trying to understand how things are done in Roman Fietze driver
> > but
> > can´t find a difference. That makes me think that perhaps other
> > registers
> > must be modificated before driver loading. Meanwhile, I keep waiting for
> >
> > Grant Likely release, :-).
> > Has this happened to someone before?
> >
> > Thanks for your help.
> >
> > Pedro.
> >
> > _________________________________________________________________
> > Horóscopo, tarot, numerología... Escucha lo que te dicen los astros.
> > http://astrocentro.msn.es/
> >
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded@ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> >
>
>
[-- Attachment #2: Type: text/html, Size: 3714 bytes --]
next prev parent reply other threads:[~2006-12-19 17:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 15:33 LITE5200B Powerfail Pedro Luis D. L.
2006-12-16 1:52 ` John Rigby
2006-12-19 17:34 ` John Rigby [this message]
2006-12-19 17:36 ` Pedro Luis D. L.
2007-01-19 11:17 ` Pedro Luis D. L.
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=4b73d43f0612190934t53fdd35ap98243ba107eb446c@mail.gmail.com \
--to=jcrigby@gmail.com \
--cc=carcadiz@hotmail.com \
--cc=linuxppc-embedded@ozlabs.org \
/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).