From: Kay Sievers <kay.sievers@vrfy.org>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with /proc/iomem on ARM
Date: Wed, 1 Jul 2009 20:46:55 +0200 [thread overview]
Message-ID: <ac3eb2510907011146o25204845i9deb0ebdd114f655@mail.gmail.com> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE190901A13854@mi8nycmail19.Mi8.com>
On Wed, Jul 1, 2009 at 20:24, H Hartley
Sweeten<hartleys@visionengravers.com> wrote:
> On Wednesday, July 01, 2009 11:13 AM, Kay Sievers wrote:
>>> The serial ports on my system are amba bus devices.
>>>
>>>> After all, it seems like this should be fixed in arm somewhere, not to
>>>> copy and store internal driver core pointers, but use the device
>>>> itself to retrieve the values.
>>>
>>> Maybe the problem is in drivers/amba/bus.c? amba_device_register() does:
>>>
>>> dev->res.name = dev_name(&dev->dev);
>>
>> Looks like. If you get the name directly from dev->init_name. Does that work?
>>
>
> The following patch does fix /proc/iomem for the amba uarts on my system.
> Is this the correct approach to fixing the issue?
Looks fine to work around the issue that statically allocated struct
devices can cause. The proper fix would be to convert them to dynamic
objects and get rid of .init_name entirely.
Thanks,
Kay
next prev parent reply other threads:[~2009-07-01 18:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 17:32 H Hartley Sweeten
2009-07-01 17:55 ` Kay Sievers
2009-07-01 18:01 ` H Hartley Sweeten
2009-07-01 18:12 ` Kay Sievers
2009-07-01 18:24 ` H Hartley Sweeten
2009-07-01 18:46 ` Kay Sievers [this message]
2009-07-08 22:09 ` H Hartley Sweeten
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=ac3eb2510907011146o25204845i9deb0ebdd114f655@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=hartleys@visionengravers.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®