From: ahs3@redhat.com (Al Stone)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] Is /dev/port useful on arm64?
Date: Tue, 26 Apr 2016 10:02:30 -0600 [thread overview]
Message-ID: <571F9116.7050000@redhat.com> (raw)
In-Reply-To: <4771157.GTXbP8MYg9@wuerfel>
On 04/25/2016 04:43 PM, Arnd Bergmann wrote:
> On Monday 25 April 2016 16:35:04 Al Stone wrote:
>>
>> However, /dev/port is used for both ISA and PCI IO ports. So, this led me
>> to what may be a dumb question: is there really a need for PCI support in
>> /dev/port for arm64?
>>
>> Supporting ISA just seems silly, at least from an ARMv8 server standpoint,
>> but PCI is less clear to me. Anyone have opinions one way or the other?
>
> Hisilicon has an ISA-like bus in their system, in form of LPC.
Right, I'd heard about that one.
>> It seems like it would be a waste of time to do the work to make sure the
>> PCI ports work correctly only to find out they will never be used, but I
>> can't think of anyone that actually needs them.
>
> I think we should change the /dev/port implementation to interact with
> the architecture code so it knows which addresses have been registered
> through pci_ioremap_io to ensure that accessing it at least doesn't
> predictably crash the kernel.
Yeah, agreed, but a more long term solution than I personally need today.
I'll look into it a bit more, though.
> Aside from that, most distros probably want to disable it anyway along
> with /dev/mem, but an embedded user can access the two if they absolutely
> need to.
>
> Arnd
This is what I was thinking, too, but I didn't want to cut anything
short if someone was actually using it.
--
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Red Hat, Inc.
ahs3 at redhat.com
-----------------------------------
prev parent reply other threads:[~2016-04-26 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 22:35 [RFC] Is /dev/port useful on arm64? Al Stone
2016-04-25 22:43 ` Arnd Bergmann
2016-04-26 16:02 ` Al Stone [this message]
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=571F9116.7050000@redhat.com \
--to=ahs3@redhat.com \
--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