[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <525FEB7A.5040406@metafoo.de>
Date:	Thu, 17 Oct 2013 15:51:54 +0200
From:	Lars-Peter Clausen <lars@...afoo.de>
To:	Timur Tabi <timur@...i.org>
CC:	Xiubo Li <Li.Xiubo@...escale.com>, r65073@...escale.com,
	lgirdwood@...il.com, broonie@...nel.org, mark.rutland@....com,
	alsa-devel@...a-project.org, linux-doc@...r.kernel.org,
	tiwai@...e.de, b18965@...escale.com, LW@...O-electronics.de,
	linux@....linux.org.uk, b42378@...escale.com, oskar@...ra.com,
	grant.likely@...aro.org, devicetree@...r.kernel.org,
	ian.campbell@...rix.com, pawel.moll@....com, swarren@...dotorg.org,
	rob.herring@...xeda.com, linux-arm-kernel@...ts.infradead.org,
	fabio.estevam@...escale.com, linux-kernel@...r.kernel.org,
	rob@...dley.net, r64188@...escale.com, shawn.guo@...aro.org,
	linuxppc-dev@...ts.ozlabs.org
Subject: Re: [alsa-devel] [PATCHv1 1/8] ALSA: Add SAI SoC Digital Audio Interface
 driver.
On 10/17/2013 03:37 PM, Timur Tabi wrote:
> Lars-Peter Clausen wrote:
>>> >Maybe I've been out of the loop for too long, but why is that a particular
>>> >problem with this driver?
> 
>> It is usually something you'd want to check in general to make sure that you
>> don't have multiple device that access the same iomem region at the same
>> time.
> 
> I understand that, but I'm trying to figure out why of_iomap() is okay for
> hundreds of other drivers, but not this one.  I've used it dozens of times
> myself, without ever worrying about overlapping regions.
The driver would work fine with just of_iomap(). But the resource range
check comes basically for free and it does help to catch errors, so I'd
recommend on using it rather than not using it.
- Lars
--
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
 
