On Mon, May 07, 2012 at 16:14:42, Shilimkar, Santosh wrote:
> On Mon, May 7, 2012 at 4:02 PM, Cousson, Benoit wrote:
> > Hi Paul,
> >
> >
> > On 5/2/2012 11:09 AM, Paul Walmsley wrote:
> >>
> >> On Fri, 27 Apr 2012, Hiremath, Vaibhav wrote:
> >>
> >> So first we have to decide whether the CONFIG_
On Mon, May 7, 2012 at 4:02 PM, Cousson, Benoit wrote:
> Hi Paul,
>
>
> On 5/2/2012 11:09 AM, Paul Walmsley wrote:
>>
>> On Fri, 27 Apr 2012, Hiremath, Vaibhav wrote:
>>
>>> I will be waiting for your comment and conformation on, which family
>>> AM33xx
>>> device should fall in? Please refer to t
Hi Paul,
On 5/2/2012 11:09 AM, Paul Walmsley wrote:
On Fri, 27 Apr 2012, Hiremath, Vaibhav wrote:
I will be waiting for your comment and conformation on, which family AM33xx
device should fall in? Please refer to the mail-chain -
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg67275
On Wed, May 02, 2012 at 15:00:28, Paul Walmsley wrote:
>
> Hello Vaibhav,
>
> I've reworked these patches somewhat to separate the PRM and CM changes
> into their own patches. Also, the omap_hwmod changes have been separated
> and moved into a different series, as have the clock tree changes.
On Wed, May 02, 2012 at 15:00:28, Paul Walmsley wrote:
>
> Hello Vaibhav,
>
> I've reworked these patches somewhat to separate the PRM and CM changes
> into their own patches. Also, the omap_hwmod changes have been separated
> and moved into a different series, as have the clock tree changes.
Hello Vaibhav,
I've reworked these patches somewhat to separate the PRM and CM changes
into their own patches. Also, the omap_hwmod changes have been separated
and moved into a different series, as have the clock tree changes.
So now, pending for 3.5, there are the SCM, voltagedomain, PRM, CM
On Fri, 27 Apr 2012, Hiremath, Vaibhav wrote:
> I will be waiting for your comment and conformation on, which family AM33xx
> device should fall in? Please refer to the mail-chain -
>
> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg67275.html
This decision turns out to be pretty imp
On Fri, Apr 27, 2012 at 00:35:25, Tony Lindgren wrote:
> * Hiremath, Vaibhav [120426 11:52]:
> >
> > Yes, they were accepted and were also available under linux-omap/soc2
> > branch
> > for quite some time.
>
> Hmm sorry if I've dropped them accidentally. I tend to drop the branches
> after ea
* Hiremath, Vaibhav [120426 11:52]:
>
> Yes, they were accepted and were also available under linux-omap/soc2 branch
> for quite some time.
Hmm sorry if I've dropped them accidentally. I tend to drop the branches
after each merge window and purge my linux-omap mailbox too.
Regards,
Tony
--
To
On Fri, Apr 27, 2012 at 00:13:13, Tony Lindgren wrote:
> * Hiremath, Vaibhav [120423 11:31]:
> > On Thu, Apr 19, 2012 at 04:48:37, Tony Lindgren wrote:
> > > * Hiremath, Vaibhav [120413 03:39]:
> > > > On Thu, Apr 12, 2012 at 13:56:06, Paul Walmsley wrote:
> > > >
> > > > Yes, we are using am351
* Hiremath, Vaibhav [120423 11:31]:
> On Thu, Apr 19, 2012 at 04:48:37, Tony Lindgren wrote:
> > * Hiremath, Vaibhav [120413 03:39]:
> > > On Thu, Apr 12, 2012 at 13:56:06, Paul Walmsley wrote:
> > >
> > > Yes, we are using am3517evm file for AM33XX MACHINE_INIT definition here.
> > > These patc
On Fri, Mar 30, 2012 at 21:33:51, Hiremath, Vaibhav wrote:
> After some healthy discussion, now we have come to the conclusion and
> decided to handle AM33XX PRM/CM part separately; as AM33XX-PRCM module is
> different than OMAP3 and OMAP4 architecture.
>
> The difference becomes very interesting/
On Thu, Apr 19, 2012 at 04:48:37, Tony Lindgren wrote:
> * Hiremath, Vaibhav [120413 03:39]:
> > On Thu, Apr 12, 2012 at 13:56:06, Paul Walmsley wrote:
> >
> > Yes, we are using am3517evm file for AM33XX MACHINE_INIT definition here.
> > These patches have been reviewed and accepted in the list,
* Paul Walmsley [120413 03:46]:
> Hi Vaibhav,
>
> On Fri, 13 Apr 2012, Hiremath, Vaibhav wrote:
>
> > Yes, we are using am3517evm file for AM33XX MACHINE_INIT definition here.
> > These patches have been reviewed and accepted in the list, only thing is
> > they couldn't make it to upstream durin
* Hiremath, Vaibhav [120413 03:39]:
> On Thu, Apr 12, 2012 at 13:56:06, Paul Walmsley wrote:
>
> Yes, we are using am3517evm file for AM33XX MACHINE_INIT definition here.
> These patches have been reviewed and accepted in the list, only thing is
> they couldn't make it to upstream during v3.4 mer
On Fri, Apr 13, 2012 at 16:13:07, Paul Walmsley wrote:
> Hi Vaibhav,
>
> On Fri, 13 Apr 2012, Hiremath, Vaibhav wrote:
>
> > Yes, we are using am3517evm file for AM33XX MACHINE_INIT definition here.
> > These patches have been reviewed and accepted in the list, only thing is
> > they couldn't mak
Hi Vaibhav,
On Fri, 13 Apr 2012, Hiremath, Vaibhav wrote:
> Yes, we are using am3517evm file for AM33XX MACHINE_INIT definition here.
> These patches have been reviewed and accepted in the list, only thing is
> they couldn't make it to upstream during v3.4 merge window.
>
> I believe Tony is goi
On Thu, Apr 12, 2012 at 13:56:06, Paul Walmsley wrote:
> Hello Vaibhav,
>
> On Fri, 30 Mar 2012, Vaibhav Hiremath wrote:
>
> > After some healthy discussion, now we have come to the conclusion and
> > decided to handle AM33XX PRM/CM part separately; as AM33XX-PRCM module is
> > different than OMA
Hello Vaibhav,
On Fri, 30 Mar 2012, Vaibhav Hiremath wrote:
> After some healthy discussion, now we have come to the conclusion and
> decided to handle AM33XX PRM/CM part separately; as AM33XX-PRCM module is
> different than OMAP3 and OMAP4 architecture.
Have been reviewing these patch sets here
On Fri, Mar 30, 2012 at 21:33:51, Hiremath, Vaibhav wrote:
> After some healthy discussion, now we have come to the conclusion and
> decided to handle AM33XX PRM/CM part separately; as AM33XX-PRCM module is
> different than OMAP3 and OMAP4 architecture.
>
> The difference becomes very interesting/
20 matches
Mail list logo
