public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: iMX31 MBX registers Porting problem
Date: Mon, 31 Jan 2011 00:31:28 +0000	[thread overview]
Message-ID: <20110131003128.GD27436@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTin+Mo9YXEfoDAa+btjX5VdiOz1QJp++ck0efPAk@mail.gmail.com>

On Sat, Jan 29, 2011 at 11:48:54PM -0700, Badguy Badguy wrote:
> 2.6.35
> 2.6.38-rc2
>  neither of these worked, provide various dynamic address results for
> the registers,
>  when read do not conform to expected results.
> 
> here are some examples, I am iounmap and kfree when removing correctly
> but I still get a new address for each insert, after removal,
> this does not happen on 2.6.19.2, it's always the same.
> 
> Address: 0xC48A0000
> MBX1_GLOBREG_REVISION: 0x00000000
> 
> Address: 0xC48A8000
> MBX1_GLOBREG_REVISION: 0x00000000
> 
> Address: 0xC48B8000
> MBX1_GLOBREG_REVISION: 0x00000000
> 
> Address: 0xC48C0000
> MBX1_GLOBREG_REVISION: 0x00000000
> 
>  I have been trying to understand the code behind ioremap, and the
> changes involved.

I can't say why you can't access the registers, but as far as the above
goes, please check /proc/vmallocinfo after each insert and remove, and
report anything which looks wrong.

You should see a new entry when you insert, and that entry removed when
you remove your module.  Check that you're calling iounmap() with the
right arguments too.

It might help if you posted a cut-down version of your code which just
demonstrates the problem so others with an iMX31 can try it too.

  reply	other threads:[~2011-01-31  0:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-30  6:48 iMX31 MBX registers Porting problem Badguy Badguy
2011-01-31  0:31 ` Russell King - ARM Linux [this message]
2011-01-31  5:08   ` Chris
2011-01-31 15:45     ` Russell King - ARM Linux
2011-01-31 17:37       ` Chris
2011-02-01 21:05         ` Chris
2011-02-01 21:29           ` Chris

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=20110131003128.GD27436@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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