On Monday 14 December 2015 10:19:40 Thierry Reding wrote:
> > PCIe host driver that use fixup (DECLARE_PCI_FIXUP_*) can't use tristate.
> > Fixup region is in kernel region and this region if not updated when
> > loading a module.
>
> Interesting, I hadn't thought about that. I suppose this means
Hi,
Changes since v1:
- Added Reviewed-by from Andy for patch 1-2, I decided to not add the
reviewed-by
to patch 3 due to the changes since v1
- patch for omap-dma to support passing the filter setup to the core
- dma_request_slave_channel_reason() remeved and it is now defines as
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 find_candidate() to provide consistent execution and
going to allow us to reuse this mode of channel lookup later.
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/omap-dma.c | 4
include/linux/omap-dma.h | 6 ++
2 files changed, 10 insertions(+)
diff --git
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 | 4
include/linux/platform_data/edma.h | 7 +++
2 files changed, 11
On Mon, Dec 14, 2015 at 04:33:51PM +0800, Ley Foon Tan wrote:
> On Mon, Dec 14, 2015 at 4:24 PM, Thierry Reding
> wrote:
> > On Mon, Dec 14, 2015 at 09:19:30AM +0100, Geert Uytterhoeven wrote:
> >> Hi Paul,
> >>
> >> On Sun, Dec 13, 2015 at 2:41 AM, Paul Gortmaker
> >>
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
If mask is NULL skip the mask matching against the DMA device capabilities.
Signed-off-by: Peter Ujfalusi
Reviewed-by: Andy Shevchenko
---
drivers/dma/dmaengine.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Monday 14 December 2015 13:22:15 Peter Ujfalusi wrote:
>
> Changes since v1:
> - Added Reviewed-by from Andy for patch 1-2, I decided to not add the
> reviewed-by
> to patch 3 due to the changes since v1
> - patch for omap-dma to support passing the filter setup to the core
> -
On Thu, Dec 10, 2015 at 06:26:32PM -0800, Tony Lindgren wrote:
> +- compatible : shall be one of "ti,dm814-adpll-s-clock" or
> + "ti,dm814-adpll-j-clock" depending on the type of the ADPLL
There's still a j -> lj you missed.
Also, since the device series almost always referred to as dm814x, any
Do not use the legacy and deprecated omap-dma interface for setting up the
memcpy.
Signed-off-by: Peter Ujfalusi
---
Hi,
this patch depends on the dma setup simplification patch:
https://www.mail-archive.com/linux-omap@vger.kernel.org/msg122375.html
We could try to
Hi Peter,
[auto build test WARNING on slave-dma/next]
[also build test WARNING on v4.4-rc5 next-20151214]
url:
https://github.com/0day-ci/linux/commits/Peter-Ujfalusi/dmaengine-core-Skip-mask-matching-when-it-is-not-provided-to-private_candidate/20151214-192521
base: https://git.kernel.org
On Thu, Dec 10, 2015 at 11:31 PM, Tony Lindgren wrote:
>> >
>> > I think we need to add ourselves to MAINTAINERS for this driver,
>> > otherwise we'll keep on missing emails.
>>
>> Good idea! Patches accepted.
>
> How about this one below?
Patch applied for fixes!
Yours,
* Adam Ford [151212 19:08]:
Please add a description here like "The binding for wl12xx bluetooth
got removed by commit xyz and until we have a better binding we need
to use the platform data to initialize bluetooth".
Regards,
Tony
--
To unsubscribe from this list: send the
Hi,
randomly hit this issue from 4.4-rc1:
[ 35.926605] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 35.932373] (detected by 0, t=2602 jiffies, g=519, c=518, q=38)
[ 35.938659] All QSes seen, last rcu_sched kthread activity 2602
(-26407--29009), jiffies_till_next_fqs=1, root ->qsmask
We have 4 functions containing almost identical DMA setup code. Create one
function which can set up the DMA for both read and write and use this in
place for the setup code in the driver.
The new function will use wait_for_completion_timeout() and it will figure
out the best data_type to be used
Now ARM TWD timer can be enabled for AM437x devices since all prerequisite
patches have been merged already [1] [2].
But before finally enable ARM TWD timer for UP AM437x devices -
the Broadcast event source and infrustructure need to be enabled properly.
Otherwise CPUIdle will be broken.
[1]
System will misbehave in the following case:
- AM43XX only build (UP);
- CONFIG_CPU_IDLE=y
- ARM TWD timer enabled and selected as clockevent device.
In the above case, It's expected that broadcast timer will be used as
backup timer when CPUIdle will put MPU in low power states where ARM
TWD will
From: Felipe Balbi
Make sure to tell the kernel that AM437x devices have ARM TWD timer.
Signed-off-by: Felipe Balbi
[grygorii.stras...@ti.com: drop ARM Global timer selection, because
it's incompatible with PM (cpuidle/cpufreq). So, it's unsafe to enable
it
* Matthijs van Duin [151214 01:16]:
> On Thu, Dec 10, 2015 at 06:26:32PM -0800, Tony Lindgren wrote:
> > +- compatible : shall be one of "ti,dm814-adpll-s-clock" or
> > + "ti,dm814-adpll-j-clock" depending on the type of the ADPLL
>
> There's still a j -> lj you
On Sat, 12 Dec 2015 16:44:19 +0100
Markus Brunner wrote:
> On Wednesday 09 December 2015 22:31:15 David Rivshin wrote:
> ...
> > This patch was originally developed in parallel with 1f71e8c96fc6 to
> > accomplish the same goal. When I replaced this patch
On Sat, Dec 12, 2015 at 03:41:31PM +0100, Arnd Bergmann wrote:
> On Friday 11 December 2015 17:10:56 Brian Norris wrote:
> > drivers/mtd/nand/omap_elm.c:417 elm_probe() error: '%pr' expects argument
> > of type struct resource *, but argument 3 has type 'struct resource**'
> > [smatch]
>
> Ah,
Hi Paul,
On Sun, Dec 13, 2015 at 2:41 AM, Paul Gortmaker
wrote:
> This series of commits is a slice of a larger project to ensure
> people don't have dead code for module removal in non-modular
> drivers. Overall there was roughly 5k lines of dead code in the
>
On Mon, Dec 14, 2015 at 09:19:30AM +0100, Geert Uytterhoeven wrote:
> Hi Paul,
>
> On Sun, Dec 13, 2015 at 2:41 AM, Paul Gortmaker
> wrote:
> > This series of commits is a slice of a larger project to ensure
> > people don't have dead code for module removal in
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
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
Reviewed-by: Arnd Bergmann
---
drivers/dma/edma.c | 4
On 12/14/2015 01:22 PM, Peter Ujfalusi wrote:
> /**
> + * struct dma_slave_map - associates slave device and it's slave channel with
> + * parameter to be used by a filter function
> + * @devname: name of the device
> + * @slave: slave channel name
> + * @param: opaque parameter to pass to
Hi,
Changes since v2:
- in patch 3 some tabs got replaced by spaces, now they are fixed
- added Reviewed-by from Arnd
Changes since v1:
- Added Reviewed-by from Andy for patch 1-2, I decided to not add the
reviewed-by
to patch 3 due to the changes since v1
- patch for omap-dma to support
If mask is NULL skip the mask matching against the DMA device capabilities.
Signed-off-by: Peter Ujfalusi
Reviewed-by: Andy Shevchenko
Reviewed-by: Arnd Bergmann
---
drivers/dma/dmaengine.c | 2 +-
1 file changed, 1
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
Reviewed-by: Arnd Bergmann
---
drivers/dma/omap-dma.c | 4
include/linux/omap-dma.h | 6 ++
2
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 find_candidate() to provide consistent execution and
going to allow us to reuse this mode of channel lookup later.
On Mon, Dec 14, 2015 at 4:24 PM, Thierry Reding
wrote:
> On Mon, Dec 14, 2015 at 09:19:30AM +0100, Geert Uytterhoeven wrote:
>> Hi Paul,
>>
>> On Sun, Dec 13, 2015 at 2:41 AM, Paul Gortmaker
>> wrote:
>> > This series of commits is a slice
On 14.12.2015 09:24, Thierry Reding wrote:
> On Mon, Dec 14, 2015 at 09:19:30AM +0100, Geert Uytterhoeven wrote:
>> Hi Paul,
>>
>> On Sun, Dec 13, 2015 at 2:41 AM, Paul Gortmaker
>> wrote:
>>> This series of commits is a slice of a larger project to ensure
>>> people
33 matches
Mail list logo