From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: Configurable interrupt sources, and DT bindings Date: Tue, 29 Nov 2011 11:20:10 +0000 Message-ID: <20111129112010.GD2851@opensource.wolfsonmicro.com> References: <4ED40B5F.6030603@nvidia.com> <4ED417F2.1030900@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <4ED417F2.1030900-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org Sender: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org To: Rob Herring Cc: Devicetree Discuss List-Id: devicetree@vger.kernel.org On Mon, Nov 28, 2011 at 05:23:30PM -0600, Rob Herring wrote: > I think adding another property is the wrong approach. The information > is already there in the interrupt binding. irq_create_of_mapping almost > does what you need. Perhaps it could be extended to return the type as > part of the irq resource. There are already defined resource bits for this: That looks like a sensible place to put the translation but it (or the dt_translate() op it calls) is still going to need to figure out the value to return from somewhere and if the interrupt binding defines that information it's not terribly obvious.