/* * linux/drivers/video/macmodes.h -- Standard MacOS video modes * * Copyright (C) 1998 Geert Uytterhoeven * * This file is subject to the terms and conditions of the GNU General Public * License. See the file COPYING in the main directory of this archive for * more details. */ #ifndef _VIDEO_MACMODES_H #define _VIDEO_MACMODES_H /* * Video mode values. * These are supposed to be the same as the values that Apple uses in * MacOS. */ #define VMODE_NVRAM 0 #define VMODE_512_384_60I 1 /* 512x384, 60Hz interlaced (NTSC) */ #define VMODE_512_384_60 2 /* 512x384, 60Hz */ #define VMODE_640_480_50I 3 /* 640x480, 50Hz interlaced (PAL) */ #define VMODE_640_480_60I 4 /* 640x480, 60Hz interlaced (NTSC) */ #define VMODE_640_480_60 5 /* 640x480, 60Hz (VGA) */ #define VMODE_640_480_67 6 /* 640x480, 67Hz */ #define VMODE_640_870_75P 7 /* 640x870, 75Hz (portrait) */ #define VMODE_768_576_50I 8 /* 768x576, 50Hz (PAL full frame) */ #define VMODE_800_600_56 9 /* 800x600, 56Hz */ #define VMODE_800_600_60 10 /* 800x600, 60Hz */ #define VMODE_800_600_72 11 /* 800x600, 72Hz */ #define VMODE_800_600_75 12 /* 800x600, 75Hz */ #define VMODE_832_624_75 13 /* 832x624, 75Hz */ #define VMODE_1024_768_60 14 /* 1024x768, 60Hz */ #define VMODE_1024_768_70 15 /* 1024x768, 70Hz (or 72Hz?) */ #define VMODE_1024_768_75V 16 /* 1024x768, 75Hz (VESA) */ #define VMODE_1024_768_75 17 /* 1024x768, 75Hz */ #define VMODE_1152_870_75 18 /* 1152x870, 75Hz */ #define VMODE_1280_960_75 19 /* 1280x960, 75Hz */ #define VMODE_1280_1024_75 20 /* 1280x1024, 75Hz */ #define VMODE_1152_768_60 21 /* 1152x768, 60Hz Titanium PowerBook */ #define VMODE_1600_1024_60 22 /* 1600x1024, 60Hz 22" Cinema Display */ #define VMODE_MAX 22 #define VMODE_CHOOSE 99 #define CMODE_NVRAM -1 #define CMODE_CHOOSE -2 #define CMODE_8 0 /* 8 bits/pixel */ #define CMODE_16 1 /* 16 (actually 15) bits/pixel */ #define CMODE_32 2 /* 32 (actually 24) bits/pixel */ extern int mac_vmode_to_var(int vmode, int cmode, struct fb_var_screeninfo *var); extern int mac_var_to_vmode(const struct fb_var_screeninfo *var, int *vmode, int *cmode); extern int mac_map_monitor_sense(int sense); extern int mac_find_mode(struct fb_var_screeninfo *var, struct fb_info *info, const char *mode_option, unsigned int default_bpp); /* * Addresses in NVRAM where video mode and pixel size are stored. */ #define NV_VMODE 0x140f #define NV_CMODE 0x1410 #endif /* _VIDEO_MACMODES_H */ dden' name='id' value='91539eb1fda2d530d3b268eef542c5414e54bf1a'/>
path: root/include/net/irda/parameters.h
diff options
context:
space:
mode:
authorIago Abal <mail@iagoabal.eu>2017-01-11 14:00:21 +0100
committerVinod Koul <vinod.koul@intel.com>2017-01-25 15:35:11 +0530
commit91539eb1fda2d530d3b268eef542c5414e54bf1a (patch)
tree960f5ca6342ad20837aff18aad6e8ecd7da32fd6 /include/net/irda/parameters.h
parent6610d0edf6dc7ee97e46ab3a538a565c79d26199 (diff)
dmaengine: pl330: fix double lock
The static bug finder EBA (http://www.iagoabal.eu/eba/) reported the following double-lock bug: Double lock: 1. spin_lock_irqsave(pch->lock, flags) at pl330_free_chan_resources:2236; 2. call to function `pl330_release_channel' immediately after; 3. call to function `dma_pl330_rqcb' in line 1753; 4. spin_lock_irqsave(pch->lock, flags) at dma_pl330_rqcb:1505. I have fixed it as suggested by Marek Szyprowski. First, I have replaced `pch->lock' with `pl330->lock' in functions `pl330_alloc_chan_resources' and `pl330_free_chan_resources'. This avoids the double-lock by acquiring a different lock than `dma_pl330_rqcb'. NOTE that, as a result, `pl330_free_chan_resources' executes `list_splice_tail_init' on `pch->work_list' under lock `pl330->lock', whereas in the rest of 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/net/irda/parameters.h')