From: andre@bitwigglers.org (Andre Haupt)
To: kernelnewbies@lists.kernelnewbies.org
Subject: LPC bus access howto
Date: Tue, 22 Nov 2011 11:01:03 +0100 [thread overview]
Message-ID: <20111122100103.GA6754@localhost.localdomain> (raw)
In-Reply-To: <20111121175330.18729ac4@xilun>
On Mon, Nov 21, 2011 at 05:53:30PM +0100, Guillaume Knispel wrote:
> On Mon, 21 Nov 2011 17:01:29 +0100
> Andre Haupt <andre@bitwigglers.org> wrote:
>
> > Hi all,
> >
> > We have a FPGA which will be connected to the LPC bus. This FPGA will
> > provide some GPIO functionality, a rotary encoder, etc.
> >
> > Now i want to write a kernel driver to talk to this FPGA.
> > I am unsure how to get access to the LPC bus in the first place.
> > What kernel APIs should i use? How to get the memory mapping right, etc?
>
> The LPC is typically automatically mapped by the hardware (southbridge)
> for some fixed ranges, various configurable ranges and might also use
> PCI substractive decoding.
>
> LPC is indeed an ISA bus with the physical layer replaced by something
> with fewer signals, but from the point of view of the software there is
> almost no difference, so look for how to program ISA drivers and you
> will probably have your answer.
So request_mem_region(), ioremap(), ioread*() and iowrite*() are my
friends here right?
Still unsure how to obtain the LPC base address. Is this mapped to
0xA0000-0xFFFFF as with ISA?
cheers,
Andre
prev parent reply other threads:[~2011-11-22 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 16:01 LPC bus access howto Andre Haupt
2011-11-21 16:53 ` Guillaume Knispel
2011-11-22 10:01 ` Andre Haupt [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=20111122100103.GA6754@localhost.localdomain \
--to=andre@bitwigglers.org \
--cc=kernelnewbies@lists.kernelnewbies.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).