From: Micha Nelissen <micha@neli.hopto.org>
To: "Bounine, Alexandre" <Alexandre.Bounine@idt.com>
Cc: Alexandre Bounine <alexb@tundra.com>,
linuxppc-dev@lists.ozlabs.org, thomas.moll@sysgo.com
Subject: Re: [PATCH 7/7] powerpc/85xx: Fix the RapidIO maintenance access functions
Date: Thu, 25 Feb 2010 20:20:28 +0100 [thread overview]
Message-ID: <4B86CD7C.6070201@neli.hopto.org> (raw)
In-Reply-To: <0CE8B6BE3C4AD74AB97D9D29BD24E552A54EA6@CORPEXCH1.na.ads.idt.com>
Bounine, Alexandre wrote:
> Hi Micha,
>
> I tested it on my setup - it works.
> Maybe Thomas may give more details on this change.
Did you (for fun) try once to decrease the maintenance window to say, 4
kB? Then you really need these "high" bits to work properly.
Or did you try with some register at offset > 4MB? The Tundra's have
registers going up to 0x14000 or so? So don't need 16MB addressing for that.
Thanks, Micha
>> -----Original Message-----
>> From: Micha Nelissen [mailto:micha@neli.hopto.org]
>> Sent: Wednesday, February 24, 2010 3:21 PM
>> To: Alexandre Bounine
>> Subject: Re: [PATCH 7/7] powerpc/85xx: Fix the RapidIO maintenance
> access functions
>> Alexandre Bounine wrote:
>>> out_be32(&priv->maint_atmu_regs->rowtar,
>>> - (destid << 22) | (hopcount << 12) | ((offset & ~0x3) >>
> 9));
>>> + (destid << 22) | (hopcount << 12) | (offset >> 12));
>>> + out_be32(&priv->maint_atmu_regs->rowtear, (destid >> 10));
>> Did this actually work for you? The (offset >> 12) is due to the 4MB
>> window size right?
>>
>> Micha
>
next prev parent reply other threads:[~2010-02-25 19:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 15:37 [PATCH 7/7] powerpc/85xx: Fix the RapidIO maintenance access functions Alexandre Bounine
[not found] ` <4B858A1F.7020505@neli.hopto.org>
[not found] ` <0CE8B6BE3C4AD74AB97D9D29BD24E552A54EA6@CORPEXCH1.na.ads.idt.com>
2010-02-25 19:20 ` Micha Nelissen [this message]
2010-03-05 6:00 ` tmo
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=4B86CD7C.6070201@neli.hopto.org \
--to=micha@neli.hopto.org \
--cc=Alexandre.Bounine@idt.com \
--cc=alexb@tundra.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=thomas.moll@sysgo.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