On 2014-07-15 20:21:21 [+], Paul Walmsley wrote:
> Hi Sebastian,
Hi Paul,
> > Acked-by: Sebastian Andrzej Siewior
> >
> > This is basically what Tony hasked me to do: No IRQ numbers & iomem.
>
> Sorry - I'm a bit confused - Sebastian, did you test this one? If so, is
> it okay to add a Te
* Suman Anna [140715 09:59]:
> Hi Tony,
>
> On 07/15/2014 08:30 AM, Tony Lindgren wrote:
> > * Suman Anna [140711 14:47]:
> >> Add the hwmod data for the 13 instances of the system mailbox
> >> IP in DRA7 SoC. The patch is needed for performing a soft-reset
> >> while configuring the respective
Hi Joachim,
is there some policy for only having nodes for existing drivers in DT files?
If I understand the device tree concept correctly, it should not describe
drivers
(and hence nothing about the state of them being mainlined), but it should
statically
describe the given hardware in a way th
On 07/10/2014 04:30 PM, Olivier Galibert wrote:
> On Wed, Jul 9, 2014 at 7:49 PM, Sebastian Andrzej Siewior
> wrote:
>> + * The lock assumption made here is none because runtime-pm suspend/resume
>> + * callbacks should not be invoked there is any operation performed on the
>> port.
>
> I think
On 07/10/2014 08:28 AM, Tony Lindgren wrote:
>> --- a/drivers/tty/serial/8250/8250_core.c
>> +++ b/drivers/tty/serial/8250/8250_core.c
>> @@ -571,7 +573,17 @@ static void serial8250_set_sleep(struct uart_8250_port
>> *p, int sleep)
>> serial_out(p, UART_EFR, 0);
>>
* Dave Gerlach [140715 19:46]:
> Tony,
> On 07/15/2014 01:38 AM, Tony Lindgren wrote:
> >* Dave Gerlach [140714 10:44]:
> >>On 07/14/2014 06:12 AM, Tony Lindgren wrote:
> >>>* Dave Gerlach [140710 19:59]:
> OMAP4 and AM33XX share the same EMIF controller IP. Although there
> are signific
This series add seperate ocp interface lists that are specific to dra74x
and dra72x, and moving USB OTG SS4 to dra74x only since its not present
in dra72x. Without this USB OTG SS4 hwmod gives an abort on dra72x.
Adding support for soc_is_dra74x() and soc_is_dra72x() in order to differentiate
betw
From: Rajendra Nayak
To deal with IPs which are specific to dra74x and dra72x, maintain seperate
ocp interface lists, while keeping the common list for all common IPs.
Move USB OTG SS4 to dra74x only list since its unavailable in
dra72x and is giving an abort during boot. The dra72x only list
is
From: Rajendra Nayak
Use the corresponding compatibles to identify the devices.
Signed-off-by: Rajendra Nayak
Signed-off-by: Lokesh Vutla
---
arch/arm/mach-omap2/soc.h |7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/mach-omap2/soc.h b/arch/arm/mach-omap2/soc.h
index 01c
* Kristina Martšenko [140715 16:33]:
> It was added to support DSP Bridge. Since DSP Bridge was removed, and
> nothing else is using the platform device, remove it too.
>
> Signed-off-by: Kristina Martšenko
> Cc: Omar Ramirez Luna
> Cc: Suman Anna
> Cc: Felipe Contreras
This should not affec
* Kristina Martšenko [140716 02:33]:
> The driver has been broken and disabled for several kernel versions now.
> It doesn't have a maintainer anymore, and most of the people who've
> worked on it have moved on. There's also still a long list of issues in
> the TODO file before it can be moved out
On 22 May 04:31 PM, Tony Lindgren wrote:
> * Christoph Fritz [140522 16:07]:
> > --- a/drivers/pinctrl/pinctrl-single.c
> > +++ b/drivers/pinctrl/pinctrl-single.c
> > @@ -2069,7 +2069,22 @@ static struct platform_driver pcs_driver = {
> > #endif
> > };
> >
> > +#ifdef CONFIG_USE_OF
> > +static
On 07/11/2014 08:41 AM, Tony Lindgren wrote:
>> I tried this with am335x-evm, dra7-evm and beaglebone (omap5-uevm and
>> am335x-evmsk didn't want to boot a kernel and omap4-blaze didn't even
>> want to show MLO/U-boot) with the same result.
>
> None of these SoCs support off-idle with mainline ker
If the client (audio) does not request interrupts for every period we can
disable them.
With updated audio driver stack we can play audio w/o the need to process
any edma interrupts.
Signed-off-by: Peter Ujfalusi
---
drivers/dma/edma.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Hi,
After this series clients can ask to not receive notifications after each
period.
In this case we can disable the completion interrupt since the position
reporting
does not rely on it for cyclic mode.
Patchset for ASoC part has been sent which allows users space to take adventage
of SNDRV_PC
The edma can report accurate DMA position so update the residue_granularity
to DMA_RESIDUE_GRANULARITY_BURST.
Signed-off-by: Peter Ujfalusi
---
drivers/dma/edma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/edma.c b/drivers/dma/edma.c
index fe55f78ea137..d5017
* Sebastian Andrzej Siewior [140716 05:14]:
> On 07/11/2014 08:41 AM, Tony Lindgren wrote:
> >
> > If the RX pin does not wake it up, you need to configure the
> > pinctrl-single entry for it, and configure that pin as a wake-up
> > interrupt. See the interrupts-extended entry in omap3-beagle-xm.
* Ezequiel Garcia [140716 04:48]:
> On 22 May 04:31 PM, Tony Lindgren wrote:
> > * Christoph Fritz [140522 16:07]:
> > > --- a/drivers/pinctrl/pinctrl-single.c
> > > +++ b/drivers/pinctrl/pinctrl-single.c
> > > @@ -2069,7 +2069,22 @@ static struct platform_driver pcs_driver = {
> > > #endif
> >
The following changes since commit 7171511eaec5bf23fb06078f59784a3a0626b38f:
Linux 3.16-rc1 (2014-06-15 17:45:28 -1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap
tags/omap-for-v3.17/dt-part1
for you to fetch changes up to 3c9464
On Wednesday 16 July 2014 06:02 PM, Tony Lindgren wrote:
> * Sebastian Andrzej Siewior [140716 05:14]:
>> On 07/11/2014 08:41 AM, Tony Lindgren wrote:
>>>
>>> If the RX pin does not wake it up, you need to configure the
>>> pinctrl-single entry for it, and configure that pin as a wake-up
>>> inter
On 16 Jul 05:36 AM, Tony Lindgren wrote:
> * Ezequiel Garcia [140716 04:48]:
> > On 22 May 04:31 PM, Tony Lindgren wrote:
> > > * Christoph Fritz [140522 16:07]:
> > > > --- a/drivers/pinctrl/pinctrl-single.c
> > > > +++ b/drivers/pinctrl/pinctrl-single.c
> > > > @@ -2069,7 +2069,22 @@ static str
There is no access to access a struct uart_8250_port for a specific
line. This is only required outside of the 8250/uart callbacks like for
devices' suspend & remove callbacks. For those the 8250-core provides
wrapper like serial8250_unregister_port() which passes the struct
to the proper function
This patch provides a 8250-core based UART driver for the internal OMAP
UART. The longterm goal is to provide the same functionality as the
current OMAP uart driver and hopefully DMA support which could borrowed
from the 8250-core.
It has been only tested as console UART on am335x-evm and dra7-evm
The omap uart provides support for HW assisted flow control. What is
missing is the support to throttle / unthrottle callbacks which are used
by the omap-serial driver at the moment.
This patch adds the callbacks. It should be safe to add them since they
are only invovked from the serial_core (uart
While comparing the OMAP-serial and the 8250 part of this I noticed that
the the latter does not use runtime-pm. Here are the pieces. It is
basically a get before first register access and a last_busy + put after
last access.
If I understand this correct, it should do nothing as long as
pm_runtime_
I converted most of the omap-serial over to the 8250-core based code where it
once was forked from. I dropped the rs485 support for now.
The runtime-pm does not crash any machines because none of them shutdown the
IP core and/or enter deep idle where it would metter.
Sebastian
--
To unsubscribe f
The OMAP version of the 8250 can actually use 1:1 serial8250_startup().
However it needs to be extended by a wakeup irq which should to be
requested & enabled at ->startup() time and disabled at ->shutdown() time.
v2…v3: properly copy callbacks
v1…v2: add shutdown callback
Acked-by: Alan Cox
Sig
Hi,
On Wed, Jul 16, 2014 at 04:45:02PM +0200, Sebastian Andrzej Siewior wrote:
> @@ -1280,6 +1285,7 @@ static void serial8250_stop_tx(struct uart_port *port)
> struct uart_8250_port *up =
> container_of(port, struct uart_8250_port, port);
>
> + pm_runtime_get_sync(port->d
On 07/15/2014 06:30 PM, Kristina Martšenko wrote:
> The driver has been broken and disabled for several kernel versions now.
> It doesn't have a maintainer anymore, and most of the people who've
> worked on it have moved on. There's also still a long list of issues in
> the TODO file before it can
On 07/15/2014 06:30 PM, Kristina Martšenko wrote:
> It was added to support DSP Bridge. Since DSP Bridge was removed, and
> nothing else is using the platform device, remove it too.
>
> Signed-off-by: Kristina Martšenko
> Cc: Omar Ramirez Luna
> Cc: Suman Anna
> Cc: Felipe Contreras
Acked-by:
On 07/16/2014 05:16 PM, Felipe Balbi wrote:
> Hi,
Hi Felipe,
> On Wed, Jul 16, 2014 at 04:45:02PM +0200, Sebastian Andrzej Siewior
> wrote:
>> @@ -1280,6 +1285,7 @@ static void serial8250_stop_tx(struct
>> uart_port *port) struct uart_8250_port *up = container_of(port,
>> struct uart_8250_port, p
Hi,
On Wed, Jul 16, 2014 at 05:54:56PM +0200, Sebastian Andrzej Siewior wrote:
> On 07/16/2014 05:16 PM, Felipe Balbi wrote:
> > Hi,
>
> Hi Felipe,
>
> > On Wed, Jul 16, 2014 at 04:45:02PM +0200, Sebastian Andrzej Siewior
> > wrote:
> >> @@ -1280,6 +1285,7 @@ static void serial8250_stop_tx(struc
Hi folks,
I was trying to use Kernel Function Profiler to figure out why my
driver's IRQ handler is taking so much CPU time but to my surprise,
whenever I try to trace anything, I get a "Unable to handle kernel
paging request at virtual address " error.
Is anybody else seen that or did I scre
On Wed, 16 Jul 2014 11:23:28 -0500
Felipe Balbi wrote:
> Hi folks,
>
> I was trying to use Kernel Function Profiler to figure out why my
> driver's IRQ handler is taking so much CPU time but to my surprise,
> whenever I try to trace anything, I get a "Unable to handle kernel
> paging request at
On 07/16/2014 06:06 PM, Felipe Balbi wrote:
>>> well, other than in probe and other functions which need to
>>> make sure clocks are on, but it seems unnecessary to
>>> enable/disable in every function.
>>
>> What do you have in mind? Do you plan to let the uart on while
>> the minicom is attache
Hi again,
On Wed, Jul 16, 2014 at 11:41:41AM -0500, Felipe Balbi wrote:
> Hi,
>
> On Wed, Jul 16, 2014 at 12:29:21PM -0400, Steven Rostedt wrote:
> > On Wed, 16 Jul 2014 11:23:28 -0500
> > Felipe Balbi wrote:
> >
> > > Hi folks,
> > >
> > > I was trying to use Kernel Function Profiler to figur
On Wed, Jul 16, 2014 at 06:40:01PM +0200, Sebastian Andrzej Siewior wrote:
> On 07/16/2014 06:06 PM, Felipe Balbi wrote:
>
> >>> well, other than in probe and other functions which need to
> >>> make sure clocks are on, but it seems unnecessary to
> >>> enable/disable in every function.
> >>
> >>
On Wed, 16 Jul 2014 11:41:42 -0500
Felipe Balbi wrote:
> .config attached. It's actually an ARM platform, I can help out with
> testing anything you need.
In that case, can you see if it works under my repo?
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
branch: ftrace/c
On Thu, Jul 10, 2014 at 01:46:20PM +0200, Wolfram Sang wrote:
> Some drivers were flagged to remove class based instantiation soon to improve
> boot-up time. Originally, I was planning for a longer deprecation time so
> users
> could switch over to some other kind of instantiation. However, the de
On Wed, Jul 16, 2014 at 01:24:13PM -0400, Steven Rostedt wrote:
> On Wed, 16 Jul 2014 11:41:42 -0500
> Felipe Balbi wrote:
>
>
> > .config attached. It's actually an ARM platform, I can help out with
> > testing anything you need.
>
> In that case, can you see if it works under my repo?
>
> gi
Hi,
On Wed, Jul 16, 2014 at 01:29:44PM -0500, Felipe Balbi wrote:
> On Wed, Jul 16, 2014 at 01:24:13PM -0400, Steven Rostedt wrote:
> > On Wed, 16 Jul 2014 11:41:42 -0500
> > Felipe Balbi wrote:
> >
> >
> > > .config attached. It's actually an ARM platform, I can help out with
> > > testing any
On Wed, 16 Jul 2014 13:41:52 -0500
Felipe Balbi wrote:
> Hi,
>
> On Wed, Jul 16, 2014 at 01:29:44PM -0500, Felipe Balbi wrote:
> > On Wed, Jul 16, 2014 at 01:24:13PM -0400, Steven Rostedt wrote:
> > > On Wed, 16 Jul 2014 11:41:42 -0500
> > > Felipe Balbi wrote:
> > >
> > >
> > > > .config att
On Wed, 16 Jul 2014, Sebastian Andrzej Siewior wrote:
> On 2014-07-15 20:21:21 [+], Paul Walmsley wrote:
>
> > > Acked-by: Sebastian Andrzej Siewior
> > >
> > > This is basically what Tony hasked me to do: No IRQ numbers & iomem.
> >
> > Sorry - I'm a bit confused - Sebastian, did you test
On Wed, Jul 16, 2014 at 02:54:42PM -0400, Steven Rostedt wrote:
> On Wed, 16 Jul 2014 13:41:52 -0500
> Felipe Balbi wrote:
>
> > Hi,
> >
> > On Wed, Jul 16, 2014 at 01:29:44PM -0500, Felipe Balbi wrote:
> > > On Wed, Jul 16, 2014 at 01:24:13PM -0400, Steven Rostedt wrote:
> > > > On Wed, 16 Jul
On 07/15/2014 01:48 AM, Tony Lindgren wrote:
> * Dave Gerlach [140714 10:44]:
>> Santosh, Tony,
>>
>> On 07/14/2014 09:37 AM, Santosh Shilimkar wrote:
>>> On Monday 14 July 2014 07:15 AM, Tony Lindgren wrote:
* Dave Gerlach [140710 19:59]:
> From: Vaibhav Bedia
>
> OMAP timer co
If I may nit-pick here for a minute...
On 11 July 2014 15:04, Suman Anna wrote:
> Logic has been added to the OMAP2+ mailbox code to parse the
> mailbox dt nodes and construct the different sub-mailboxes
> associated with the instance. The DT representation of the
> sub-mailbox devices is differe
Hi Markus,
On 07/16/2014 03:50 PM, Markus Mayer wrote:
> If I may nit-pick here for a minute...
>
> On 11 July 2014 15:04, Suman Anna wrote:
>> Logic has been added to the OMAP2+ mailbox code to parse the
>> mailbox dt nodes and construct the different sub-mailboxes
>> associated with the instan
47 matches
Mail list logo
