Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Matteo Croce <technoboy85@gmail.com>
To: Florian Lohoff <flo@rfc822.org>
Cc: linux-mips@linux-mips.org, Eugene Konev <ejka@imfi.kspu.ru>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH][MIPS][3/6]: AR7: VLYNQ bus
Date: Wed, 2 Apr 2008 15:57:08 +0200	[thread overview]
Message-ID: <200804021557.08605.technoboy85@gmail.com> (raw)
In-Reply-To: <20080329095914.GA18263@paradigm.rfc822.org>

Il Saturday 29 March 2008 10:59:14 Florian Lohoff ha scritto:
> What i found in the TI code is that FIRST the local->control needs to
> get set before issueing a remote access so shouldnd the 
> 
> 	vlynq_reg_write(dev->remote ... )
> 
> move behind the dev->local ? I mean the logic is to set a local clock
> divisor - try to access something on the remote end and see if the link
> got up ?!?
> 
> Flo


dunno about the order, maybe "vlynq_reg_write(dev->remote->control, 0);"
and other NULL writes works as a reset...

  parent reply	other threads:[~2008-04-02 13:57 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12  1:21 [PATCH][MIPS][0/6]: AR7 final Matteo Croce
2008-03-12  1:25 ` [PATCH][MIPS][2/6]: AR7 mtd partition map Matteo Croce
2008-03-12  1:26 ` [PATCH][MIPS][3/6]: AR7: VLYNQ bus Matteo Croce
2008-03-29  9:59   ` Florian Lohoff
2008-04-02 12:56     ` Matteo Croce
2008-04-02 18:31       ` Florian Lohoff
2008-04-03  0:19         ` Matteo Croce
2008-04-03  6:08           ` Florian Lohoff
2008-04-02 13:57     ` Matteo Croce [this message]
2008-04-02 14:58     ` Matteo Croce
2008-03-12  1:28 ` [PATCH][MIPS][4/6]: AR7 gpio Matteo Croce
2008-03-12  1:30 ` [PATCH][MIPS][5/6]: AR7: serial hack Matteo Croce
2008-03-12  9:31   ` Thomas Bogendoerfer
2008-03-13  0:38     ` Matteo Croce
2008-03-13  8:45       ` Thomas Bogendoerfer
2008-03-14 15:46         ` Matteo Croce
2008-03-15 10:40           ` Thomas Bogendoerfer
2008-03-16 15:45             ` Matteo Croce
2008-03-18 13:30               ` Thomas Bogendoerfer
2008-03-18 13:43                 ` Sergei Shtylyov
2008-03-18 13:49                   ` Sergei Shtylyov
2008-03-18 14:01                 ` Alan Cox
2008-03-18 14:01                   ` Alan Cox
2008-03-18 15:28                   ` Thomas Bogendoerfer
2008-03-21  1:55               ` Thomas Bogendoerfer
2008-03-27 21:14                 ` Matteo Croce
2008-03-27 21:17                 ` Matteo Croce
2008-03-15 11:38           ` Alan Cox
2008-03-12 11:16   ` Alan Cox
2008-03-13  0:31     ` Matteo Croce
2008-03-13  9:01       ` Thomas Bogendoerfer
2008-03-16 15:27         ` Matteo Croce
2008-03-16 15:49         ` Matteo Croce
2008-03-12  1:34 ` [PATCH][MIPS][6/6]: AR7 leds Matteo Croce
2008-03-13  0:34   ` Matteo Croce
2008-03-12 18:06 ` [PATCH][MIPS][1/6]: AR7: core Matteo Croce
2008-03-12 19:33   ` Ralf Baechle
2008-03-29 10:34   ` Florian Lohoff
  -- strict thread matches above, loose matches on Subject: below --
2007-12-27 18:19 [PATCH][MIPS][0/6]: AR7 refresh Matteo Croce
2007-12-27 18:24 ` [PATCH][MIPS][3/6]: AR7: VLYNQ bus Matteo Croce

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=200804021557.08605.technoboy85@gmail.com \
    --to=technoboy85@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=ejka@imfi.kspu.ru \
    --cc=flo@rfc822.org \
    --cc=linux-mips@linux-mips.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