[PATCH 0/5] DSPBRIDGE: patches.

[PATCH 0/5] DSPBRIDGE: patches.

[Guzman Lugo, Fernando]

Hi,

	I am sending my patches again, now they are base on this commit:

commit bacaa3dc169e11488faf17519a42c4e8641fc17e
Author: Hiroshi DOYU <Hiroshi.DOYU@nokia.com>
Date:   Mon Feb 16 10:43:15 2009 +0200

    TIDSPBRIDGE: fix some build warnings

I hope there will be not problems this time.

Re: [PATCH 0/5] DSPBRIDGE: patches.

[Ameya Palande]

On Tue, Mar 3, 2009 at 2:00 AM, Guzman Lugo, Fernando <x0095840@ti.com> wrote:
>
>
> Hi,
>
>        I am sending my patches again, now they are base on this commit:
>
> commit bacaa3dc169e11488faf17519a42c4e8641fc17e
> Author: Hiroshi DOYU <Hiroshi.DOYU@nokia.com>
> Date:   Mon Feb 16 10:43:15 2009 +0200
>
>    TIDSPBRIDGE: fix some build warnings
>
> I hope there will be not problems this time.
>

Hi Fernando,

Are you using tidspbridge-pm branch from
http://gitorious.org/projects/lk/repos/mainline ?

Cheers,
Ameya.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

RE: [PATCH 0/5] DSPBRIDGE: patches.

[Kanigeri, Hari]

Hi Ameya,

> Hi Fernando,
> 
> Are you using tidspbridge-pm branch from 
> http://gitorious.org/projects/lk/repos/mainline ?
> 
> Cheers,
> Ameya.

-- The Bridge patches will be based on omapzoom tree.

Thank you,
Best regards,
Hari
 

> -----Original Message-----
> From: linux-omap-owner@vger.kernel.org 
> [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Ameya Palande
> Sent: Thursday, March 05, 2009 4:27 AM
> To: Guzman Lugo, Fernando
> Cc: Hiroshi DOYU; linux-omap@vger.kernel.org
> Subject: Re: [PATCH 0/5] DSPBRIDGE: patches.
> 
> On Tue, Mar 3, 2009 at 2:00 AM, Guzman Lugo, Fernando 
> <x0095840@ti.com> wrote:
> >
> >
> > Hi,
> >
> >        I am sending my patches again, now they are base on 
> this commit:
> >
> > commit bacaa3dc169e11488faf17519a42c4e8641fc17e
> > Author: Hiroshi DOYU <Hiroshi.DOYU@nokia.com>
> > Date:   Mon Feb 16 10:43:15 2009 +0200
> >
> >    TIDSPBRIDGE: fix some build warnings
> >
> > I hope there will be not problems this time.
> >
> 
> Hi Fernando,
> 
> Are you using tidspbridge-pm branch from 
> http://gitorious.org/projects/lk/repos/mainline ?
> 
> Cheers,
> Ameya.
> --
> To unsubscribe from this list: send the line "unsubscribe 
> linux-omap" in the body of a message to 
> majordomo@vger.kernel.org More majordomo info at  
> http://vger.kernel.org/majordomo-info.html
> 
> --
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH 0/5] DSPBRIDGE: patches.

[Felipe Contreras]

On Thu, Mar 5, 2009 at 3:18 PM, Kanigeri, Hari <h-kanigeri2@ti.com> wrote:
> Hi Ameya,
>
>> Hi Fernando,
>>
>> Are you using tidspbridge-pm branch from
>> http://gitorious.org/projects/lk/repos/mainline ?
>>
>> Cheers,
>> Ameya.
>
> -- The Bridge patches will be based on omapzoom tree.

We are in linux-omap, not omapzoom, and this is the tidspbridge branch
in linux-omap:
http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=shortlog;h=tidspbridge

I'm sure you don't want to increase the discrepancy between linux-omap
and omapzoom, so the patches sent to l-o should apply on top of the
l-o tidspbridge in order to be merged.

-- 
Felipe Contreras

RE: [PATCH 0/5] DSPBRIDGE: patches.

[Kanigeri, Hari]

Hi Felipe,

