Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1680866
| From | Mark Brown <broonie@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v2] regmap: irq: allow different device for irq chip and regmap |
| Date | 2017-07-04 12:50 +0200 |
| Message-ID | <tZtz4-76W-31@gated-at.bofh.it> (permalink) |
| References | <tV89P-3RQ-7@gated-at.bofh.it> <tVvzs-1Yc-17@gated-at.bofh.it> <tY4jo-64M-33@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Fri, Jun 30, 2017 at 03:33:27PM +0200, Michael Grzeschik wrote: > On Fri, Jun 23, 2017 at 01:00:43PM +0100, Mark Brown wrote: > > syscon is one potential thing here but it seems odd for the sort of > > hardware that syscon handles to be a good fit for regmap-irq. > We have the special case that we use the syscon as the basic driver > underneath some subdevices that vary in function. We have six arcnet > controllers sitting side by side in an 8 byte offset. And after them we > have the next small memory windows for an reset controller and one > interrupt controller which the other devices reference. Why is this a syscon and not a MFD? It sounds exactly like a MFD to me, syscon is more for cases where things are really jumbled together (even in single registers) but that sounds like a bunch of separate register ranges for separate devices that happen to be very close together in address.
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Re: [PATCH v2] regmap: irq: allow different device for irq chip and regmap Mark Brown <broonie@kernel.org> - 2017-07-04 12:50 +0200 Re: [PATCH v2] regmap: irq: allow different device for irq chip and regmap Michael Grzeschik <mgr@pengutronix.de> - 2017-07-05 11:10 +0200
csiph-web