Archit Taneja a2b3a5571f drm/msm: Get irq number within kms driver itself
The driver gets the irq number using platform_get_irq on the main kms
platform device. This works fine since both MDP4 and MDP5 currently
have a flat device hierarchy. The platform device tied with the
drm_device points to the MDP DT node in both cases.

This won't work when MDP5 supports a tree-like hierarchy. In this
case, the platform device tied to the top level drm_device is the
MDSS DT node, and the irq we need for KMS is the one generated by
MDP5, not MDSS.

Get the irq number from the MDP4/5 kms driver itself. Each driver
can later provide the irq number based on what device hierarchy it
uses.

While we're at it, call drm_irq_install only when we have a valid KMS
driver.

Signed-off-by: Archit Taneja <architt@codeaurora.org>
Signed-off-by: Rob Clark <robdclark@gmail.com>
2016-07-16 10:08:50 -04:00
..
2016-06-24 23:36:20 +02:00
2016-05-31 11:52:59 -07:00
2016-06-18 06:04:01 -10:00
2016-05-24 11:00:20 -07:00
2016-07-02 15:56:01 +10:00
2016-05-19 11:27:09 -07:00
2016-06-09 22:38:16 +02:00
2016-06-18 06:05:28 -10:00
2016-07-02 15:56:01 +10:00
2016-05-18 16:38:59 -07:00
2016-05-27 15:26:11 -07:00
2016-06-23 00:29:32 +02:00
2016-07-02 15:56:01 +10:00
2016-05-26 19:34:26 -07:00
2016-06-09 14:28:28 -06:00
2016-05-27 15:26:11 -07:00
2016-04-30 13:56:46 -07:00
2016-06-15 09:51:35 +01:00
2016-06-10 23:06:21 -07:00
2016-07-16 11:23:50 +10:00
2016-05-20 21:26:15 -07:00
2016-05-29 22:32:27 -07:00
2016-05-26 19:34:26 -07:00
2016-05-20 18:33:37 -07:00
2016-05-28 12:23:12 -07:00
2016-04-30 14:15:56 -07:00
2016-07-02 15:56:01 +10:00
2016-05-01 14:11:12 -07:00
2016-05-31 21:25:52 -06:00
2016-05-10 01:19:26 -07:00
2016-06-07 12:42:58 +03:00
2016-05-23 11:18:01 -07:00