summaryrefslogtreecommitdiffstats
path: root/drivers/media/dvb-frontends/cx24116.c
diff options
context:
space:
mode:
authorPeter Ujfalusi <peter.ujfalusi@ti.com>2012-11-21 16:15:18 -0700
committerPaul Walmsley <paul@pwsan.com>2012-11-21 16:15:18 -0700
commitc567b0584c352e7f97ced003be46bed8581ddd5b (patch)
tree282feb4b7a0f4b430b363048616f50e27f656594 /drivers/media/dvb-frontends/cx24116.c
parentdad4191d79bded6674529084bcf842c00e4d874a (diff)
downloadblackbird-op-linux-c567b0584c352e7f97ced003be46bed8581ddd5b.tar.gz
blackbird-op-linux-c567b0584c352e7f97ced003be46bed8581ddd5b.zip
ARM: OMAP2+: omap_device: Correct resource handling for DT boot
When booting with DT the OF core can fill up the resources provided within the DT blob. The current way of handling the DT boot prevents us from removing hwmod data for platforms only suppose to boot with DT (OMAP5 for example) since we need to keep the whole hwmod database intact in order to have more resources in hwmod than in DT (to be able to append the DMA resource from hwmod). To fix this issue we just examine the OF provided resources: If we do not have resources we use hwmod to fill them. If we have resources we check if we already able to recive DMA resource, if no we only append the DMA resurce from hwmod to the OF provided ones. In this way we can start removing hwmod data for devices which have their resources correctly configured in DT without regressions. Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com> Acked-by: Benoît Cousson <b-cousson@ti.com> [paul@pwsan.com: fixed checkpatch problem; updated to apply] Signed-off-by: Paul Walmsley <paul@pwsan.com>
Diffstat (limited to 'drivers/media/dvb-frontends/cx24116.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud