[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120510214604.GA3525@kroah.com>
Date: Thu, 10 May 2012 14:46:04 -0700
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Hiroshi DOYU <hdoyu@...dia.com>
Cc: linux-tegra@...r.kernel.org,
Grant Likely <grant.likely@...retlab.ca>,
Rob Herring <rob.herring@...xeda.com>,
Rob Landley <rob@...dley.net>,
Colin Cross <ccross@...roid.com>,
Olof Johansson <olof@...om.net>,
Stephen Warren <swarren@...dotorg.org>,
Russell King <linux@....linux.org.uk>,
Santosh Shilimkar <santosh.shilimkar@...com>,
Benoit Cousson <b-cousson@...com>, Aneesh V <aneesh@...com>,
devicetree-discuss@...ts.ozlabs.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 3/4] ARM: tegra30: Add Tegra Memory Controller(MC) driver
On Thu, May 10, 2012 at 10:42:32AM +0300, Hiroshi DOYU wrote:
> Tegra Memory Controller(MC) driver for Tegra30
> Added to support MC General interrupts, mainly for IOMMU(SMMU).
I'll apply this, but:
> +static inline u32 mc_readl(struct tegra30_mc *mc, u32 offs)
> +{
> + if (offs < 0x10)
> + return readl(mc->regs[0] + offs);
> + BUG_ON(offs < 0x3c);
> + if (offs < 0x1f0)
> + return readl(mc->regs[1] + offs - 0x3c);
> + BUG_ON(offs < 0x200);
> + if (offs < 0x228)
> + return readl(mc->regs[2] + offs - 0x200);
> + BUG_ON(offs < 0x284);
> + if (offs < 0x400)
> + return readl(mc->regs[3] + offs - 0x284);
> + BUG();
> +}
That's a lot of BUG* calls. Same thing with the 1/4 patch in this
series.
We really should not have a BUG call in any driver, as you just stopped
the whole system. I can understand this being there for debugging when
you create the code originally, but as these are things no one should
ever be able to hit now, you should remove them, right?
Care to write a follow-on patch removing all of these BUG_ON and BUG
calls in this and the drivers/memory/tegra20-mc.c driver?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists