{"action":"created","issue":{"url":"https://api.github.com/repos/raspberrypi/linux/issues/936","labels_url":"https://api.github.com/repos/raspberrypi/linux/issues/936/labels{/name}","comments_url":"https://api.github.com/repos/raspberrypi/linux/issues/936/comments","events_url":"https://api.github.com/repos/raspberrypi/linux/issues/936/events","html_url":"https://github.com/raspberrypi/linux/issues/936","id":69663973,"number":936,"title":"ARCH_BCM270x: Moving more devices to DT","user":{"login":"notro","id":530887,"avatar_url":"https://avatars.githubusercontent.com/u/530887?v=3","gravatar_id":"","url":"https://api.github.com/users/notro","html_url":"https://github.com/notro","followers_url":"https://api.github.com/users/notro/followers","following_url":"https://api.github.com/users/notro/following{/other_user}","gists_url":"https://api.github.com/users/notro/gists{/gist_id}","starred_url":"https://api.github.com/users/notro/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/notro/subscriptions","organizations_url":"https://api.github.com/users/notro/orgs","repos_url":"https://api.github.com/users/notro/repos","events_url":"https://api.github.com/users/notro/events{/privacy}","received_events_url":"https://api.github.com/users/notro/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":13,"created_at":"2015-04-20T19:36:31Z","updated_at":"2015-04-26T13:03:54Z","closed_at":null,"body":"This is a list of the devices in [arch/arm/mach-bcm2709/bcm2709.c](https://github.com/raspberrypi/linux/blob/rpi-4.0.y/arch/arm/mach-bcm2709/bcm2709.c) that isn't loaded through Device Tree:\r\n- bcm2708_dmaman_device  \r\n  This driver allocates DMA channels. The bcm2835-dma driver will take care of this on ARCH_BCM2835.\r\n- bcm2708_vcio_device  \r\n  Mailbox driver. Eric Anholt has worked on upstreaming this functionality, not sure of the current status.\r\n- bcm2708_systemtimer_device  \r\n  I could not find the driver that uses this.\r\n- bcm2708_fb_device  \r\n  This device can move to DT (driver depends on mailbox and dma). Probably still a while until the vc4 graphics driver is ready.\r\n- bcm2708_usb_device  \r\n  Device can move to DT. This usb driver will probably stay with us for some time.\r\n- bcm2708_uart1_device  \r\n  This device should be possible to move to DT, but I don't have a CM to test with.\r\n- bcm2708_powerman_device  \r\n  I could not find the driver that uses this. Maybe [arch/arm/mach-bcm2708/power.c](https://github.com/raspberrypi/linux/blob/rpi-4.0.y/arch/arm/mach-bcm2708/power.c) was meant to use it?\r\n- bcm2708_alsa_devices[0-7]  \r\n  Devices can move to DT.\r\n- bcm2835_hwmon_device  \r\n  The device can move to DT (driver depends on mailbox). Driver is not enabled in the default config.\r\n- bcm2835_thermal_device  \r\n  The device can move to DT (driver depends on mailbox).\r\n- amba_devs (uart0)  \r\n  PR #910 (BCM270x_DT: Configure UART using DT)\r\n\r\nI have made a patch for the following devices: bcm2708_fb_device, bcm2708_usb_device, bcm2708_alsa_devices[0-7], bcm2835_thermal_device\r\nPatch: https://gist.github.com/notro/882b88430626269d0572\r\n(the patch is for Pi2 against rpi-4.0.y)\r\n\r\nAudio: Should we use 2708 in the compatibility string to avoid a possible clash with a future mainline driver?\r\n```\r\n\taudio@0 {\r\n\t\tcompatible = \"bcrm,bcm2835-audio\";\r\n\t\tcompatible = \"bcrm,bcm2708-audio\";\r\n\t};\r\n```\r\n\r\nAre these in use: bcm2708_systemtimer_device, bcm2708_powerman_device ?\r\n\r\nI can make a PR if this is useful. Comments are welcome.\r\n"},"comment":{"url":"https://api.github.com/repos/raspberrypi/linux/issues/comments/96376796","html_url":"https://github.com/raspberrypi/linux/issues/936#issuecomment-96376796","issue_url":"https://api.github.com/repos/raspberrypi/linux/issues/936","id":96376796,"user":{"login":"P33M","id":2474547,"avatar_url":"https://avatars.githubusercontent.com/u/2474547?v=3","gravatar_id":"","url":"https://api.github.com/users/P33M","html_url":"https://github.com/P33M","followers_url":"https://api.github.com/users/P33M/followers","following_url":"https://api.github.com/users/P33M/following{/other_user}","gists_url":"https://api.github.com/users/P33M/gists{/gist_id}","starred_url":"https://api.github.com/users/P33M/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/P33M/subscriptions","organizations_url":"https://api.github.com/users/P33M/orgs","repos_url":"https://api.github.com/users/P33M/repos","events_url":"https://api.github.com/users/P33M/events{/privacy}","received_events_url":"https://api.github.com/users/P33M/received_events","type":"User","site_admin":false},"created_at":"2015-04-26T13:03:54Z","updated_at":"2015-04-26T13:03:54Z","body":"I agree that the use case where we would want USB turned off is of marginal benefit - the power consumption versus connectivity tradeoff doesn't really make sense.\r\n\r\nAs it removes some complexity (for now) from the ARM side code then it seems reasonable to just change the default state in firmware, but in the future we would want the state to be communicated to whatever PM/power domain driver that exists in the upstream world."}}