24 Jun, 2016
1 commit
-
Use helper of_platform_default_populate() in linux/of_platform
when possible, instead of calling of_platform_populate() with
the default match table.Acked-by: Shawn Guo
Cc: Signed-off-by: Huang Shijie
Cc: Shawn Guo
Signed-off-by: Kefeng Wang
Signed-off-by: Rob Herring
13 Mar, 2016
1 commit
-
Currently we have an incorrect behaviour when multiple devices
are present under the weim node. For example:&weim {
...
status = "okay";sram@0,0 {
...
status = "okay";
};mram@0,0 {
...
status = "disabled";
};
};In this case only the 'sram' device should be probed and not 'mram'.
However what happens currently is that the status variable is ignored,
causing the 'sram' device to be disabled and 'mram' to be enabled.Change the weim_parse_dt() function to use
for_each_available_child_of_node()so that the devices marked with
'status = disabled' are not probed.Cc:
Suggested-by: Wolfgang Netbal
Signed-off-by: Fabio Estevam
Reviewed-by: Sascha Hauer
Acked-by: Shawn Guo
Signed-off-by: Olof Johansson
02 Mar, 2015
1 commit
-
Probe all children of the WEIM node, reporting any failures. Report
failure from parsing of WEIM node itself if probes of all children fail.Signed-off-by: Alison Chaiken
Acked-by: Sascha Hauer
Signed-off-by: Shawn Guo
20 Oct, 2014
1 commit
-
A platform_driver does not need to set an owner, it will be populated by the
driver core.Signed-off-by: Wolfram Sang
18 Jul, 2014
1 commit
-
There could be some memory map devices located in
a certain chip select region of the i.MX WEIM.
The devices could be attached to a simple bus(for
example, a AXI bus) whose root node is one child
device tree node of the i.MX WEIM device tree node.
There should be a bridge(very likely, software
transparent) bewteen the i.MX WEIM and the simple bus.
This patch makes the i.MX WEIM driver possible to
populate devices on a simple bus. In this way, people
may try various IPs(in a FPGA, maybe) outside of i.MX
chips with the i.MX WEIM embedded.Signed-off-by: Liu Ying
Signed-off-by: Shawn Guo
05 Mar, 2014
1 commit
-
For imx50-weim and imx6q-weim type of devices, there might a WEIM CS
space configuration register in General Purpose Register controller,
e.g. IOMUXC_GPR1 on i.MX6Q.Depending on which configuration of the following 4 is chosen for given
system, IOMUXC_GPR1[11:0] should be set up as 05, 033, 0113 or 01111
correspondingly.CS0(128M) CS1(0M) CS2(0M) CS3(0M)
CS0(64M) CS1(64M) CS2(0M) CS3(0M)
CS0(64M) CS1(32M) CS2(32M) CS3(0M)
CS0(32M) CS1(32M) CS2(32M) CS3(32M)The patch creates a function for such type of devices, which scans
'ranges' property of WEIM node and build the GPR value incrementally.
Thus the WEIM CS GPR can be set up automatically at boot time.Signed-off-by: Shawn Guo
Reviewed-by: Philippe De Muyter
Tested-by: Philippe De Muyter
16 Aug, 2013
5 commits
-
This patch adds WEIM support for all i.MX CPUs supported by the kernel.
Signed-off-by: Alexander Shiyan
Signed-off-by: Shawn Guo -
Signed-off-by: Alexander Shiyan
Signed-off-by: Shawn Guo -
Driver should be called only once at startup, so code converted
to using module_platform_driver_probe().Signed-off-by: Alexander Shiyan
Signed-off-by: Shawn Guo -
Signed-off-by: Alexander Shiyan
Signed-off-by: Shawn Guo -
Driver uses only probe function so no reason to keep variables
in private driver data.Signed-off-by: Alexander Shiyan
Signed-off-by: Shawn Guo
17 Jun, 2013
1 commit
-
The WEIM(Wireless External Interface Module) works like a bus.
You can attach many different devices on it, such as NOR, onenand.In the case of i.MX6q-sabreauto, the NOR is connected to WEIM.
This patch also adds the devicetree binding document.
The driver only works when the devicetree is enabled.Signed-off-by: Huang Shijie
Acked-by: Sascha Hauer
Signed-off-by: Shawn Guo