Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
F
FMC Bus
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
1
Issues
1
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
Wiki
Wiki
image/svg+xml
Discourse
Discourse
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
Projects
FMC Bus
Commits
ce2ad8ad
Commit
ce2ad8ad
authored
Jul 19, 2012
by
Alessandro Rubini
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
fmc: new irq-related operations
parent
cd263d0d
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
15 additions
and
5 deletions
+15
-5
fmc-bus.in
doc/fmc-bus.in
+11
-5
fmc.h
kernel/include/linux/fmc.h
+4
-0
No files found.
doc/fmc-bus.in
View file @
ce2ad8ad
...
...
@@ -185,7 +185,10 @@ struct fmc_operations {
uint32
_
t (*readl)(struct fmc
_
device *d, int offset);
void (*writel)(struct fmc
_
device *d, int offset, uint32
_
t value);
int (*reprogram)(struct fmc
_
device *d, void *data, int len);
int (*irq
_
request)(struct fmc
_
device *d, irq
_
handler
_
t h,
char *name, int flags);
void (*irq
_
ack)(struct fmc
_
device *d);
int (*irq
_
free)(struct fmc
_
device *d);
int (*read
_
ee)(struct fmc
_
device *d, int pos, void *data, int len);
int (*write
_
ee)(struct fmc
_
device *d, int pos, void *data, int len);
}
;
...
...
@@ -216,12 +219,15 @@ The individual methods perform the following tasks:
carrier will reprogram the golden binary -- which will happen
after @i
{
remove
}
time in any case.
@item irq
_
ack
@item irq
_
request
@itemx irq
_
ack
@itemx irq
_
free
Interrupt acknowledge is carrier-specific, so it is abstracted
as an operation. Interrupts on the other hand are expected to be
reported by normal host means, at the IRQ number stated in the
device structure.
Interrupt management is carrier-specific, so it is abstracted
as operations. The interrupt number is listed in the device
structure, but it's only informative for the mezzanine driver.
The handler will receive the @i
{
fmc
}
pointer as @i
{
dev
_
id
}
; the
@i
{
flags
}
argument is still to be defined.
@item read
_
ee
@itemx write
_
ee
...
...
kernel/include/linux/fmc.h
View file @
ce2ad8ad
...
...
@@ -11,6 +11,7 @@
#define __LINUX_FMC_H__
#include <linux/types.h>
#include <linux/device.h>
#include <linux/interrupt.h>
struct
fmc_device
;
struct
fmc_driver
;
...
...
@@ -35,7 +36,10 @@ struct fmc_operations {
uint32_t
(
*
readl
)(
struct
fmc_device
*
d
,
int
offset
);
void
(
*
writel
)(
struct
fmc_device
*
d
,
int
offset
,
uint32_t
value
);
int
(
*
reprogram
)(
struct
fmc_device
*
d
,
void
*
data
,
int
len
);
int
(
*
irq_request
)(
struct
fmc_device
*
d
,
irq_handler_t
h
,
char
*
name
,
int
flags
);
void
(
*
irq_ack
)(
struct
fmc_device
*
d
);
int
(
*
irq_free
)(
struct
fmc_device
*
d
);
int
(
*
read_ee
)(
struct
fmc_device
*
d
,
int
pos
,
void
*
data
,
int
len
);
int
(
*
write_ee
)(
struct
fmc_device
*
d
,
int
pos
,
void
*
data
,
int
len
);
};
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment