Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1550615
| From | Jean Delvare <jdelvare@suse.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] i2c: i801: Register optional lis3lv02d i2c device on Dell machines |
| Date | 2017-01-04 11:20 +0100 |
| Message-ID | <sVQPL-3lt-23@gated-at.bofh.it> (permalink) |
| References | <sSZwd-29x-9@gated-at.bofh.it> <sTJIK-7F5-11@gated-at.bofh.it> <sTQ7w-3ld-19@gated-at.bofh.it> <sTQqS-3tD-13@gated-at.bofh.it> <sVtgu-40T-45@gated-at.bofh.it> |
| Organization | SUSE Linux |
On Tue, 3 Jan 2017 10:06:41 +0100, Benjamin Tissoires wrote: > On Dec 29 2016 or thereabouts, Pali Rohár wrote: > > So 4d5538f5882a is breaking lis3lv02d driver... > > Apologies for that. > > I could easily fix this by adding a kernel API to know whether the > provided irq is from Host Notify or if it was coming from an actual > declaration. However, I have no idea how many other drivers would > require this (hopefully only this one). > > One other solution would be to reserve the Host Notify IRQ and let the > actual drivers that need it to set it, but this was not the best > solution according to Dmitri. On my side, I am not entirely against this > given that it's a chip feature, so the driver should be able to know > that it's available. > > Dmitri, Wolfram, Jean, any preferences? I did not look at your work so I do not feel qualified to give advice on the proper way. I trust you to make the right decision :-) -- Jean Delvare SUSE L3 Support
Back to linux.kernel | Previous | Next | Find similar | Unroll thread
Re: [PATCH] i2c: i801: Register optional lis3lv02d i2c device on Dell machines Jean Delvare <jdelvare@suse.de> - 2017-01-04 11:20 +0100
csiph-web