On Tue, Feb 26, 2013 at 23:00:31, Hunter, Jon wrote:
> The GPMC has various different configuration options such as bus-width,
> synchronous or asychronous mode selection, burst mode options etc.
> Currently, there is no common function for configuring these options and
> various devices set these
On Wed, Feb 27, 2013 at 09:36:03PM +, Arnd Bergmann wrote:
> On Wednesday 27 February 2013, Vinod Koul wrote:
> > Yes we had agreed that I will send it.
> >
> > I have applied this one now, and will send second PULL request to Linus
> > soon.
> >
> > Arnd,
> > The second patch of dw_dmac you
On Wed, Feb 15, 2012 at 5:04 PM, Benoit Cousson wrote:
> @@ -52,7 +55,8 @@ struct gpio_bank {
> struct list_head node;
> void __iomem *base;
> u16 irq;
> - u16 virtual_irq_start;
> + int irq_base;
> + struct irq_domain *domain;
This seems wrong. IRQ doma
On 02/26/2013 09:57 PM, Javier Martinez Canillas wrote:
[snip]
> Something like that would definitely solve the GPIO request issue but
> we still have the issue that the current OMAP GPIO controller binding
> does not support #interrupt-cells = <2>.
>
> So, we can't pass the trigger type and le
On Wednesday 27 February 2013, Vinod Koul wrote:
> Yes we had agreed that I will send it.
>
> I have applied this one now, and will send second PULL request to Linus soon.
>
> Arnd,
> The second patch of dw_dmac you wnated to send me fails to apply for me. Can
> you
> either rebase or send with
On 02/26/2013 09:47 PM, Javier Martinez Canillas wrote:
> On Wed, Feb 27, 2013 at 12:08 AM, Jon Hunter wrote:
>>
>> On 02/26/2013 04:01 AM, Javier Martinez Canillas wrote:
>>
>> [snip]
>>
>>> I was wondering if the level/edge settings for gpios is working on OMAP.
>>>
>>> I'm adding DT support fo
On Wed, Feb 27, 2013 at 6:50 PM, Stephen Warren wrote:
> On 02/26/2013 08:57 PM, Javier Martinez Canillas wrote:
>> On Wed, Feb 27, 2013 at 2:07 AM, Jon Hunter wrote:
>>>
>>> On 02/26/2013 06:13 PM, Stephen Warren wrote:
On 02/26/2013 04:45 PM, Jon Hunter wrote:
> ...
> One issue I see i
On Wed, Feb 27, 2013 at 6:47 PM, Stephen Warren wrote:
> On 02/26/2013 08:33 PM, Javier Martinez Canillas wrote:
> ...
>> Yes, I realized that requesting the gpio was necessary so what I did
>> is to use the "regulator-fixed" optional property "gpio" and define
>> the GPIO used as an IRQ in a regu
Quoting Tero Kristo (2013-02-27 00:44:19)
> Hi Paul and Mike,
>
> It looks like we need to start putting more effort into this clock data
> move now, as this is starting to hinder us on several fronts.
> Unfortunately I still can't personally participate in this work myself
> as I am now allocated
On 02/26/2013 08:57 PM, Javier Martinez Canillas wrote:
> On Wed, Feb 27, 2013 at 2:07 AM, Jon Hunter wrote:
>>
>> On 02/26/2013 06:13 PM, Stephen Warren wrote:
>>> On 02/26/2013 04:45 PM, Jon Hunter wrote:
...
One issue I see is that by not calling gpio_request, then potentially
you cou
On 02/26/2013 08:33 PM, Javier Martinez Canillas wrote:
...
> Yes, I realized that requesting the gpio was necessary so what I did
> is to use the "regulator-fixed" optional property "gpio" and define
> the GPIO used as an IRQ in a regulator used by the SMSC chip. So, I
> have this on my board DT:
I've specified an I2C bus and all 6 UARTs in the dts file for my custom cpu
board, as follows:-
ocp {
uart1: serial@44e09000 {
pinctrl-names = "default";
status = "okay";
};
uart2: serial@4802
The OMAP4 Blaze Tablet is TI OMAP4 processor-based
development platform in a tablet formfactor.
The platform contains many of the features found in
present-day handsets (such as audio, video, wireless
functions and user interfaces) and in addition
contains features for software development and test
Hi,
This patch is a second attempt to add basic support of OMAP4 Blaze Tablet
software development platform - in this case using only Device Tree.
Additional information about this platform can be found here:
http://www.svtronics.com/omap?product_id=15
Ruslan Bilovol (1):
ARM: DTS: OMAP4: Add
On 27-02-2013 04:44, Tero Kristo wrote:
Hi Paul and Mike,
It looks like we need to start putting more effort into this clock data
move now, as this is starting to hinder us on several fronts.
Unfortunately I still can't personally participate in this work myself
as I am now allocated to some hwm
Mike,
On 27-02-2013 01:35, Mike Turquette wrote:
Quoting Eduardo Valentin (2013-02-26 14:53:38)
This patch changes the clock management code to also update
the clock prepare counter, this way we won't skip the enable/disable
operation due to prepare dependencies.
Signed-off-by: Eduardo Valenti
Hi Felipe,
On Wed, Feb 27, 2013 at 1:36 PM, Felipe Balbi wrote:
> Hi,
>
> sorry for the delay
>
That's alright ;-)
> On Mon, Jan 28, 2013 at 07:06:56PM +0530, Vivek Gautam wrote:
>> Hi Felipe,
>>
>>
>> On Mon, Jan 28, 2013 at 5:15 PM, Felipe Balbi wrote:
>> > On Mon, Jan 28, 2013 at 05:12:26P
Hi Paul and Mike,
It looks like we need to start putting more effort into this clock data
move now, as this is starting to hinder us on several fronts.
Unfortunately I still can't personally participate in this work myself
as I am now allocated to some hwmod related work, but Eduardo should
have p
Hi,
sorry for the delay
On Mon, Jan 28, 2013 at 07:06:56PM +0530, Vivek Gautam wrote:
> Hi Felipe,
>
>
> On Mon, Jan 28, 2013 at 5:15 PM, Felipe Balbi wrote:
> > On Mon, Jan 28, 2013 at 05:12:26PM +0530, Vivek Gautam wrote:
> >> The current code in the dwc3 probe effectively disables runtime p
19 matches
Mail list logo
