linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Misbah khan <misbah_khan@engineer.com>
To: linuxppc-embedded@ozlabs.org
Subject: facing problem with io_p2v() function
Date: Wed, 13 Aug 2008 08:31:28 -0700 (PDT)	[thread overview]
Message-ID: <18965524.post@talk.nabble.com> (raw)


Hi all,

I am using io_p2v() function in my driver to get the virtual address mapping
timer control registers

i am passing address as 0x48304024 as base and after getting the virtual
address of it i am reading and writing to it but my any attempt to read the
location or write is giving segmentation fault

If i use __pa() to read the corresponding location it returning as
0x98304024 insted of 0x48304024

I dont know where the mapping is going wrong 

Even when i tried using ioremap() i got the same kernel panic 

Below is the error message 


-------------------------------------------------------------------------------------------------------

In init function
 Read reg address virt 0xd8304024 and phy 0x98304024 are
Unhandled fault: external abort on non-linefetch (0x1028) at 0xd8304024
Internal error: : 1028 [#1]
Modules linked in: omap_timer
CPU: 0    Not tainted  (2.6.22.1-omap3 #1)
PC is at omap_timer_read_register+0x30/0x3c [omap_timer]
LR is at release_console_sem+0x1c0/0x1d4
pc : [<bf000160>]    lr : [<c005f650>]    psr: 60000013
sp : c7f1bea0  ip : c7f1bdd8  fp : c7f1beb4
r10: c8858000  r9 : 00000026  r8 : 00000027
r7 : c06dfdf0  r6 : 00000000  r5 : bf001018  r4 : 00000024
r3 : d8304000  r2 : 00000000  r1 : 60000013  r0 : 0000003d
Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  Segment user
Control: 00c5387f  Table: 80694018  DAC: 00000015
Process insmod (pid: 306, stack limit = 0xc7f1a2d0)
Stack: (0xc7f1bea0 to 0xc7f1c000)
bea0: 00000000 bf001018 c7f1bed4 c7f1beb8 bf0001c4 bf00013c 00000000
bf001280
bec0: bf001100 c06dfdf0 c7f1bef4 c7f1bed8 bf0030c4 bf0001b0 00000000
c006b5c4
bee0: c06dfdc4 c06dfc00 c7f1bfa4 c7f1bef8 c007f514 bf00300c 00000000
c0024380
bf00: 000ce008 00000000 00000000 00000000 00000000 00000000 00000000
00000000
bf20: 00000000 00000000 00000000 00000000 00000000 00000000 c886ca30
c07fc200
bf40: 00000000 c8867c88 c88678f0 00000000 00000054 00000054 0000000a
c886758f
bf60: c8867cd8 bf00110c c8867cb0 00000024 00000000 c035da98 c0030184
000a81fc
bf80: bebf5d74 00014cdd 00000080 c0029f68 c7f1a000 00000000 00000000
c7f1bfa8
bfa0: c0029dc0 c007e1d8 000a81fc bebf5d74 000ce018 00014cdd 000ce008
00000001
bfc0: 000a81fc bebf5d74 00014cdd 00000080 00000000 bebf5d74 bebf5e54
00000061
bfe0: bebf5a20 bebf5a10 0001e1c0 401d2ec0 60000010 000ce018 00000017
0011b8d8
Backtrace:
[<bf000130>] (omap_timer_read_register+0x0/0x3c [omap_timer]) from
[<bf0001c4>] (omap_dm_timer_set_l
oad+0x20/0x5c [omap_timer])
 r5:bf001018 r4:00000000
[<bf0001a4>] (omap_dm_timer_set_load+0x0/0x5c [omap_timer]) from
[<bf0030c4>] (omap_gp_timer_init_mo
de+0xc4/0xf0 [omap_timer])
 r7:c06dfdf0 r6:bf001100 r5:bf001280 r4:00000000
[<bf003000>] (omap_gp_timer_init_mode+0x0/0xf0 [omap_timer]) from
[<c007f514>] (sys_init_module+0x13
48/0x1400)
 r5:c06dfc00 r4:c06dfdc4
[<c007e1cc>] (sys_init_module+0x0/0x1400) from [<c0029dc0>]
(ret_fast_syscall+0x0/0x2c)
Code: e1a01003 e59f000c eb417e8b e5953010 (e7930004)
Segmentation fault

-----------------------------------------------------------------------------------------------------------

Looking forward for the suggestion for the above problem


----- Misbah <><
-- 
View this message in context: http://www.nabble.com/facing-problem-with-io_p2v%28%29-function-tp18965524p18965524.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.

             reply	other threads:[~2008-08-13 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13 15:31 Misbah khan [this message]
2008-08-20 23:47 ` facing problem with io_p2v() function Sergey Temerkhanov
2008-08-21 20:00 ` Olof Johansson

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=18965524.post@talk.nabble.com \
    --to=misbah_khan@engineer.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).