summaryrefslogtreecommitdiff
path: root/include/dt-bindings/clock/rk3036-cru.h
diff options
context:
space:
mode:
authorDamien Le Moal <damien.lemoal@wdc.com>2017-01-12 15:25:11 +0900
committerMartin K. Petersen <martin.petersen@oracle.com>2017-01-17 14:06:22 -0500
commit68af412c7713b55c01ffc4312320abd10ca70e77 (patch)
tree95e1d382c0115be6c7ccfdbbcabd0182f2f2aa69 /include/dt-bindings/clock/rk3036-cru.h
parent26f2819772af891dee2843e1f8662c58e5129d5f (diff)
scsi: sd: Ignore zoned field for host-managed devices
There is no good match of the zoned field of the block device characteristics page for host-managed devices. For these devices, the zoning model is derived directly from the device type. So ignore the zoned field for these drives. [mkp: typo] Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com> Reviewed-by: Hannes Reinecke <hare@suse.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'include/dt-bindings/clock/rk3036-cru.h')
0 files changed, 0 insertions, 0 deletions
the code `pch->work_list' is protected by `pch->lock'. I don't know if this may cause race conditions. Similarly `pch->cyclic' is written by `pl330_alloc_chan_resources' under `pl330->lock' but read by `pl330_tx_submit' under `pch->lock'. Second, I have removed locking from `pl330_request_channel' and `pl330_release_channel' functions. Function `pl330_request_channel' is only called from `pl330_alloc_chan_resources', so the lock is already held. Function `pl330_release_channel' is called from `pl330_free_chan_resources', which already holds the lock, and from `pl330_del'. Function `pl330_del' is called in an error path of `pl330_probe' and at the end of `pl330_remove', but I assume that there cannot be concurrent accesses to the protected data at those points. Signed-off-by: Iago Abal <mail@iagoabal.eu> Reviewed-by: Marek Szyprowski <m.szyprowski@samsung.com> Signed-off-by: Vinod Koul <vinod.koul@intel.com>
Diffstat (limited to 'include/uapi/misc/Kbuild')