* Franklin S Cooper Jr [151028 14:02]:
> Add device tree entry for the error location module.
>
> Signed-off-by: Franklin S Cooper Jr
Applying this one into omap-for-v4.5/dt thanks.
Tony
> arch/arm/boot/dts/omap4.dtsi | 8
> 1 file changed, 8
* Vignesh R [151129 21:16]:
> Add qspi memory mapped region entries for DRA7xx based SoCs. Also,
> update the binding documents for the controller to document this change.
>
> Acked-by: Rob Herring
> Signed-off-by: Vignesh R
> ---
>
> v4: No
* Dmitry Lifshitz [151124 22:41]:
> + {
> + status = "okay";
> + pinctrl-names = "default";
> + pinctrl-0 = <_pins_default>;
> + clock-frequency = <10>;
> +
> + rtc0: rtc@56 {
> + compatible = "emmicro,em3027";
> + reg =
* Nishanth Menon [151126 21:03]:
> On 11/26/2015 02:31 AM, Vignesh R wrote:
> > Uart1 rxd is wakeup capable on DRA72 EVM. Hence, mark rxd line as
> > wakeup capable. This is similar to commit 66b0436977e2c ("ARM: dts:
> > dra7-evm: Mark uart1 rxd as wakeup capable") for DRA74 EVM.
>
* Aaro Koskinen [151123 13:33]:
> Fix a typo when registering HW RNG.
Applying into omap-for-v4.5/soc thanks.
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
* Franklin S Cooper Jr [151028 14:02]:
> ELM address information is provided by device tree. No longer need
> to include this information within hwmod.
>
> This patch has only been boot tested.
>
> Signed-off-by: Franklin S Cooper Jr
And this one seems safe for
* Mugunthan V N [151118 23:02]:
> Adding missed spi alias for qspi which helps probe the qspi
> device in U-Boot.
>
> Mugunthan V N (2):
> dts: dra7: add spi alias for qspi
> arm: dts: am4372: add spi alias for qspi
>
> arch/arm/boot/dts/am4372.dtsi | 1 +
>
* Rob Herring [151112 06:02]:
> On Tue, Oct 27, 2015 at 01:36:36PM +0100, Heiko Schocher wrote:
> > remove tps65217.dtsi and adapt all boards, which
> > used it.
> >
> > Signed-off-by: Heiko Schocher
> > Tested-by: Keerthy
> > Acked-by: Mark
* Heiko Schocher [151117 00:25]:
> --- /dev/null
> +++ b/arch/arm/boot/dts/am335x-shc.dts
> + {
> + compatible = "ti,tps65217";
> + ti,pmic-shutdown-controller;
> +
> + regulators {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> +
* Nikita Kiryanov [151124 05:20]:
> + {
> + pinctrl-names = "default";
> + pinctrl-0 = <_pins_default>;
> +};
> +
Please get rid of the extra line at the end of the file.. It will cause
whitespace warnings when applying and will also cause issues applying
other
* Dmitry Lifshitz [151130 06:27]:
> +++ b/arch/arm/boot/dts/am57xx-cl-som-am57x.dts
> + tps659038_pmic {
> + compatible = "ti,tps659038-pmic";
> +
> + regulators {
> + smps12_reg: smps12 {
> +
* Nishanth Menon [151022 19:49]:
> On 10/22/2015 08:01 PM, Praneeth wrote:
> > Hi Nishanth,
> >
> > On 10/22/2015 07:24 PM, Praneeth Bajjuri wrote:
> >> From: "J.D. Schroeder"
> >>
> >> UART4 low level debug support. This helps in debugging with UART4
> >>
We don't need timers right away and initializing them later gives us few
nice things like interrupts and kmalloc. As the timers have a dependency
to the clock framework, we're better off initializing things later rather
than early if things go wrong. And this allows us to make the mux clock
driver
We want to be able to probe a few selected device drivers before hwmod
code populates the clocks in omap_hwmod_setup_all(). This allows us to
convert most of the clock drivers into regular device drivers.
We only need a few minimal clock drivers early for the system timers to
select between the
Hi,
Here are some initcall changes to initialize things a bit later.
This make it easier to make timers into drivers and allows us
to make most of the clocks into regular device drivers.
Regards,
Tony
Tony Lindgren (2):
ARM: OMAP2+: Initialize timers later with late_time_init
ARM: OMAP2+:
Am Montag, den 16.11.2015, 14:24 +0200 schrieb Grygorii Strashko:
> On 11/16/2015 01:25 PM, Lucas Stach wrote:
> > omap_interconnect_sync() is the only user of the SRAM scratch area
> > allocated in the omap4_sram_init initcall. The interconnect sync is
> > used exclusively in the OMAP4 specific
* Tony Lindgren [151006 05:12]:
> * Tero Kristo [150924 07:30]:
> > PRM driver now supports reset controller for the defined reset lines.
> > Reset configurations are provided through device tree. Later, functionality
> > like hwmod and system reboot will be
* Grygorii Strashko [151127 12:11]:
> Hi Felipe,
>
> On 11/20/2015 08:21 PM, Felipe Balbi wrote:
> > Grygorii Strashko writes:
> >> Since system clocksource is finally selected by Clocksource core at
> >> fs_initcall stage during boot there
* Heiko Schocher [151129 22:51]:
> Hello all,
>
> Am 18.11.2015 um 09:24 schrieb Heiko Schocher:
> >Hello Dave,
> >
> >Am 17.11.2015 um 22:29 schrieb Dave Gerlach:
> >>Hi,
> >>On 11/17/2015 02:24 AM, Heiko Schocher wrote:
> >>>add support for the am335x based shc board.
> >>>
>
* Tony Lindgren [151125 10:40]:
> Linus,
>
> * Tony Lindgren [151118 16:25]:
> > * Javier Martinez Canillas [151117 05:51]:
> > > Hello Linus,
> > >
> > > On 11/17/2015 10:47 AM, Linus Walleij wrote:
> > > > On Fri, Nov 13, 2015 at
* Andrew F. Davis [151116 08:39]:
> On 11/13/2015 08:47 AM, Tony Lindgren wrote:
> >* Javier Martinez Canillas [151112 20:55]:
> >>Hello Tony,
> >>
> >>This series converts all the remaining OMAP boards that didn't use the
> >>IOPAD macros to specify the
* Roger Quadros [151023 00:09]:
> On 21/10/15 18:20, Tony Lindgren wrote:
> > * Roger Quadros [151021 01:31]:
> >>
> >> I couldn't run randconfig beyond few iterations as it keeps failing
> >> everywhere. How do we limit the randconfig options to OMAP only
> >>
On Mon, 30 Nov 2015, Pali Rohár wrote:
> On Monday 30 November 2015 07:23:53 Tony Lindgren wrote:
> > * Pali Rohár [151129 16:16]:
> > > On Monday 30 November 2015 01:09:17 Nicolas Pitre wrote:
> > > > On Sun, 29 Nov 2015, Russell King - ARM Linux wrote:
> > > > > On Sat,
* Pali Rohár [151129 16:16]:
> On Monday 30 November 2015 01:09:17 Nicolas Pitre wrote:
> > On Sun, 29 Nov 2015, Russell King - ARM Linux wrote:
> > > On Sat, Nov 28, 2015 at 12:34:23PM -0500, Nicolas Pitre wrote:
> > > > Good. And Arnd likes the idea too. So we might be
On Wed, Nov 25, 2015 at 05:03:00PM -0600, Rob Herring wrote:
> On Tue, Nov 24, 2015 at 03:19:02PM +0200, Nikita Kiryanov wrote:
> > Add basic support for SBC-T43: a CM-T43 based single board computer.
> > CM-T43 is an AM437x based System-on-Module designed to serve as a building
> > block in
Errata i810 states that DPLL controller can get stuck while transitioning
to a power saving state, while its M/N ratio is being re-programmed.
As a workaround, before re-programming the M/N ratio, SW has to ensure
the DPLL cannot start an idle state transition. SW can disable DPLL
idling by
On Fri, Oct 30, 2015 at 10:00:35AM +0200, Peter Ujfalusi wrote:
> Hi,
>
> Changes since v1:
> - Fixed issue introduced by the bitops patch: wrong error check, also switch
> to
> use find_first_zero_bit() instead of find_next_zero_bit()
>
> Cover letter:
>
> This series depends on the eDMA
On Wed, Nov 25, 2015 at 04:57:34PM -0600, Rob Herring wrote:
> On Tue, Nov 24, 2015 at 03:19:13PM +0200, Nikita Kiryanov wrote:
> > CompuLab SB-SOM baseboard is a carrier board for multiple arm-based SoMs.
> > It currently supports (with minor adjustments to assembly) CM-T43, CM-T54,
> > and
ARM TWD and Global timer are clocked by PERIPHCLK which is MPU_CLK/2.
But now they are clocked by dpll_mpu_m2_ck == MPU_CLK and, as result.
Timekeeping core misbehaves. For example, execution of command
"sleep 5" will take 10 sec instead of 5.
Hence, fix it by adding mpu_periphclk
On Monday 30 November 2015 07:23:53 Tony Lindgren wrote:
> * Pali Rohár [151129 16:16]:
> > On Monday 30 November 2015 01:09:17 Nicolas Pitre wrote:
> > > On Sun, 29 Nov 2015, Russell King - ARM Linux wrote:
> > > > On Sat, Nov 28, 2015 at 12:34:23PM -0500, Nicolas Pitre
Hi,
* Peter Ujfalusi [151130 05:49]:
>
> For each dmaengine driver an array of DMA device, slave and the parameter
> for the filter function needs to be added:
>
> static struct dma_filter_map da830_edma_map[] = {
> DMA_FILTER_ENTRY("davinci-mcasp.0", "rx",
On Sun, Nov 29, 2015 at 02:10:01PM +0200, Dmitry Lifshitz wrote:
> Hi Nishanth,
>
> Thank you for the provided feedback.
>
> On 11/25/2015 11:36 PM, Nishanth Menon wrote:
> >On 11/25/2015 12:39 AM, Dmitry Lifshitz wrote:
> >[...]
> >
> >>diff --git a/arch/arm/boot/dts/am57xx-cl-som-am57x.dts
>
* Neil Armstrong [151102 03:14]:
> In order to set the currently platform dependent dmtimer
> functions pointers as platform data for the pwm-omap-dmtimer
> platform driver, add it to plat-omap auxdata_lookup table.
>
> Suggested-by: Tony Lindgren
>
* Suman Anna [151005 16:35]:
> Add the hwmod data for GPTimer 12. GPTimer 12 is present in
> WKUPAON power domain and is clocked from a secure 32K clock.
> GPTimer 12 serves as a secure timer on HS devices, but is
> available for kernel on regular GP devices.
>
> The hwmod link is
* Suman Anna [151006 09:06]:
> On 10/06/2015 02:52 AM, Tony Lindgren wrote:
> > * Felipe Balbi [151005 17:51]:
> >>
> >> according to Tony we should avoid using status at all for in-SoC
> >> devices.
> >>
> >> Tony, can you confirm I understood you correctly ?
> >
>
* Franklin S Cooper Jr [151015 10:42]:
> Add dma channel information to the gpmc. Although not enabled by
> default this will allow prefetch-dma to be used.
Picking up this patch only out of the series into omap-for-v4.5/dt.
The documentation patch does not apply as it has a
On 11/30/2015 07:27 PM, Lucas Stach wrote:
> Am Montag, den 16.11.2015, 14:24 +0200 schrieb Grygorii Strashko:
>> On 11/16/2015 01:25 PM, Lucas Stach wrote:
>>> omap_interconnect_sync() is the only user of the SRAM scratch area
>>> allocated in the omap4_sram_init initcall. The interconnect sync
* Neil Armstrong [151102 03:14]:
> Adds support for using a OMAP dual-mode timer with PWM capability
> as a Linux PWM device. The driver controls the timer by using the
> dmtimer API.
>
> Add a platform_data structure for each pwm-omap-dmtimer nodes containing
> the
* Neil Armstrong [151022 02:19]:
> Add dm81xx hwmod data entries for dm816x spinbox support.
Looks good to me, I'll apply patches 3 and 4 in this series into
omap-for-v4.5/soc thanks.
Tony
> Cc: Brian Hutchinson
> Signed-off-by: Neil Armstrong
* Neil Armstrong [151113 01:30]:
> On 11/12/2015 06:47 PM, Tony Lindgren wrote:
> > * Neil Armstrong [151112 06:08]:
> >> In order to fix support for the dm816x platform, add missing bits in
> >> the dm816x dtsi and cleanup OCP.
> >
> > Which
Now the System stall is observed on TI AM437x based board
(am437x-gp-evm) during resuming from System suspend when ARM Global
timer is selected as clocksource device (CPUIdle not enabled) - SysRq are
working,
but nothing else.
The reason of stall is that ARM Global timer loses its contexts
* Suman Anna [151022 10:16]:
> Hi Tony,
>
> On 09/16/2015 06:48 PM, Suman Anna wrote:
> > Hi Tony,
> >
> > The following series removes the legacy platform device creation
> > logic for OMAP IOMMU devices. I will cleanup the legacy support
> > from the OMAP IOMMU driver in a
* Adam Ford [151026 05:53]:
> The schematic expects VAUX1 to be 3.0V attached to the debug port.
> The schematic expects VAUX4 to be 1.8V.
> VAUX4 powers VDDS_CSI2 on processor.
Applying all your six patches into omap-for-v4.4/dt finally thanks.
Tony
--
To unsubscribe
On 11/30, Tero Kristo wrote:
> Errata i810 states that DPLL controller can get stuck while transitioning
> to a power saving state, while its M/N ratio is being re-programmed.
>
> As a workaround, before re-programming the M/N ratio, SW has to ensure
> the DPLL cannot start an idle state
* Uri Mashiach [151124 06:03]:
> --- /dev/null
> +++ b/arch/arm/boot/dts/am335x-cm-t335.dts
...
> + {
> + pinctrl-names = "default";
> + pinctrl-0 = <_pins>;
> +
> + status = "okay";
> +};
> +
FYI, the extra line break at the end of the file causes
Hi Roger,
On Tue, Oct 27, 2015 at 11:37:03AM +0200, Roger Quadros wrote:
> On 26/10/15 23:23, Brian Norris wrote:
> > I'm not too familiar with OMAP platforms, and I might have missed out on
> > prior discussions/context, so please forgive if I'm asking silly or old
> > questions here.
>
> No
On 11/24, Tero Kristo wrote:
> Hi Michael, Stephen,
>
> Here are some TI clock driver fixes for 4.4-rc.
>
> -Tero
>
>
>
> The following changes since commit 8005c49d9aea74d382f474ce11afbbc7d7130bec:
>
> Linux 4.4-rc1
Hi,
Vignesh R writes:
> ti-qspi controller provides mmap port to read data from SPI flashes.
> mmap port is enabled in QSPI_SPI_SWITCH_REG. ctrl module register may
> also need to be accessed for some SoCs. The QSPI_SPI_SETUP_REGx needs to
> be populated with flash specific
* Tony Lindgren [151130 14:03]:
> * Vignesh R [151129 21:16]:
> > Add qspi memory mapped region entries for DRA7xx based SoCs. Also,
> > update the binding documents for the controller to document this change.
> >
> > Acked-by: Rob Herring
>
* Vignesh R [151129 21:16]:
> Add qspi memory mapped region entries for DRA7xx based SoCs. Also,
> update the binding documents for the controller to document this change.
>
> Acked-by: Rob Herring
> Signed-off-by: Vignesh R
...
> ---
Some header files are never included outside of a mach-iop13xx
directory and do not need to be made visible in include/mach,
so let's just move them all down one level.
Signed-off-by: Arnd Bergmann
---
arch/arm/mach-iop13xx/include/mach/pci.h | 57 -
Some header files are never included outside of a mach-davinci
directory and do not need to be made visible in include/mach,
so let's just move them all down one level.
Signed-off-by: Arnd Bergmann
---
arch/arm/mach-davinci/board-da830-evm.c| 2 +-
I could not find any users of this file, past or present, and
it contains only a comment, so let's remove it.
Signed-off-by: Arnd Bergmann
---
arch/arm/mach-netx/include/mach/param.h | 18 --
1 file changed, 18 deletions(-)
delete mode 100644
* Grygorii Strashko [151126 07:24]:
> Enable REGULATOR_FIXED_VOLTAGE for all OMAP2+ platforms
> otherwise system can't boot from SD-card when kernel is
> built for single SoC (for example, with CONFIG_SOC_DRA7XX=y only).
>
> It's also required for almost all TI SoC's
* Arnd Bergmann [151130 15:02]:
> Some header files are never included outside of a mach-omap1
> directory and do not need to be made visible in include/mach,
> so let's just move them all down one level.
>
> Signed-off-by: Arnd Bergmann
> ---
>
Hi,
Adding linux-omap to Cc.
* Philipp Rosenberger [151118 05:20]:
> Hi,
>
> I have seen with pleasure that some support for DM814x was integrated to the
> kernel. But it seems incomplete I get various errors when I try to boot the
> kernel on a DM814x/AM387x based board.
Some header files are never included outside of a mach-omap1
directory and do not need to be made visible in include/mach,
so let's just move them all down one level.
Signed-off-by: Arnd Bergmann
---
arch/arm/mach-omap1/board-ams-delta.c | 2 +-
This file was left over from a cleanup of asm/gpio.h and has
not been used in a while. Let's just remove it now, so the
arch/arm/mach-mvebu/include/ directory can also disappear.
Signed-off-by: Arnd Bergmann
---
arch/arm/mach-mvebu/include/mach/gpio.h | 1 -
1 file changed, 1
Some header files are never included outside of a mach-w90x900
directory and do not need to be made visible in include/mach,
so let's just move them all down one level.
Signed-off-by: Arnd Bergmann
---
arch/arm/mach-w90x900/cpu.c | 4 ++--
Some header files are never included outside of a mach-ks8695
directory and do not need to be made visible in include/mach,
so let's just move them all down one level.
Signed-off-by: Arnd Bergmann
---
arch/arm/mach-ks8695/board-acs5k.c | 2 +-
I've already posted the mach-pxa cleanup along the same lines,
here is another bunch of patches. I'd like to put them into
the next/multiplatform branch in arm-soc.
They come from an old script of mine to look for headers that
are not used by drivers, and I've done thousands of randconfig
builds
Hi Arnd,
On 01/12/15 09:00, Arnd Bergmann wrote:
> Some header files are never included outside of a mach-ks8695
> directory and do not need to be made visible in include/mach,
> so let's just move them all down one level.
>
> Signed-off-by: Arnd Bergmann
Looks good, thanks.
TMP102 works based on conversions done periodically. However, as per
the TMP102 data sheet[1] the first conversion is triggered immediately
after we program the configuration register. The temperature data
registers do not reflect proper data until the first conversion is
complete (in our case
Hello Tony,
Am 30.11.2015 um 22:41 schrieb Tony Lindgren:
* Heiko Schocher [151117 00:25]:
--- /dev/null
+++ b/arch/arm/boot/dts/am335x-shc.dts
+ {
+ compatible = "ti,tps65217";
+ ti,pmic-shutdown-controller;
+
+ regulators {
+ #address-cells =
We currently can't unload omap2430 MUSB platform glue driver module and
this cause issues for fixing the MUSB code further. The reason we can't
remove omap2430 is because it uses the PHY functions and also exports the
omap_musb_mailbox function that some PHY drivers are using.
Let's fix the issue
Hi,
Here are two patches to fix rmmod for musb omap2430. This makes any
further work on this driver a bit easier.
Regards,
Tony
Tony Lindgren (2):
usb: musb: core: Fix handling of the phy notifications
usb: musb: Fix unbalanced pm_runtime_enable
drivers/phy/phy-twl4030-usb.c | 32
When reloading omap2430 kernel module we get a warning about
unbalanced pm_runtime_enable. Let's fix this. Note that we
need to do this after the child musb-core platform_device is
removed because of pm_runtime_irq_safe being set at the child.
Cc: Bin Liu
Cc: Felipe Balbi
On 11/30/2015 08:25 PM, Nishanth Menon wrote:
TMP102 works based on conversions done periodically. However, as per
the TMP102 data sheet[1] the first conversion is triggered immediately
after we program the configuration register. The temperature data
registers do not reflect proper data until
If we reload phy-twl4030-usb, we get a warning about unbalanced
pm_runtime_enable. Let's fix the issue and also fix idling of the
device on unload before we attempt to shut it down.
If we don't properly idle the PHY before shutting it down on removal,
the twl4030 ends up consuming about 62mW of
Otherwise rmmod omap2430; rmmod phy-twl4030-usb; modprobe omap2430
will try to use a non-existing phy and oops:
Unable to handle kernel paging request at virtual address b6f7c1f0
...
[] (devm_usb_get_phy_by_node) from []
(omap2430_musb_init+0x44/0x2b4 [omap2430])
[] (omap2430_musb_init
On 12/01/2015 04:04 AM, Tony Lindgren wrote:
> * Vignesh R [151129 21:16]:
>> Add qspi memory mapped region entries for DRA7xx based SoCs. Also,
>> update the binding documents for the controller to document this change.
>>
>> Acked-by: Rob Herring
>>
Hi,
Here are two fixes for rmmod and PM. These can be merged separately after
the review from the MUSB related changes.
Regards,
Tony
Tony Lindgren (2):
phy: twl4030-usb: Relase usb phy on unload
phy: twl4030-usb: Fix unbalanced pm_runtime_enable on module reload
* Heiko Schocher [151130 21:21]:
> Hello Tony,
>
> Am 30.11.2015 um 22:41 schrieb Tony Lindgren:
> >* Heiko Schocher [151117 00:25]:
> >>--- /dev/null
> >>+++ b/arch/arm/boot/dts/am335x-shc.dts
> >>+ {
> >>+ compatible = "ti,tps65217";
> >>+
Hello Tony,
Am 01.12.2015 um 06:53 schrieb Tony Lindgren:
* Heiko Schocher [151130 21:21]:
Hello Tony,
Am 30.11.2015 um 22:41 schrieb Tony Lindgren:
* Heiko Schocher [151117 00:25]:
--- /dev/null
+++ b/arch/arm/boot/dts/am335x-shc.dts
+ {
+ compatible =
Hi Felipe,
On 12/01/2015 04:05 AM, Balbi, Felipe wrote:
>
> Hi,
>
> Vignesh R writes:
[...]
>> +}
>> +
>> +static int ti_qspi_spi_flash_read(struct spi_device *spi,
>> + struct spi_flash_read_message *msg)
>> +{
>> +struct ti_qspi *qspi =
On 11/27/2015 09:44 PM, Grygorii Strashko wrote:
ARM TWD and Global timer are clocked by PERIPHCLK which is MPU_CLK/2.
But now they are clocked by dpll_mpu_m2_ck == MPU_CLK and, as result.
Timekeeping core misbehaves. For example, execution of command
"sleep 5" will take 10 sec instead of 5.
On 11/30/2015 02:29 AM, santosh.shilim...@oracle.com wrote:
On 11/27/15 11:47 AM, Grygorii Strashko wrote:
Now the System stall is observed on TI AM437x based board
(am437x-gp-evm) during resuming from System suspend when ARM Global
timer is selected as clocksource device (CPUIdle not enabled)
On 11/30/2015 10:25 AM, Tero Kristo wrote:
On 11/27/2015 09:44 PM, Grygorii Strashko wrote:
ARM TWD and Global timer are clocked by PERIPHCLK which is MPU_CLK/2.
But now they are clocked by dpll_mpu_m2_ck == MPU_CLK and, as result.
Timekeeping core misbehaves. For example, execution of command
The drivers are now converted to not use the DMA resource.
Signed-off-by: Peter Ujfalusi
---
arch/arm/mach-davinci/devices-da8xx.c | 49 ---
1 file changed, 49 deletions(-)
diff --git a/arch/arm/mach-davinci/devices-da8xx.c
The driver is converted to not use the DMA resource.
Signed-off-by: Peter Ujfalusi
---
arch/arm/mach-davinci/devices.c | 19 ---
1 file changed, 19 deletions(-)
diff --git a/arch/arm/mach-davinci/devices.c b/arch/arm/mach-davinci/devices.c
index
The driver is converted to not use the DMA resource.
Signed-off-by: Peter Ujfalusi
---
arch/arm/mach-davinci/dm365.c | 8
1 file changed, 8 deletions(-)
diff --git a/arch/arm/mach-davinci/dm365.c b/arch/arm/mach-davinci/dm365.c
index 3dfcf7c9aa20..fe98e5f55634
The driver is converted to not use the DMA resource.
Signed-off-by: Peter Ujfalusi
---
arch/arm/mach-davinci/dm355.c | 8
1 file changed, 8 deletions(-)
diff --git a/arch/arm/mach-davinci/dm355.c b/arch/arm/mach-davinci/dm355.c
index dc8d7ccf69f4..7c6ab2d16e3e
With the new dma_request_chan() the clinet driver does not need to look for
the DMA resource and it does not need to pass filter_fn anymore.
By switching to the new API the davinci_mmc driver can now support deferred
probing against DMA.
Signed-off-by: Peter Ujfalusi
---
Provide the dma_filter_map to edma which will allow us to move the drivers
to the new, simpler dmaengine API and we can remove the DMA resources also
for the devices.
Signed-off-by: Peter Ujfalusi
---
arch/arm/mach-davinci/dm644x.c | 12
1 file changed, 12
With the new dma_request_chan() the clinet driver does not need to look for
the DMA resource and it does not need to pass filter_fn anymore.
By switching to the new API the davinci_mmc driver can now support deferred
probing against DMA.
Signed-off-by: Peter Ujfalusi
---
On 11/30/2015 03:32 PM, Tero Kristo wrote:
> On 11/30/2015 01:53 PM, Grygorii Strashko wrote:
>> On 11/30/2015 10:25 AM, Tero Kristo wrote:
>>> On 11/27/2015 09:44 PM, Grygorii Strashko wrote:
ARM TWD and Global timer are clocked by PERIPHCLK which is MPU_CLK/2.
But now they are clocked
Provide the dma_filter_map to edma which will allow us to move the drivers
to the new, simpler dmaengine API and we can remove the DMA resources also
for the devices.
Signed-off-by: Peter Ujfalusi
---
arch/arm/mach-davinci/dm646x.c | 11 +++
1 file changed, 11
Provide the dma_filter_map to edma which will allow us to move the drivers
to the new, simpler dmaengine API and we can remove the DMA resources also
for the devices.
Signed-off-by: Peter Ujfalusi
---
arch/arm/mach-davinci/dm365.c | 22 ++
1 file
Add support for providing device to filter_fn mapping so client drivers
can switch to use the dma_request_chan() API.
Signed-off-by: Peter Ujfalusi
---
drivers/dma/edma.c | 24
include/linux/platform_data/edma.h | 5 +
2 files
Provide the dma_filter_map to edma which will allow us to move the drivers
to the new, simpler dmaengine API and we can remove the DMA resources also
for the devices.
Signed-off-by: Peter Ujfalusi
---
arch/arm/mach-davinci/devices-da8xx.c | 46
Provide the dma_filter_map to edma which will allow us to move the drivers
to the new, simpler dmaengine API and we can remove the DMA resources also
for the devices.
Signed-off-by: Peter Ujfalusi
---
arch/arm/mach-davinci/dm355.c | 20
1 file
Channel matching with private_candidate() is used in two paths, the error
checking is slightly different in them and they are duplicating code also.
Move the code under dma_get_channel() to provide consistent execution and
going to allow us to reuse this mode of channel lookup later.
Hi,
Changes since RFC v01:
- dma_request_chan(); lost the mask parameter
- The new API does not rely on RESOURCE_DMA, instead the dma_filter_map table
will be used to provide the needed information to the filter function in
legacy mode
- Extended the example patches to convert most of daVinci
The two API function can cover most, if not all current APIs used to
request a channel. With minimal effort dmaengine drivers, platforms and
dmaengine user drivers can be converted to use the two function.
struct dma_chan *dma_request_chan_by_mask(const dma_cap_mask_t *mask);
To request any
Treat as true condition the case when the mask is NULL.
Signed-off-by: Peter Ujfalusi
---
drivers/dma/dmaengine.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/dma/dmaengine.c b/drivers/dma/dmaengine.c
index daf54a39bcc7..52c3eee48e2e 100644
---
On 11/30/2015 03:49 PM, Grygorii Strashko wrote:
On 11/30/2015 03:32 PM, Tero Kristo wrote:
On 11/30/2015 01:53 PM, Grygorii Strashko wrote:
On 11/30/2015 10:25 AM, Tero Kristo wrote:
On 11/27/2015 09:44 PM, Grygorii Strashko wrote:
ARM TWD and Global timer are clocked by PERIPHCLK which is
On Monday 30 November 2015 15:45:33 Peter Ujfalusi wrote:
> const char *name);
> struct dma_chan *dma_request_slave_channel(struct device *dev, const char
> *name);
> +
> +struct dma_chan *dma_request_chan(struct device *dev, const char *name);
>
On Monday 30 November 2015 15:45:34 Peter Ujfalusi wrote:
> @@ -2428,6 +2436,22 @@ bool edma_filter_fn(struct dma_chan *chan, void *param)
> }
> EXPORT_SYMBOL(edma_filter_fn);
>
> +static bool edma_filter_for_map(struct dma_chan *chan, void *param)
> +{
> + bool match = false;
> +
> +
On Fri, Nov 20, 2015 at 2:35 PM, Grygorii Strashko
wrote:
> Originally OMAP MPUIO GPIO irqchip was implemented using Generic irq
> chip, but after set of reworks Generic irq chip code was replaced by
> common OMAP GPIO implementation and finally removed by
> commit
On 11/30/2015 07:29 AM, Dmitry Lifshitz wrote:
> On 11/29/2015 07:06 PM, Nishanth Menon wrote:
>> On 11/29/2015 06:10 AM, Dmitry Lifshitz wrote:
[...]
>>
>> You might want to ask your TI support contact for IODelay
>> recommendations. TRM mentions that pinmuxing must be performed under IO
>>
1 - 100 of 116 matches
Mail list logo