linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Domen Puncer <domen.puncer@telargo.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/2] mpc52xx: stop drivers from accessing clock config directly
Date: Wed, 24 Oct 2007 21:12:06 +0200	[thread overview]
Message-ID: <20071024191206.GD3369@nd47.coderock.org> (raw)
In-Reply-To: <20071024182308.21194.69416.stgit@trillian.cg.shawcable.net>

On 24/10/07 12:24 -0600, Grant Likely wrote:
> Domen,
> 
> Here's a real solution to the problem.  I've somewhat tested this on
> the lite5200b.  Can you give it a spin on efika and see if SPI still
> works for you?

My test case was lite5200b too, I don't think I ever tried SPI on
efika.
(Are even the right pins on irda connector, or is a necessary line
missing?)


	Domen

> 
> Thanks,
> g.
> 
> --
> Grant Likely, B.Sc. P.Eng.
> Secret Lab Technologies Ltd.

-- 
Domen Puncer | Research & Development
.............................................................................................
Telargo d.o.o. | Zagrebška cesta 20 | 2000 Maribor | Slovenia
.............................................................................................
www.telargo.com

  parent reply	other threads:[~2007-10-24 19:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24 18:24 [PATCH 0/2] mpc52xx: stop drivers from accessing clock config directly Grant Likely
2007-10-24 18:24 ` [PATCH 1/2] mpc52xx: add cdm (clock module) helper function for PSCs Grant Likely
2007-10-25  0:50   ` Stephen Rothwell
2007-10-24 18:24 ` [PATCH 2/2] mpc5200: psc-spi driver must not touch port_config or cdm registers Grant Likely
2007-10-24 19:12 ` Domen Puncer [this message]
2007-10-24 20:14   ` [PATCH 0/2] mpc52xx: stop drivers from accessing clock config directly Grant Likely
2007-10-24 20:54     ` Domen Puncer
2007-10-25 12:29     ` Domen Puncer

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=20071024191206.GD3369@nd47.coderock.org \
    --to=domen.puncer@telargo.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@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).