public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Omar Ramirez Luna <omar.ramirez@ti.com>
To: "Ramirez Luna, Omar" <omar.ramirez@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
	Ameya Palande <ameya.palande@nokia.com>,
	Hiroshi Doyu <Hiroshi.DOYU@nokia.com>,
	Felipe Contreras <felipe.contreras@nokia.com>,
	"Menon, Nishanth" <nm@ti.com>
Subject: Re: [PATCH 00/12] Custom debug removal
Date: Tue, 23 Feb 2010 12:09:07 -0600	[thread overview]
Message-ID: <4B8419C3.4050701@ti.com> (raw)
In-Reply-To: <1266529083-2358-1-git-send-email-omar.ramirez@ti.com>

On 2/18/2010 3:37 PM, Ramirez Luna, Omar wrote:
> Step 2 to remove custom debug tracing.
>
> This set of patches gets rid of GT_* and DBG_* functionality, and
> replaces them to use dev_dbg instead.
>
> This is meant to be a follow up of previous debug removal patches.
>
> More info on dynamic_debug:
> http://lwn.net/Articles/286191/
>
> Omar Ramirez Luna (12):
>    DSPBRIDGE: global bridge device
>    DSPBRIDGE: Change custom GT_trace for dev_dbg
>    DSPBRIDGE: Change custom GT_trace for dev_dbg in wmd
>    DSPBRIDGE: Change custom GT_trace for dev_dbg in pmgr
>    DSPBRIDGE: Change custom GT_trace for dev_dbg in services
>    DSPBRIDGE: Remove GT_trace variables for rmgr
>    DSPBRIDGE: Remove GT_trace variables for wmd
>    DSPBRIDGE: Remove GT_trace variables for pmgr
>    DSPBRIDGE: Remove GT_trace variables for services
>    DSPBRIDGE: Remove custom debugging implementation
>    DSPBRIDGE: Remove debug header files
>    DSPBRIDGE: Remove unused instances of CONFIG_BRIDGE_DEBUG
>
>   arch/arm/plat-omap/include/dspbridge/dbc.h     |    2 -
>   arch/arm/plat-omap/include/dspbridge/dbg.h     |   89 -------
>   arch/arm/plat-omap/include/dspbridge/gt.h      |  308 ----------------------
>   arch/arm/plat-omap/include/dspbridge/host_os.h |    1 +
>   drivers/dsp/bridge/Makefile                    |    4 +-
>   drivers/dsp/bridge/gen/_gt_para.c              |   95 -------
>   drivers/dsp/bridge/gen/gt.c                    |  336 ------------------------
>   drivers/dsp/bridge/pmgr/chnl.c                 |   11 -
>   drivers/dsp/bridge/pmgr/cmm.c                  |   19 +-
>   drivers/dsp/bridge/pmgr/cod.c                  |   15 +-
>   drivers/dsp/bridge/pmgr/dbll.c                 |   75 ++----
>   drivers/dsp/bridge/pmgr/dev.c                  |    8 -
>   drivers/dsp/bridge/pmgr/dmm.c                  |   58 ++---
>   drivers/dsp/bridge/pmgr/io.c                   |   10 -
>   drivers/dsp/bridge/pmgr/msg.c                  |   13 +-
>   drivers/dsp/bridge/pmgr/wcd.c                  |    7 -
>   drivers/dsp/bridge/rmgr/dbdcd.c                |   32 +--
>   drivers/dsp/bridge/rmgr/disp.c                 |   69 ++----
>   drivers/dsp/bridge/rmgr/drv.c                  |   96 +++----
>   drivers/dsp/bridge/rmgr/drv_interface.c        |   55 ++---
>   drivers/dsp/bridge/rmgr/dspdrv.c               |   14 +-
>   drivers/dsp/bridge/rmgr/mgr.c                  |   31 +--
>   drivers/dsp/bridge/rmgr/nldr.c                 |   43 +---
>   drivers/dsp/bridge/rmgr/node.c                 |  118 +++------
>   drivers/dsp/bridge/rmgr/proc.c                 |   94 ++-----
>   drivers/dsp/bridge/rmgr/rmm.c                  |   11 -
>   drivers/dsp/bridge/rmgr/strm.c                 |   45 ++--
>   drivers/dsp/bridge/services/cfg.c              |   23 +--
>   drivers/dsp/bridge/services/clk.c              |   12 +-
>   drivers/dsp/bridge/services/dbg.c              |   88 ------
>   drivers/dsp/bridge/services/mem.c              |    6 -
>   drivers/dsp/bridge/services/ntfy.c             |    8 -
>   drivers/dsp/bridge/services/reg.c              |    7 -
>   drivers/dsp/bridge/services/regsup.c           |   26 +--
>   drivers/dsp/bridge/services/services.c         |   21 +--
>   drivers/dsp/bridge/services/sync.c             |    8 -
>   drivers/dsp/bridge/wmd/chnl_sm.c               |    5 +-
>   drivers/dsp/bridge/wmd/io_sm.c                 |  119 ++++-----
>   drivers/dsp/bridge/wmd/mmu_fault.c             |   10 +-
>   drivers/dsp/bridge/wmd/tiomap3430.c            |  134 +++++------
>   drivers/dsp/bridge/wmd/tiomap3430_pwr.c        |   64 ++----
>   drivers/dsp/bridge/wmd/tiomap_io.c             |    1 -
>   drivers/dsp/bridge/wmd/tiomap_sm.c             |    6 +-
>   drivers/dsp/bridge/wmd/ue_deh.c                |    6 +-
>   44 files changed, 406 insertions(+), 1797 deletions(-)
>   delete mode 100644 arch/arm/plat-omap/include/dspbridge/dbg.h
>   delete mode 100644 arch/arm/plat-omap/include/dspbridge/gt.h
>   delete mode 100644 drivers/dsp/bridge/gen/_gt_para.c
>   delete mode 100644 drivers/dsp/bridge/gen/gt.c
>   delete mode 100644 drivers/dsp/bridge/services/dbg.c
>   create mode 100644 drivers/dsp/bridge/uTimeout
>

removed bogus file: create mode 100644 drivers/dsp/bridge/uTimeout from 
patch [02/12] DSPBRIDGE: Change custom GT_trace for dev_dbg

Included as part of the set:
DSPBRIDGE: Remove GT_TRACE conditional macro
http://marc.info/?l=linux-omap&m=126694528710256&w=2

Rebased and pushed to dspbridge

- omar

      parent reply	other threads:[~2010-02-23 18:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 21:37 [PATCH 00/12] Custom debug removal Omar Ramirez Luna
2010-02-18 21:37 ` [PATCH 01/12] DSPBRIDGE: global bridge device Omar Ramirez Luna
2010-02-18 21:37   ` [PATCH 02/12] DSPBRIDGE: Change custom GT_trace for dev_dbg Omar Ramirez Luna
2010-02-18 21:37     ` [PATCH 03/12] DSPBRIDGE: Change custom GT_trace for dev_dbg in wmd Omar Ramirez Luna
2010-02-18 21:37       ` [PATCH 04/12] DSPBRIDGE: Change custom GT_trace for dev_dbg in pmgr Omar Ramirez Luna
2010-02-18 21:37         ` [PATCH 05/12] DSPBRIDGE: Change custom GT_trace for dev_dbg in services Omar Ramirez Luna
2010-02-18 21:37           ` [PATCH 06/12] DSPBRIDGE: Remove GT_trace variables for rmgr Omar Ramirez Luna
2010-02-18 21:37             ` [PATCH 07/12] DSPBRIDGE: Remove GT_trace variables for wmd Omar Ramirez Luna
2010-02-18 21:37               ` [PATCH 08/12] DSPBRIDGE: Remove GT_trace variables for pmgr Omar Ramirez Luna
2010-02-18 21:38                 ` [PATCH 09/12] DSPBRIDGE: Remove GT_trace variables for services Omar Ramirez Luna
2010-02-18 21:38                   ` [PATCH 10/12] DSPBRIDGE: Remove custom debugging implementation Omar Ramirez Luna
2010-02-18 21:38                     ` [PATCH 11/12] DSPBRIDGE: Remove debug header files Omar Ramirez Luna
2010-02-18 21:38                       ` [PATCH 12/12] DSPBRIDGE: Remove unused instances of CONFIG_BRIDGE_DEBUG Omar Ramirez Luna
2010-02-23 18:09 ` Omar Ramirez Luna [this message]

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=4B8419C3.4050701@ti.com \
    --to=omar.ramirez@ti.com \
    --cc=Hiroshi.DOYU@nokia.com \
    --cc=ameya.palande@nokia.com \
    --cc=felipe.contreras@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox