- 30 Oct, 2014 32 commits
-
-
Yoshihiro Shimoda authored
Enable HS-USB device for the Koelsch board, defining the GPIO that the driver should check when probing (which is the ID output from MAX3355 OTG chip). Note that there will be pinctrl-related error messages if both internal PCI and HS-USB drivers are enabled but they should be just ignored. Signed-off-by:
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com> [Sergei: added pin function/group and prop, moved device node, fixed summary, added changelog] Signed-off-by:
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com> Signed-off-by:
Simon Horman <horms+renesas@verge.net.au>
-
Yoshihiro Shimoda authored
Define the R8A7791 generic part of the HS-USB device node. It is up to the board file to enable the device. Signed-off-by:
-
Yoshihiro Shimoda authored
Enable HS-USB device for the Lager board, defining the GPIO that the driver should check when probing. Since this board doesn't have the OTG ID pin, we assume that GP5_18 (USB0_PWEN) is an ID pin because it is 1 when the SW5 is in position 2-3 (meaning USB function) and 0 in other positions. Note that there will be pinctrl-related error messages if both internal PCI and HS-USB drivers are enabled but they should be just ignored. Signed-off-by:
-
Yoshihiro Shimoda authored
Define the R8A7790 generic part of the HS-USB device node. It is up to the board file to enable the device. Signed-off-by:
-
Yoshihiro Shimoda authored
Signed-off-by:
-
Yoshihiro Shimoda authored
Since the PHY of USB3.0 and EHCI/OHCI ch2 are the same, the USB3.0 driver cannot use the phy driver when the EHCI/OHCI ch2 already used it: phy phy-e6590100.usb-phy.3: phy init failed --> -16 xhci-hcd: probe of ee000000.usb failed with error -16 If so, we have to unbind the EHCI/OHCI ch2, and then we have to bind the USB3.0 driver as the following: echo 0000:02:02.0 > /sys/bus/pci/drivers/ehci-pci/unbind echo 0000:02:01.0 > /sys/bus/pci/drivers/ohci-pci/unbind echo ee000000.usb > /sys/bus/platform/drivers/xhci-hcd/bind Note that there will be pinctrl-related error messages if both internal PCI and USB3.0 are enabled but they should be just ignored: sh-pfc e6060000.pfc: pin GP_5_22 already requested by ee0d0000.pci; cannot claim for ee000000.usb sh-pfc e6060000.pfc: pin-182 (ee000000.usb) status -22 ata1: SATA link down (SStatus 0 SControl 300) sh-pfc e6060000.pfc: could not request pin 182 (GP_5_22) from group usb2 on device sh-pfc Signed-off-by:
-
Yoshihiro Shimoda authored
Signed-off-by:
-
Hisashi Nakamura authored
Signed-off-by:
Hisashi Nakamura <hisashi.nakamura.ak@renesas.com> Signed-off-by:
-
Simon Horman authored
Initialise TMU device using DT when booting bockw using DT-reference. Acked-by:
Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by:
-
Simon Horman authored
This describes all of the TMU hardware of the r8a7778. Each node is disabled and may be enabled as necessary by board DTS files. Acked-by:
-
Geert Uytterhoeven authored
ch0 will be used for clock events and for periodic clock events, ch1 will be used as clock source. Signed-off-by:
Geert Uytterhoeven <geert+renesas@glider.be> Acked-by:
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> Signed-off-by:
-
Geert Uytterhoeven authored
Signed-off-by:
-
Yoshifumi Hosoya authored
Signed-off-by:
Yoshifumi Hosoya <yoshifumi.hosoya.wj@renesas.com> Signed-off-by:
Yoshihiro Kaneko <ykaneko0929@gmail.com> Acked-by:
-
Yoshifumi Hosoya authored
Signed-off-by:
-
Kouei Abe authored
Signed-off-by:
Kouei Abe <kouei.abe.cp@renesas.com> Signed-off-by:
-
Kouei Abe authored
Signed-off-by:
-
Geert Uytterhoeven authored
The clocks property for the scifa2 device node referred to the scifa0 clock index instead of the scifa2 clock index. Signed-off-by:
-
Wolfram Sang authored
SCIF and SCIFA can be plexed onto the same wires on Lager board. The datasheet also describes the wires as SCIFA. So, to make use of the bigger FIFOs switch to SCIFA instead. Signed-off-by:
Wolfram Sang <wsa+renesas@sang-engineering.com> Signed-off-by:
-
Sergei Shtylyov authored
Describe the PCI USB devices that are behind the PCI bridges, adding necessary links to the USB PHY device. Signed-off-by:
-
Sergei Shtylyov authored
Describe the PCI USB devices that are behind the PCI bridges, adding necessary links to the USB PHY device. Based on the original work by Ben Dooks <ben.dooks@codethink.co.uk>. Signed-off-by:
-
Sergei Shtylyov authored
Enable USB PHY device for the Henninger board. Signed-off-by:
-
Sergei Shtylyov authored
Enable USB PHY device for the Koelsch board. Signed-off-by:
-
Sergei Shtylyov authored
Define the R8A7791 generic part of the USB PHY device node. It is up to the board file to enable the device. Signed-off-by:
-
Sergei Shtylyov authored
Enable USB PHY device for the Lager board. Signed-off-by:
-
Sergei Shtylyov authored
Define the R8A7790 generic part of the USB PHY device node. It is up to the board file to enable the device. Signed-off-by:
-
Geert Uytterhoeven authored
This clock drives the INTCA irqpin controller modules. Before, it was assumed enabled by the bootloader or reset state. Signed-off-by:
-
Simon Horman authored
Renesas ARM Based SoC r8a73a4 DT Timers Updates for v3.19 * Initialise CMT1 timer using DT
-
Laurent Pinchart authored
Specify the DU output topology, enable the DU device and configure the related pins. Signed-off-by:
-
Laurent Pinchart authored
The DU device is now instantiated from the device tree, remove the corresponding platform device. Signed-off-by:
-
Laurent Pinchart authored
Specify the DU output topology, enable the DU device and configure the related pins. Signed-off-by:
-
Laurent Pinchart authored
The DU device is now instantiated from the device tree, remove the corresponding platform device. Signed-off-by:
-
Laurent Pinchart authored
Specify the DU output topology, enable the DU device and configure the related pins. Signed-off-by:
-
- 27 Oct, 2014 5 commits
-
-
Laurent Pinchart authored
The Mitsubishi AA104XD12 panel is commonly used with the Marzen, Lager and Koelsch boards. Create a .dtsi file that describe the panel and its connection to the board. Signed-off-by:
-
Laurent Pinchart authored
Add the DU device with a disabled state. Boards that want to enable the DU need to specify the output topology Signed-off-by:
-
Laurent Pinchart authored
Add the DU device with a disabled state. Boards that want to enable the DU need to specify the output topology. Signed-off-by:
-
Laurent Pinchart authored
Add the DU device with a disabled state. Boards that want to enable the DU need to specify the output topology Signed-off-by:
-
Laurent Pinchart authored
The information is already included in the COPYING file in the kernel sources root directory, we don't want to modify all source files when the FSF will move to a new address, and I'm tired of seeing the related checkpatch.pl warnings. Signed-off-by:
-
- 24 Oct, 2014 3 commits
-
-
Simon Horman authored
r8a73a4_add_dt_devices() no longer enables any devices so remove it. Signed-off-by: -
Simon Horman authored
Initialise CMT1 device using DT when booting ape6evm using DT-reference. Signed-off-by: -
Simon Horman authored
Rename r8a7790_register_cmt() as r8a73a4_register_cmt() to reflect name of the SoC in use. The use of r8a7790 appears to be due to historical sharing of code from that SoC. Shared code is no longer used. Signed-off-by:
-
