From: Andreas Larsson <andreas-FkzTOoA/JUlBDgjK7y7TUQ@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: jacmet-OfajU3CKLf1/SzgSGea1oA@public.gmane.org,
software-FkzTOoA/JUlBDgjK7y7TUQ@public.gmane.org
Subject: [PATCH 0/3] Add support for sparc, custom set and get functions, and the GRLIB port of the controller
Date: Thu, 11 Oct 2012 16:11:16 +0200 [thread overview]
Message-ID: <1349964679-23244-1-git-send-email-andreas@gaisler.com> (raw)
Hi!
This patchset adds support for sparc, for custom setreg and getreg functions,
and for the GRLIB port of the controller.
On sparc, irq is not present as an IORESOURCE in the struct platform_device
representation. Therefore, irq_of_parse_and_map() is used instead, which for
sparc simply returns an irq number.
The GRLIB port of the controller needs custom getreg and setreg functions to
allow for big endian register access and to deal with the fact that the PRELOW
and PREHIGH registers have been merged into one register.
Cheers,
Andreas
Andreas Larsson (3):
i2c-ocores: Add irq support for sparc
i2c-ocores: Add support for custom getreg and setreg functions
i2c-ocores: Add support for the GRLIB port of the controller.
drivers/i2c/busses/i2c-ocores.c | 74 +++++++++++++++++++++++++++++++++++---
1 files changed, 68 insertions(+), 6 deletions(-)
next reply other threads:[~2012-10-11 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 14:11 Andreas Larsson [this message]
[not found] ` <1349964679-23244-1-git-send-email-andreas-FkzTOoA/JUlBDgjK7y7TUQ@public.gmane.org>
2012-10-11 14:11 ` [PATCH 1/3] i2c-ocores: Add irq support for sparc Andreas Larsson
2012-10-11 14:11 ` [PATCH 2/3] i2c-ocores: Add support for custom getreg and setreg functions Andreas Larsson
2012-10-11 14:11 ` [PATCH 3/3] i2c-ocores: Add support for the GRLIB port of the controller Andreas Larsson
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=1349964679-23244-1-git-send-email-andreas@gaisler.com \
--to=andreas-fkztooa/julbdgjk7y7tuq@public.gmane.org \
--cc=jacmet-OfajU3CKLf1/SzgSGea1oA@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=software-FkzTOoA/JUlBDgjK7y7TUQ@public.gmane.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).