From: richard@nod.at (Richard Weinberger)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Handling interrupts in spidev
Date: Tue, 28 Jan 2014 16:54:12 +0100 [thread overview]
Message-ID: <52E7D2A4.3020407@nod.at> (raw)
In-Reply-To: <1390918329.64761.YahooMailNeo@web125705.mail.ne1.yahoo.com>
Am 28.01.2014 15:12, schrieb Amit Mahadik:
> Thanks Richard. One more question. If I register an SPI irq struct spi_board_info spi_board_info[] structure in machine board.c file; then the request irq api and irq handler
> should be written in board.c file or in the spidev driver.
Never do any programming in the board file.
The purpose if the board file it describing the hardware.
Please note, board files go away, device tree is the way to go.
Thanks,
//richard
next prev parent reply other threads:[~2014-01-28 15:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-26 12:25 Handling interrupts in spidev Amit Mahadik
2014-01-26 15:23 ` Richard Weinberger
2014-01-27 5:37 ` Amit Mahadik
2014-01-27 6:51 ` Richard Weinberger
2014-01-27 9:21 ` Amit Mahadik
2014-01-27 9:23 ` Richard Weinberger
2014-01-28 14:12 ` Amit Mahadik
2014-01-28 15:54 ` Richard Weinberger [this message]
2014-01-28 16:17 ` Vishwanath Govind
2014-02-14 6:19 ` Nilesh Bacchewar
2014-02-14 18:49 ` Anand Moon
2014-02-19 15:01 ` Amit Mahadik
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=52E7D2A4.3020407@nod.at \
--to=richard@nod.at \
--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).