On Thursday 26 May 2016 08:18:30, Meng Yi wrote:
Hi Alexander,
From your backtrace I guess wait_event_timeout is called in some atomic context (might_sleep(); is called inside wait_event_timeout). This has nothing to do with regmap.
Here is my view of point: Since IRQ setup codes using regmap, and which is not setup properly, so wait_event_timeout.
The inital problem came up with 922a9f936e40001f9b921379aab90047d5990923 ("regmap: mmio: Convert to regmap_bus and fix accessor usage"). The commits 9f9f8b863ad130ec0c25f378bdbad64ba71291de, 4f7d6dd4df8b388e2056c89b528254cdd79dea2a and 0dbdb76c0ca8e7caf27c9a210f64c4359e2974a4 tried to fix that. With those I could successfully probe DCU.
Thanks for your information. DCU was able to be probed without those patches, and DCU still not works with those patches.
Yes, sure. DCU was probed fine before 922a9f936e40001f9b921379aab90047d5990923. But this introduced a regression for DCU and also DSPI on LS1021A which got fixed by the other 3 named commits. I didn't try to use DCU for a while, maybe there is another regression. Please try reverting 2ed94f6fde066fb37bc3553b786edb805561699e If that helps the device tree probing does not work in regmap_get_val_endian
Best regards, Alexander