diff options
author | Sven Van Asbroeck <thesven73@gmail.com> | 2018-12-17 10:48:00 -0500 |
---|---|---|
committer | Shawn Guo <shawnguo@kernel.org> | 2019-01-11 15:16:45 +0800 |
commit | c7995bcb36ef61e8b4136efab31ecf3c9b1633f9 (patch) | |
tree | 7f8be64f47e0407b4f2012df087de0d37cfcb5a3 /tools | |
parent | bus: imx-weim: support multiple address ranges per child node (diff) | |
download | linux-dev-c7995bcb36ef61e8b4136efab31ecf3c9b1633f9.tar.xz linux-dev-c7995bcb36ef61e8b4136efab31ecf3c9b1633f9.zip |
bus: imx-weim: guard against timing configuration conflicts
When specifying weim child devices, there is a risk that more than
one timing setting is specified for the same chip select.
The driver cannot support such a configuration.
In case of conflict, this patch will print a warning to the log,
and will ignore the child node in question.
In this example, node acme@1 will be ignored, as it tries to modify
timing settings for CS0:
&weim {
acme@0 {
compatible = "acme,whatever";
reg = <0 0 0x100>;
fsl,weim-cs-timing = <something>;
};
acme@1 {
compatible = "acme,whatnot";
reg = <0 0x500 0x100>;
fsl,weim-cs-timing = <something else>;
};
};
However in this example, the driver will be happy:
&weim {
acme@0 {
compatible = "acme,whatever";
reg = <0 0 0x100>;
fsl,weim-cs-timing = <something>;
};
acme@1 {
compatible = "acme,whatnot";
reg = <0 0x500 0x100>;
fsl,weim-cs-timing = <something>;
};
};
Signed-off-by: Sven Van Asbroeck <TheSven73@googlemail.com>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions