[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1376910775.3157.1.camel@hornet>
Date: Mon, 19 Aug 2013 12:12:55 +0100
From: Pawel Moll <pawel.moll@....com>
To: Stephen Warren <swarren@...dotorg.org>
Cc: Kumar Gala <galak@...eaurora.org>,
"ohad@...ery.com" <ohad@...ery.com>,
"rob.herring@...xeda.com" <rob.herring@...xeda.com>,
Mark Rutland <Mark.Rutland@....com>,
Ian Campbell <ian.campbell@...rix.com>,
"grant.likely@...aro.org" <grant.likely@...aro.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>,
Jeffrey Hugo <jhugo@...eaurora.org>,
Eric Holmberg <eholmber@...eaurora.org>
Subject: Re: [PATCH v3] hwspinlock/msm: Add support for Qualcomm MSM HW
Mutex block
On Fri, 2013-08-16 at 23:54 +0100, Stephen Warren wrote:
> Indeed, I tend to think that reg-names is a bad idea.
>
> IIRC, the rule for "reg" is that entries must always have a defined
> order, so that it can always be accessed by integer index.
First time I hear about that rule, really...
> And given
> that's true, allowing for reg-names just creates confusion since it
> implies you can look up the index in reg-names and then read reg at that
> index.
I actually believe that named resources leave less are for error than
indexed ones. And this is the message I remember being "spread" in the
times of static platform devices.
Pawel
--
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