Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1397512
| From | Stephen Warren <swarren@wwwdotorg.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Using the mailbox subsystem for plain doorbells? |
| Date | 2016-05-10 01:50 +0200 |
| Message-ID | <rx362-7sX-9@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
Jassi, Does the HW described below sound like something that should be represented using the Linux kernel's mailbox subsystem, and related DT bindings? I think the existing drivers/mailbox/pcc.c is similar, but wanted to double-check. We have some HW that literally just allows a SW-generated interrupt to be generated by our main CPU complex to an auxiliary CPU, and likewise a different interrupt can be generated in the opposite direction. There's no ability to transfer any data; just an IRQ is generated. Our current mailbox implementation just handles IRQ generation/reception so struct mbox_chan_ops.send_data completely ignores the data parameter, and our IRQ handler "receives" hard-coded NULL messages when the IRQ fires. Higher level protocol code (using shared memory along with the plain-IRQ mbox channels) is outside the mailbox driver. Does that fit the mailbox subsystem?
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Using the mailbox subsystem for plain doorbells? Stephen Warren <swarren@wwwdotorg.org> - 2016-05-10 01:50 +0200
Re: Using the mailbox subsystem for plain doorbells? Jassi Brar <jassisinghbrar@gmail.com> - 2016-05-10 05:30 +0200
Re: Using the mailbox subsystem for plain doorbells? Stephen Warren <swarren@wwwdotorg.org> - 2016-05-10 18:00 +0200
Re: Using the mailbox subsystem for plain doorbells? Jassi Brar <jassisinghbrar@gmail.com> - 2016-05-10 18:20 +0200
csiph-web