All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: balbi@ti.com
Cc: linux-media@vger.kernel.org, linux-omap@vger.kernel.org,
	sakari.ailus@maxwell.research.nokia.com
Subject: Re: [PATCH v6 02/10] omap3: Remove unusued ISP CBUFF resource
Date: Mon, 14 Feb 2011 13:59:26 +0100	[thread overview]
Message-ID: <201102141359.27273.laurent.pinchart@ideasonboard.com> (raw)
In-Reply-To: <20110214123106.GW2549@legolas.emea.dhcp.ti.com>

Hi Felipe,

On Monday 14 February 2011 13:31:06 Felipe Balbi wrote:
> On Mon, Feb 14, 2011 at 01:21:29PM +0100, Laurent Pinchart wrote:
> > From: Sergio Aguirre <saaguirre@ti.com>
> > 
> > The ISP CBUFF module isn't use, its resource isn't needed.
> > 
> > Signed-off-by: Sergio Aguirre <saaguirre@ti.com>
> > Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > Acked-by: Tony Lindgren <tony@atomide.com>
> 
> it's unused but it's there right ? what's the problem in keeping it ?
> maybe you'd like to add name for the resources as well, there are many
> of them and keeping the order correct might be difficult. You can move
> to platform_get_resource_byname() on drivers.

But if it's unused, why keep it ? :-) There are other resources present on the 
chip (especially on older silicon versions) that are completely unused and 
even undocumented. They're not defined either.

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2011-02-14 12:59 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14 12:21 [PATCH v6 00/10] OMAP3 ISP driver Laurent Pinchart
2011-02-14 12:21 ` [PATCH v6 01/10] ARM: OMAP3: Update Camera ISP definitions for OMAP3630 Laurent Pinchart
2011-02-14 12:21 ` [PATCH v6 02/10] omap3: Remove unusued ISP CBUFF resource Laurent Pinchart
2011-02-14 12:31   ` Felipe Balbi
2011-02-14 12:59     ` Laurent Pinchart [this message]
2011-02-14 12:21 ` [PATCH v6 03/10] omap3: Add function to register omap3isp platform device structure Laurent Pinchart
2011-02-14 12:34   ` Felipe Balbi
2011-02-14 13:07     ` Laurent Pinchart
2011-02-14 13:18       ` Felipe Balbi
2011-02-14 15:15         ` David Cohen
2011-02-14 12:21 ` [PATCH v6 04/10] omap2: Fix camera resources for multiomap Laurent Pinchart
2011-02-14 12:35   ` Felipe Balbi
2011-02-14 13:19     ` Laurent Pinchart
2011-02-14 13:41       ` Felipe Balbi
2011-02-14 13:50         ` Laurent Pinchart
2011-02-14 15:11           ` David Cohen
2011-02-14 12:21 ` [PATCH v6 05/10] omap3isp: OMAP3 ISP core Laurent Pinchart
2011-02-14 12:21 ` [PATCH v6 06/10] omap3isp: Video devices and buffers queue Laurent Pinchart
2011-02-14 12:21 ` [PATCH v6 07/10] omap3isp: CCP2/CSI2 receivers Laurent Pinchart
2011-02-14 12:37   ` Felipe Balbi
2011-02-14 13:25     ` Laurent Pinchart
2011-02-14 13:32     ` Laurent Pinchart
2011-02-14 12:38   ` Felipe Balbi
2011-02-14 12:21 ` [PATCH v6 08/10] omap3isp: CCDC, preview engine and resizer Laurent Pinchart
2011-02-14 12:21 ` [PATCH v6 09/10] omap3isp: Statistics Laurent Pinchart
2011-02-14 12:21 ` [PATCH v6 10/10] omap3isp: Kconfig and Makefile Laurent Pinchart
2011-02-14 12:56 ` [PATCH v6 00/10] OMAP3 ISP driver Hans Verkuil

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=201102141359.27273.laurent.pinchart@ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=balbi@ti.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=sakari.ailus@maxwell.research.nokia.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.