> We are in linux-omap, not omapzoom, and this is the 
> tidspbridge branch in linux-omap:
> http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.
6.git;a=shortlog;h=tidspbridge
> 
> I'm sure you don't want to increase the discrepancy between 
> linux-omap and omapzoom, so the patches sent to l-o should 
> apply on top of the l-o tidspbridge in order to be merged.

-- I am sorry, as of now the Bridge patches will be based only on omapzoom tree.

Thank you,
Best regards,
Hari
 

> -----Original Message-----
> From: Felipe Contreras [mailto:felipe.contreras@gmail.com] 
> Sent: Thursday, March 05, 2009 7:42 AM
> To: Kanigeri, Hari
> Cc: Ameya Palande; Guzman Lugo, Fernando; Hiroshi DOYU; 
> linux-omap@vger.kernel.org
> Subject: Re: [PATCH 0/5] DSPBRIDGE: patches.
> 
> On Thu, Mar 5, 2009 at 3:18 PM, Kanigeri, Hari 
> <h-kanigeri2@ti.com> wrote:
> > Hi Ameya,
> >
> >> Hi Fernando,
> >>
> >> Are you using tidspbridge-pm branch from 
> >> http://gitorious.org/projects/lk/repos/mainline ?
> >>
> >> Cheers,
> >> Ameya.
> >
> > -- The Bridge patches will be based on omapzoom tree.
> 
> We are in linux-omap, not omapzoom, and this is the 
> tidspbridge branch in linux-omap:
> http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.
6.git;a=shortlog;h=tidspbridge
> 
> I'm sure you don't want to increase the discrepancy between 
> linux-omap and omapzoom, so the patches sent to l-o should 
> apply on top of the l-o tidspbridge in order to be merged.
> 
> --
> Felipe Contreras
> 
> 

RE: [PATCH 0/5] DSPBRIDGE: patches.

[Menon, Nishanth]

Hi Hari,
> -----Original Message-----
> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> owner@vger.kernel.org] On Behalf Of Kanigeri, Hari
> Sent: Thursday, March 05, 2009 3:52 PM
> To: Felipe Contreras
> Cc: Ameya Palande; Guzman Lugo, Fernando; Hiroshi DOYU; linux-
> omap@vger.kernel.org
> Subject: RE: [PATCH 0/5] DSPBRIDGE: patches.
> > We are in linux-omap, not omapzoom, and this is the
> > tidspbridge branch in linux-omap:
> > http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.
> 6.git;a=shortlog;h=tidspbridge
> >
> > I'm sure you don't want to increase the discrepancy between
> > linux-omap and omapzoom, so the patches sent to l-o should
> > apply on top of the l-o tidspbridge in order to be merged.
> 
> -- I am sorry, as of now the Bridge patches will be based only on omapzoom
> tree.

Ok, so we have:
a) omapzoom bridge
b) linux omap bridge

Impertinent question: what are our plans b/w these two?

Regards,
Nishanth Menon

RE: [PATCH 0/5] DSPBRIDGE: patches.

[Kanigeri, Hari]

Hi,

> Ok, so we have:
> a) omapzoom bridge
> b) linux omap bridge
> 
> Impertinent question: what are our plans b/w these two?
> 

A. omapzoom bridge -- As far as I know, this will be the master tree for the DSPBridge code. The Bridge patches will be based on this tree. I think it was already communicated some time ago that the linux-omap mailing list will be used for Bridge discussions and for sending the Bridge patches to OMAPZOOM. There is no separate mailing list for omapzoom.

B. linux omap bridge -- I think this tree is maintained by Hiroshi by merging the patches that are sent to OMAPZOOM tree. The only difference that should be between the omapzoom tree and linux omap tree is the Power management. Omapzoom Bridge uses T.I Power management, where as the linux omap Bridge uses open source Power management. So, any patches related to open source power manaegment will be based on linux omap tree. The maintainer of linux omap Bridge tree should sync up the Bridge changes from the omapzoom tree.


Thank you,
Best regards,
Hari
 

