Revision tags: v6.6.25, v6.6.24, v6.6.23, v6.6.16, v6.6.15, v6.6.14, v6.6.13, v6.6.12, v6.6.11, v6.6.10, v6.6.9, v6.6.8, v6.6.7, v6.6.6, v6.6.5, v6.6.4, v6.6.3, v6.6.2, v6.5.11, v6.6.1, v6.5.10, v6.6, v6.5.9, v6.5.8, v6.5.7, v6.5.6, v6.5.5, v6.5.4, v6.5.3, v6.5.2, v6.1.51, v6.5.1, v6.1.50, v6.5, v6.1.49, v6.1.48, v6.1.46, v6.1.45, v6.1.44, v6.1.43, v6.1.42, v6.1.41, v6.1.40, v6.1.39, v6.1.38, v6.1.37, v6.1.36, v6.4, v6.1.35, v6.1.34, v6.1.33, v6.1.32, v6.1.31, v6.1.30, v6.1.29, v6.1.28, v6.1.27, v6.1.26, v6.3, v6.1.25, v6.1.24, v6.1.23, v6.1.22 |
|
#
b59ed26f |
| 26-Mar-2023 |
Moudy Ho <moudy.ho@mediatek.com> |
media: platform: mtk-mdp3: chip config split about component settings
For different chips, different types and numbers of components are configured in the MDP3 to achieve the desired application, wh
media: platform: mtk-mdp3: chip config split about component settings
For different chips, different types and numbers of components are configured in the MDP3 to achieve the desired application, which will cause ID compatibility problems in the same driver.
Subdivide the component ID into two kinds: 1. public_id (compatible with other chips) 2. inner_id (what the current chip actually owns)
In addition, the chip configuration related structures of MDP3 components are integrated into specific file.
Signed-off-by: Moudy Ho <moudy.ho@mediatek.com> Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
show more ...
|
#
0cbfa7c9 |
| 26-Mar-2023 |
Moudy Ho <moudy.ho@mediatek.com> |
media: platform: mtk-mdp3: add files for chip configuration
In order to be compatible with more MDP3 chip settings in further, integrate and separate chip-related configurations into specific files.
media: platform: mtk-mdp3: add files for chip configuration
In order to be compatible with more MDP3 chip settings in further, integrate and separate chip-related configurations into specific files.
Signed-off-by: Moudy Ho <moudy.ho@mediatek.com> Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
show more ...
|