- 24 Dec, 2013 29 commits
-
-
Laurent Pinchart authored
The field will be removed from the sh-sci driver. Don't set it and let the driver handle baud rate calculation internally. Signed-off-by:
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> Signed-off-by:
Simon Horman <horms+renesas@verge.net.au>
-
Laurent Pinchart authored
Passing the register base address and IRQ through platform data is deprecated. Use resources instead. Signed-off-by:
-
Laurent Pinchart authored
Passing the register base address and IRQ through platform data is deprecated. Use resources instead. Signed-off-by:
-
Laurent Pinchart authored
Passing the register base address and IRQ through platform data is deprecated. Use resources instead. Signed-off-by:
-
Laurent Pinchart authored
Passing the register base address and IRQ through platform data is deprecated. Use resources instead. Signed-off-by:
-
Laurent Pinchart authored
Passing the register base address and IRQ through platform data is deprecated. Use resources instead. Signed-off-by:
-
Laurent Pinchart authored
Passing the register base address and IRQ through platform data is deprecated. Use resources instead. Signed-off-by:
-
Laurent Pinchart authored
The SCIF driver is transitioning to platform resources. Board code will thus need to define an array of resources for each SCIF device. This is incompatible with the macro-based SCIF platform data definition as an array. Rework the macro to define platform data as individual structures. Signed-off-by:
-
Laurent Pinchart authored
The SCIF driver is transitioning to platform resources. Board code will thus need to define an array of resources for each SCIF device. This is incompatible with the macro-based SCIF platform data definition as an array. Rework the macro to define platform data as individual structures. Signed-off-by:
-
Laurent Pinchart authored
The SCIF driver is transitioning to platform resources. Board code will thus need to define an array of resources for each SCIF device. This is incompatible with the macro-based SCIF platform data definition as an array. Rework the macro to define platform data as individual structures. Signed-off-by:
-
Laurent Pinchart authored
The SCIF driver is transitioning to platform resources. Board code will thus need to define an array of resources for each SCIF device. This is incompatible with the macro-based SCIF platform data definition as an array. Rework the macro to define platform data as individual structures. Signed-off-by:
-
Laurent Pinchart authored
The SCIF driver is transitioning to platform resources. Board code will thus need to define an array of resources for each SCIF device. This is incompatible with the macro-based SCIF platform data definition as an array. Rework the macro to define platform data as individual structures. Signed-off-by:
-
Laurent Pinchart authored
Replace copy-n-paste SCIF platform data and device declaration with a macro. This reduces the amount of code and improves readability. Signed-off-by:
-
Laurent Pinchart authored
Replace copy-n-paste SCIF platform data and device declaration with a macro. This reduces the amount of code and improves readability. Signed-off-by:
-
Laurent Pinchart authored
Replace copy-n-paste SCIF platform data and device declaration with a macro. This reduces the amount of code and improves readability. Signed-off-by:
-
Laurent Pinchart authored
Replace copy-n-paste SCIF platform data and device declaration with a macro. This reduces the amount of code and improves readability. Signed-off-by:
-
Kuninori Morimoto authored
This is needed to use SRC (= Sampling Rate Converter) Signed-off-by:
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> Signed-off-by:
-
Simon Horman authored
-
Laurent Pinchart authored
Computing the baud rate register value requires knowledge of the hardware sampling rate. This information is currently encoded in a baud rate calculation algorithm ID passed through platform data. However, it can be derived from the port type directly in most cases. Compute the sampling rate internally in the driver if the baud rate calculation algorithm ID isn't specified, and allow platforms to override the sampling rate through platform data in special cases (this is only required for SCIFA ports on sh7723 and sh7724, the reason needs to be investigated). Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by:
-
Laurent Pinchart authored
The overrun bit index is a property of the hardware. It's currently computed based on a different and unrelated hardware property, the baud rate calculation algorithm. Compute it using hardware identification information only. Signed-off-by:
-
Laurent Pinchart authored
The driver requests at initialization time GPIOs passed through platform data. No platform makes use of this feature, remove it. Signed-off-by:
-
Laurent Pinchart authored
None of the fields is ever set by board code, and both of them are set in the driver at probe time. Move them out of struct plat_sci_port to struct sci_port. Signed-off-by:
-
Laurent Pinchart authored
Memory and IRQ resources are currently passed to the driver through platform data. Support passing them through the standard platform resources mechanism instead. This deprecates platform data resources. Signed-off-by:
-
Laurent Pinchart authored
The IRQ number can't be modified by the user as the port is fixed. There's no need to check the new IRQ number as it will be ignored by the core. Signed-off-by:
-
Laurent Pinchart authored
The base address, IRQ and baud rate generator parent clock rate can't be changed by userspace. Mark the port as fixed. Signed-off-by:
-
Laurent Pinchart authored
The driver checks if the interrupt number is greater than nr_irqs and returns an error in that case. The same check is already performed by the caller, remove it. Signed-off-by:
-
Laurent Pinchart authored
Rewrite the baud rate register value calculations in easier to read forms. The computed value isn't modified. Signed-off-by:
-
Laurent Pinchart authored
The algorithm isn't used, remove it. Signed-off-by:
-
Laurent Pinchart authored
This helps locating duplicates. Signed-off-by:
-
- 19 Dec, 2013 5 commits
-
-
Wolfram Sang authored
Signed-off-by:
Wolfram Sang <wsa@the-dreams.de> Signed-off-by:
-
Simon Horman authored
The koelsch board uses has an SH ethernet controller which uses a Micrel phy. Select MICREL_PHY for koelsch if SH_ETH is enabled to make use of the Micrel-specific phy driver rather than relying on the generic phy driver. Signed-off-by: -
Laurent Pinchart authored
When CONFIG_COMMON_CLOCK is enabled, call rcar_gen2_clocks_init() in the timer init function to initialize the common clock framework before initializing the clock sources. This will take care of clock initialization when the r8a779[01] boards will be switched to multiplatform kernels. Signed-off-by:
-
Laurent Pinchart authored
Add macros usable by device tree sources to reference r8a7791 clocks by index. Signed-off-by:
-
Laurent Pinchart authored
Add macros usable by device tree sources to reference r8a7790 clocks by index. Signed-off-by:
-
- 14 Dec, 2013 3 commits
-
-
Ben Dooks authored
The PCI sub-system is not enabled by default on ARM and on certain Renesas devices the build does not select it. This means that there are configurations that do not allow the AHB-PCI bridge used for the USB sub-systems to be built. For the R8A7790, R8A7791 and EMEV-2 select MIGHT_HAVE_PCI to allow the PCI drivers to be built. Also select MIGHT_HAVE_PCI for the multi-config where there may be many Reneasas devices selected. Reviewed-by:
Ian Molton <ian.molton@codethink.co.uk> Signed-off-by:
Ben Dooks <ben.dooks@codethink.co.uk> Signed-off-by:
-
Laurent Pinchart authored
Turn clk_enable() and clk_disable() calls into clk_prepare_enable() and clk_disable_unprepare() to get ready for the migration to the common clock framework. Signed-off-by:
Magnus Damm <damm@opensource.se> Acked-by:
-
Laurent Pinchart authored
The break timer accesses hardware registers and thus requires the port to be enabled. It currently ensures this by enabling the port at the beginning of the timer handler, and disabling it at the end. However, the enable/disable operations call the runtime PM sync functions, which are not allowed in atomic context. The current situation is thus broken. This change relies on non-atomic code to enable/disable the port. The break timer will only be started from the IRQ handler, which already runs with the port enabled. We just need to ensure that the port won't be disabled with the timer running, and that's easily done by just cancelling the timer in the port disable function. Signed-off-by:
-
- 12 Dec, 2013 3 commits
-
-
Laurent Pinchart authored
Use the %zu and %pad printk specifiers to print size_t and dma_addr_t variables, and cast pointers to uintptr_t instead of unsigned int where applicable. This fixes warnings on platforms where pointers and/or dma_addr_t have a different size than int. Cc: linux-serial@vger.kernel.org Signed-off-by:
-
Kuninori Morimoto authored
HPB-DMAC has 2 channel for USB Func (= D0/D1) D0 is used as Tx, D1 is used as Rx on this patch Signed-off-by:
-
Ben Dooks authored
If the system has been started in non-secure mode, then the ARM generic timer is not configurable during the kernel initialisation. Currently the only thing we can check for is if the timer has been correctly configured during the boot process. Signed-off-by:
-