> -----Original Message-----
> From: Menon, Nishanth 
> Sent: Thursday, March 05, 2009 8:05 AM
> To: Kanigeri, Hari; Felipe Contreras
> Cc: Ameya Palande; Guzman Lugo, Fernando; Hiroshi DOYU; 
> linux-omap@vger.kernel.org
> Subject: RE: [PATCH 0/5] DSPBRIDGE: patches.
> 
> Hi Hari,
> > -----Original Message-----
> > From: linux-omap-owner@vger.kernel.org [mailto:linux-omap- 
> > owner@vger.kernel.org] On Behalf Of Kanigeri, Hari
> > Sent: Thursday, March 05, 2009 3:52 PM
> > To: Felipe Contreras
> > Cc: Ameya Palande; Guzman Lugo, Fernando; Hiroshi DOYU; linux- 
> > omap@vger.kernel.org
> > Subject: RE: [PATCH 0/5] DSPBRIDGE: patches.
> > > We are in linux-omap, not omapzoom, and this is the tidspbridge 
> > > branch in linux-omap:
> > > http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.
> > 6.git;a=shortlog;h=tidspbridge
> > >
> > > I'm sure you don't want to increase the discrepancy between 
> > > linux-omap and omapzoom, so the patches sent to l-o 
> should apply on 
> > > top of the l-o tidspbridge in order to be merged.
> > 
> > -- I am sorry, as of now the Bridge patches will be based only on 
> > omapzoom tree.
> 
> Ok, so we have:
> a) omapzoom bridge
> b) linux omap bridge
> 
> Impertinent question: what are our plans b/w these two?
> 
> Regards,
> Nishanth Menon
> 

RE: [PATCH 0/5] DSPBRIDGE: patches.

[Menon, Nishanth]

> -----Original Message-----
> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> owner@vger.kernel.org] On Behalf Of Felipe Contreras
> Sent: Thursday, March 05, 2009 3:42 PM
> To: Kanigeri, Hari
> Cc: Ameya Palande; Guzman Lugo, Fernando; Hiroshi DOYU; linux-
> omap@vger.kernel.org
> Subject: Re: [PATCH 0/5] DSPBRIDGE: patches.
> 
> On Thu, Mar 5, 2009 at 3:18 PM, Kanigeri, Hari <h-kanigeri2@ti.com> wrote:
> > Hi Ameya,
> >
> >> Hi Fernando,
> >>
> >> Are you using tidspbridge-pm branch from
> >> http://gitorious.org/projects/lk/repos/mainline ?
> >>
> >> Cheers,
> >> Ameya.
> >
> > -- The Bridge patches will be based on omapzoom tree.
> 
> We are in linux-omap, not omapzoom, and this is the tidspbridge branch
> in linux-omap:
> http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-
> 2.6.git;a=shortlog;h=tidspbridge
> 
> I'm sure you don't want to increase the discrepancy between linux-omap
> and omapzoom, so the patches sent to l-o should apply on top of the
> l-o tidspbridge in order to be merged.
Yeah it gets real confusing. How about following the same rules for the OMAPZOOM kernel here too: any patch w.r.t OMAPZOOM comes:
Subj: RE: [OMAPZOOM PATCH 0/5] DSPBRIDGE: blah blah blah.

Helps to keep things in perspective..
Regards,
Nishanth Menon

RE: [PATCH 0/5] DSPBRIDGE: patches.

[Kanigeri, Hari]

Nishant,

> Yeah it gets real confusing. How about following the same 
> rules for the OMAPZOOM kernel here too: any patch w.r.t 
> OMAPZOOM comes:
> Subj: RE: [OMAPZOOM PATCH 0/5] DSPBRIDGE: blah blah blah.
> 

-- I agree with your suggestion. The subject should have OMAPZOOM to differentiate.



Thank you,
Best regards,
Hari
 

> -----Original Message-----
> From: Menon, Nishanth 
> Sent: Thursday, March 05, 2009 7:52 AM
> To: Felipe Contreras; Kanigeri, Hari
> Cc: Ameya Palande; Guzman Lugo, Fernando; Hiroshi DOYU; 
> linux-omap@vger.kernel.org
> Subject: RE: [PATCH 0/5] DSPBRIDGE: patches.
> 
> > -----Original Message-----
> > From: linux-omap-owner@vger.kernel.org [mailto:linux-omap- 
> > owner@vger.kernel.org] On Behalf Of Felipe Contreras
> > Sent: Thursday, March 05, 2009 3:42 PM
> > To: Kanigeri, Hari
> > Cc: Ameya Palande; Guzman Lugo, Fernando; Hiroshi DOYU; linux- 
> > omap@vger.kernel.org
> > Subject: Re: [PATCH 0/5] DSPBRIDGE: patches.
> > 
> > On Thu, Mar 5, 2009 at 3:18 PM, Kanigeri, Hari 
> <h-kanigeri2@ti.com> wrote:
> > > Hi Ameya,
> > >
> > >> Hi Fernando,
> > >>
> > >> Are you using tidspbridge-pm branch from 
> > >> http://gitorious.org/projects/lk/repos/mainline ?
> > >>
> > >> Cheers,
> > >> Ameya.
> > >
> > > -- The Bridge patches will be based on omapzoom tree.
> > 
> > We are in linux-omap, not omapzoom, and this is the 
> tidspbridge branch 
> > in linux-omap:
> > http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-
> > 2.6.git;a=shortlog;h=tidspbridge
> > 
> > I'm sure you don't want to increase the discrepancy between 
> linux-omap 
> > and omapzoom, so the patches sent to l-o should apply on top of the 
> > l-o tidspbridge in order to be merged.
> Yeah it gets real confusing. How about following the same 
> rules for the OMAPZOOM kernel here too: any patch w.r.t 
> OMAPZOOM comes:
> Subj: RE: [OMAPZOOM PATCH 0/5] DSPBRIDGE: blah blah blah.
> 
> Helps to keep things in perspective..
> Regards,
> Nishanth Menon
> 
> 

Re: [PATCH 0/5] DSPBRIDGE: patches.

[Felipe Contreras]

On Thu, Mar 5, 2009 at 3:56 PM, Kanigeri, Hari <h-kanigeri2@ti.com> wrote:
> Nishant,
>
>> Yeah it gets real confusing. How about following the same
>> rules for the OMAPZOOM kernel here too: any patch w.r.t
>> OMAPZOOM comes:
>> Subj: RE: [OMAPZOOM PATCH 0/5] DSPBRIDGE: blah blah blah.
>>
>
> -- I agree with your suggestion. The subject should have OMAPZOOM to differentiate.

Nishanth has kindly explained me that this patch, sent to the l-o
mailing list, is not meant for the l-o tree.

A better way to differentiate patches specific for o-z is to send them
to the o-z mailing list, instead of l-o, right?

Tony: Or have you agreed with TI that these [OMAPZOOM] patches that
don't apply on top of l-o are ok here?

-- 
Felipe Contreras

Re: [PATCH 0/5] DSPBRIDGE: patches.

[Tony Lindgren]

* Felipe Contreras <felipe.contreras@gmail.com> [090305 06:06]:
> On Thu, Mar 5, 2009 at 3:56 PM, Kanigeri, Hari <h-kanigeri2@ti.com> wrote:
> > Nishant,
> >
> >> Yeah it gets real confusing. How about following the same
> >> rules for the OMAPZOOM kernel here too: any patch w.r.t
> >> OMAPZOOM comes:
> >> Subj: RE: [OMAPZOOM PATCH 0/5] DSPBRIDGE: blah blah blah.
> >>
> >
> > -- I agree with your suggestion. The subject should have OMAPZOOM to differentiate.
> 
> Nishanth has kindly explained me that this patch, sent to the l-o
> mailing list, is not meant for the l-o tree.
> 
> A better way to differentiate patches specific for o-z is to send them
> to the o-z mailing list, instead of l-o, right?
> 
> Tony: Or have you agreed with TI that these [OMAPZOOM] patches that
> don't apply on top of l-o are ok here?

Well as long as they're clearly tagged as OMAPZOOM, things don't get
too confusing, so I'm OK with that.

But in general I'm worried as it looks like the zoom tree is just
piling up more and more hacks and ifdefs with no serious attempt to
merge that code upstream.

Everybody, we need to get the infrastructure pieces done properly
and into the mainline tree so we can use that for all our omap needs.

Sure some board specific hacks will be still needed here and there,
and tons of the omap and driver patches already apply against the
mainline kernel code.

It's up to each developer to submit their patches through the right
mailing lists to the mainline kernel. Piling up code into some other
trees only increases the diff against the mainline tree. 

Everybody, when you see a piece of omap code that's not in the
mainline kernel yet, whine and complain until the code gets
integrated.

Tony