From: santosh.shilimkar@ti.com (Santosh Shilimkar) Date: Tue, 11 Mar 2014 22:44:14 +0800 Subject: [PATCH 2/3] soc: keystone: add QMSS driver In-Reply-To: <5EE98053-31B8-4679-AAE2-4F026C61D1D4@codeaurora.org> References: <1393629520-12713-1-git-send-email-santosh.shilimkar@ti.com> <1393629520-12713-3-git-send-email-santosh.shilimkar@ti.com> <531E2C55.70702@ti.com> <5EE98053-31B8-4679-AAE2-4F026C61D1D4@codeaurora.org> Message-ID: <531F213E.50807@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Tuesday 11 March 2014 10:04 PM, Kumar Gala wrote: > > On Mar 10, 2014, at 4:19 PM, Santosh Shilimkar wrote: > >>>> + -- reg-names : Names for the above register regions. The name to be >>>> + used is as follows: >>>> + - "config" : Queue configuration region. >>>> + - "status" : Queue status RAM. >>>> + - "region" : Descriptor memory setup region. >>>> + - "push" : Queue Management/Queue Proxy region. >>>> + - "pop" : Queue Management/Queue Proxy region. >>>> + - "peek" : Queue Peek region. >>> >>> reg-names should be optional. Also you have the order different from >>> reg. Be consistent as to what is the correct order. >>> >> We thought of using reg-names to remove the ordering to index >> the regs. So if we make the reg-names optional, then indexing >> by order will be used. We can do that. > > We keep having this conversation, why does reg-names need to be optional for new bindings? > I guess the question is for Rob. Regards, Santosh