Hi Rob,
On 2021/8/25 0:58, Rob Herring wrote:
On Tue, Aug 24, 2021 at 03:54:15PM +0800, Sugar Zhang wrote:
This is an optional property to describe data path mapping.
Signed-off-by: Sugar Zhang sugar.zhang@rock-chips.com
Documentation/devicetree/bindings/sound/rockchip,pdm.txt | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)
diff --git a/Documentation/devicetree/bindings/sound/rockchip,pdm.txt b/Documentation/devicetree/bindings/sound/rockchip,pdm.txt index 54d94438..b2d7e47 100644 --- a/Documentation/devicetree/bindings/sound/rockchip,pdm.txt +++ b/Documentation/devicetree/bindings/sound/rockchip,pdm.txt @@ -24,6 +24,22 @@ Required properties: pinctrl-names. See ../pinctrl/pinctrl-bindings.txt for details of the property values.
+Optional properties: +- rockchip,path-map: This is a variable length array, that shows the mapping
The schema says this is a fixed length array.
Actually, it varies depends on different controller or application. considering the situation:
for 4 channel, we use path0/1, and hw wired to sdi1/3. we can map them to path0/1 as follows:
rockchip,path-map = <1 3>;
of SDIx to PATHx. By default, they are one-to-one mapping as follows:
path0 <-- sdi0
path1 <-- sdi1
path2 <-- sdi2
path3 <-- sdi3
e.g. "rockchip,path-map = <3 2 1 0>" means the mapping as follows:
path0 <-- sdi3
path1 <-- sdi2
path2 <-- sdi1
path3 <-- sdi0
Example for rk3328 PDM controller:
pdm: pdm@ff040000 {
-- 2.7.4