diff options
| author | Archit Taneja <[email protected]> | 2016-05-18 15:06:03 +0530 |
|---|---|---|
| committer | Rob Clark <[email protected]> | 2016-07-16 10:08:50 -0400 |
| commit | a2b3a5571f386e23b56164396292675bac6f2a19 (patch) | |
| tree | da55bd915480935faa6db2168cc1266294ae65eb /net/lapb/lapb_timer.c | |
| parent | 7429d860c1dce7361f97179ad096f1b0e64d40c4 (diff) | |
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 <[email protected]>
Signed-off-by: Rob Clark <[email protected]>
Diffstat (limited to 'net/lapb/lapb_timer.c')
0 files changed, 0 insertions, 0 deletions