blob: 729e9d0ed9141ef0c9325179527e77c5f519c3f8 [file] [log] [blame]
#rild
/data/radio/nv_data.bin.* u:object_r:radio_data_file:s0
/dev/block/mmcblk0p4 u:object_r:radio_device:s0
/dev/block/mmcblk0p9 u:object_r:radio_device:s0
/dev/block/platform/omap/omap_hsmmc.0/by-name/radio u:object_r:radio_device:s0
/dev/cdma_.* u:object_r:radio_device:s0
/dev/lte_.* u:object_r:radio_device:s0
/dev/tiler u:object_r:video_device:s0
/dev/ttyFIQ0 u:object_r:console_device:s0
/dev/ttyGS0 u:object_r:radio_device:s0
/dev/ttyGS1 u:object_r:radio_device:s0
/dev/umts_boot0 u:object_r:radio_device:s0
/dev/umts_boot1 u:object_r:radio_device:s0
/dev/umts_ipc0 u:object_r:radio_device:s0
/dev/umts_ramdump0 u:object_r:radio_device:s0
/dev/umts_rfs0 u:object_r:radio_device:s0
/factory(/.*)? u:object_r:efs_file:s0
/factory/bluetooth(/.*)? u:object_r:bluetooth_efs_file:s0
/factory/nv_data.bin.* u:object_r:radio_data_file:s0
#nfc
/dev/ttyO3 u:object_r:nfc_device:s0
#The devices and files used by the hciattach service are device specific
/system/bin/brcm_patchram_plus u:object_r:hci_attach_exec:s0
/dev/ttyO1 u:object_r:hci_attach_dev:s0
# In Samsung Tuna Board, ttyO0 is for uart driver. gps_device is device specific
/dev/ttyO0 u:object_r:gps_device:s0