Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
NuttX RTOS
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Container Registry
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
f4grx
NuttX RTOS
Commits
6f4a218c
Commit
6f4a218c
authored
10 years ago
by
Gregory Nutt
Browse files
Options
Downloads
Patches
Plain Diff
Clean-up some comments
parent
2dc25d5f
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
configs/sama5d4-ek/src/sam_maxtouch.c
+12
-12
12 additions, 12 deletions
configs/sama5d4-ek/src/sam_maxtouch.c
with
12 additions
and
12 deletions
configs/sama5d4-ek/src/sam_maxtouch.c
+
12
−
12
View file @
6f4a218c
...
...
@@ -94,15 +94,15 @@ struct sama5d4ek_tscinfo_s
* Private Function Prototypes
****************************************************************************/
/* IRQ/
G
PIO access callbacks. These operations all hidden behind
* callbacks to isolate the maXTouch driver from differences in
G
PIO
/* IRQ/PIO access callbacks. These operations all hidden behind
* callbacks to isolate the maXTouch driver from differences in PIO
* interrupt handling by varying boards and MCUs. If possible,
* interrupts should be configured on both rising and falling edges
* so that contact and loss-of-contact events can be detected.
*
* attach - Attach the maXTouch interrupt handler to the
G
PIO interrupt
* enable - Enable or disable the
G
PIO interrupt
* clear - Acknowledge/clear any pending
G
PIO interrupt
* attach - Attach the maXTouch interrupt handler to the PIO interrupt
* enable - Enable or disable the PIO interrupt
* clear - Acknowledge/clear any pending PIO interrupt
*/
static
int
mxt_attach
(
FAR
const
struct
mxt_lower_s
*
lower
,
mxt_handler_t
isr
,
...
...
@@ -141,15 +141,15 @@ static struct sama5d4ek_tscinfo_s g_mxtinfo =
****************************************************************************/
/****************************************************************************
* IRQ/
G
PIO access callbacks. These operations all hidden behind
* callbacks to isolate the maXTouch driver from differences in
G
PIO
* IRQ/PIO access callbacks. These operations all hidden behind
* callbacks to isolate the maXTouch driver from differences in PIO
* interrupt handling by varying boards and MCUs. If possible,
* interrupts should be configured on both rising and falling edges
* so that contact and loss-of-contact events can be detected.
*
* attach - Attach the maXTouch interrupt handler to the
G
PIO interrupt
* enable - Enable or disable the
G
PIO interrupt
* clear - Acknowledge/clear any pending
G
PIO interrupt
* attach - Attach the maXTouch interrupt handler to the PIO interrupt
* enable - Enable or disable the PIO interrupt
* clear - Acknowledge/clear any pending PIO interrupt
*
****************************************************************************/
...
...
@@ -158,8 +158,8 @@ static int mxt_attach(FAR const struct mxt_lower_s *lower, mxt_handler_t isr,
{
if
(
isr
)
{
/* Just save the address of the handler
for now. The new handler will
*
be attached
when the interrupt
is next enabled
.
/* Just save the address of the handler
and its argument for now. The
*
new handler will called via mxt_interrupt()
when the interrupt
occurs
.
*/
ivdbg
(
"Attaching %p
\n
"
,
isr
);
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment