All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Greg KH <greg@kroah.com>, linux-omap <linux-omap@vger.kernel.org>,
	Omar Ramirez Luna <omar.ramirez@ti.com>,
	Paul Walmsley <paul@pwsan.com>,
	Fernando Guzman Lugo <fernando.lugo@ti.com>
Subject: Re: [PATCH 0/5] omap: dsp: fixes for 2.6.37-rc1
Date: Mon, 8 Nov 2010 11:16:49 -0800	[thread overview]
Message-ID: <20101108191648.GR9264@atomide.com> (raw)
In-Reply-To: <20101108164538.GJ9264@atomide.com>

* Tony Lindgren <tony@atomide.com> [101108 08:37]:
> * Felipe Contreras <felipe.contreras@gmail.com> [101107 14:38]:
> 
> Thanks for putting together all these patches, that already helps
> people working on it a great deal.
> 
> However, these patches are in the no-no category for -rc cycle, they're
> in the "fixes for features that never worked in the first place"
> category. Linus will not take it and I don't want to take it. We just
> have to follow the standard Linux development cycle.
>  
> > Anyway, there's an alternative that doesn't require omap to ack:
> > 
> > --- a/drivers/staging/tidspbridge/core/tiomap3430.c
> > +++ b/drivers/staging/tidspbridge/core/tiomap3430.c
> > @@ -23,7 +23,6 @@
> >  #include <dspbridge/host_os.h>
> >  #include <linux/mm.h>
> >  #include <linux/mmzone.h>
> > -#include <plat/control.h>
> > 
> >  /*  ----------------------------------- DSP/BIOS Bridge */
> >  #include <dspbridge/dbdefs.h>
> > @@ -74,6 +73,18 @@
> >  #define PAGES_II_LVL_TABLE   512
> >  #define PHYS_TO_PAGE(phys)      pfn_to_page((phys) >> PAGE_SHIFT)
> > 
> > +/*
> > + * This is a totally ugly layer violation, but needed until
> > + * omap_ctrl_set_dsp_boot*() are provided.
> > + */
> > +#define OMAP3_IVA2_BOOTMOD_IDLE 1
> > +#define OMAP2_CONTROL_GENERAL 0x270
> > +#define OMAP343X_CONTROL_IVA2_BOOTADDR (OMAP2_CONTROL_GENERAL + 0x0190)
> > +#define OMAP343X_CONTROL_IVA2_BOOTMOD (OMAP2_CONTROL_GENERAL + 0x0194)
> > +
> > +#define OMAP343X_CTRL_REGADDR(reg) \
> > +       OMAP2_L4_IO_ADDRESS(OMAP343X_CTRL_BASE + (reg))
> > +
> >  /* Forward Declarations: */
> >  static int bridge_brd_monitor(struct bridge_dev_context *dev_ctxt);
> >  static int bridge_brd_read(struct bridge_dev_context *dev_ctxt,
> 
> If this makes the dspbridge usable, that sounds like the way to go
> for the -rc cycle.
> 
> But I don't think this the only patch needed then?

I guess it would be this fix + omap: dsp: remove shm from normal memory +
revert some drivers/staging/tidspbridge patches?

It's still quite a bit of patches for the -rc cycle..

If you want, I can keep merging your branch into linux-omap master
branch for testing while we're waiting for the next merge window. 

Regards,

Tony

  reply	other threads:[~2010-11-08 19:16 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-07 21:36 [GIT PULL] fixes for tidspbridge 2.6.37-rc1 Felipe Contreras
2010-11-07 21:43 ` [PATCH 0/5] omap: dsp: fixes for 2.6.37-rc1 Felipe Contreras
2010-11-07 22:02   ` Greg KH
2010-11-07 22:48     ` Felipe Contreras
2010-11-08 16:45       ` Tony Lindgren
2010-11-08 19:16         ` Tony Lindgren [this message]
2010-11-08 22:56           ` Felipe Contreras
2010-11-09  0:51             ` Tony Lindgren
2010-12-15  6:00   ` Paul Walmsley
2010-12-15 13:04     ` Felipe Contreras
2010-11-07 21:43 ` [PATCH 1/5] omap: dsp: remove shm from normal memory Felipe Contreras
2010-11-09  0:53   ` Tony Lindgren
2010-11-09  1:00     ` Greg KH
2010-11-07 21:43 ` [PATCH 2/5] omap: control: add functions for DSP boot Felipe Contreras
2010-11-11  0:00   ` Paul Walmsley
2010-11-11 11:12     ` Felipe Contreras
2010-11-11 15:26       ` Paul Walmsley
2010-11-07 21:43 ` [PATCH 3/5] omap: pm: use control functions in DSP reset code Felipe Contreras
2010-11-07 21:43 ` [PATCH 4/5] omap: dsp: add boot control functions Felipe Contreras
2010-11-07 21:43 ` [PATCH 5/5] staging: tidspbridge: use " Felipe Contreras
2010-11-08 23:00 ` [GIT PULL] fixes for tidspbridge 2.6.37-rc1 Felipe Contreras
2010-11-09  0:57   ` Tony Lindgren
2010-11-09 16:29   ` Arnd Bergmann
2010-11-09 16:46     ` Guzman Lugo, Fernando
2010-11-09 17:35       ` Tony Lindgren
2010-11-09 17:52         ` Guzman Lugo, Fernando
2010-11-09 18:32           ` Tony Lindgren
2010-11-09 22:13             ` Felipe Contreras
2010-11-09 22:13               ` Felipe Contreras
2010-11-09 21:26           ` Felipe Contreras
2010-11-09 16:55     ` Greg KH
2010-11-09 17:04       ` Guzman Lugo, Fernando
2010-11-09 17:04         ` Guzman Lugo, Fernando
2010-11-09 17:25         ` Greg KH
2010-11-09 17:25           ` Greg KH
2010-11-09 17:49           ` Guzman Lugo, Fernando
2010-11-09 17:49             ` Guzman Lugo, Fernando
2010-11-09 17:58             ` Greg KH
2010-11-09 17:58               ` Greg KH
2010-11-09 18:40               ` Ramirez Luna, Omar
2010-11-09 18:40                 ` Ramirez Luna, Omar
2010-11-09 21:53               ` Felipe Contreras
2010-11-09 21:53                 ` Felipe Contreras
2010-11-09 22:10                 ` Greg KH
2010-11-09 22:39                   ` Felipe Contreras
2010-11-09 22:52                     ` Greg KH
2010-11-09 22:04     ` Felipe Contreras
2010-11-09 22:04       ` Felipe Contreras

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101108191648.GR9264@atomide.com \
    --to=tony@atomide.com \
    --cc=felipe.contreras@gmail.com \
    --cc=fernando.lugo@ti.com \
    --cc=greg@kroah.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=omar.ramirez@ti.com \
    --cc=paul@pwsan.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.