From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: In-Reply-To: <9e4733910711101516n64870e40rbd1fcbe3d123fcc3@mail.gmail.com> References: <9e4733910711101144r3f8745dbs572aefa8658e1312@mail.gmail.com> <3DBBAC12-579B-4C1F-9C9E-D085FB22B687@kernel.crashing.org> <9e4733910711101516n64870e40rbd1fcbe3d123fcc3@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: From: Kumar Gala Subject: Re: IRQs in i2c-mpc.c Date: Sat, 10 Nov 2007 17:18:56 -0600 To: "Jon Smirl" Cc: PowerPC dev list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Nov 10, 2007, at 5:16 PM, Jon Smirl wrote: > On 11/10/07, Kumar Gala wrote: >> Looking at the current driver it looks like we could get ride of if >> check since the previous code checked the return of >> platform_get_irq(). > > The code was a snippet from the larger patch that is converting i2c > from being a platform driver to a of_platform driver. > > The question is, what to do about a missing IRQ tag in the device tree > or a IRQ of zero. What is an error and what should be ignored, etc. I think the lack of an IRQ in the device tree should be an error. If the IRQ value is zero, than its zero. - k