Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755292Ab3JVTsv (ORCPT ); Tue, 22 Oct 2013 15:48:51 -0400 Received: from fallback3.mail.ru ([94.100.176.58]:42139 "EHLO fallback3.mail.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755167Ab3JVTss (ORCPT ); Tue, 22 Oct 2013 15:48:48 -0400 From: =?UTF-8?B?QWxleGFuZGVyIFNoaXlhbg==?= To: =?UTF-8?B?RGF2aWQgQ29oZW4=?= Cc: gregkh@linuxfoundation.org, jslaby@suse.cz, ning.li@intel.com, ivan.gorinov@intel.com, linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org Subject: =?UTF-8?B?UmU6IFtQQVRDSCAyLzJdIG1yc3RfbWF4MzExMDogZml4IFNQSSBVQVJUIGlu?= =?UTF-8?B?dGVycnVwdCBwYXJhbWV0ZXJz?= Mime-Version: 1.0 X-Mailer: Mail.Ru Mailer 1.0 X-Originating-IP: [188.134.40.128] Date: Tue, 22 Oct 2013 23:46:00 +0400 Reply-To: =?UTF-8?B?QWxleGFuZGVyIFNoaXlhbg==?= X-Priority: 3 (Normal) Message-ID: <1382471160.205404749@f402.i.mail.ru> Content-Type: text/plain; charset=utf-8 X-Mras: Ok X-Spam: undefined In-Reply-To: <1382470930-13807-2-git-send-email-david.a.cohen@linux.intel.com> References: <1382470930-13807-1-git-send-email-david.a.cohen@linux.intel.com> <1382470930-13807-2-git-send-email-david.a.cohen@linux.intel.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id r9MJmwgD008273 Content-Length: 1390 Lines: 40 > The change in the max3110 driver makes the IRQ handling threaded, now > the handler is called only once per received character. Without that > change, we had many (more than 100) interrupts per one received > character. > > Unfortunately, SFI interface does not support IRQ polarity and > triggering modes, so we have to keep the hacks as hard-coded device > names and IRQ numbers until we switch to ACPI. > > Edge-triggered IRQ still supported to keep old platforms working. > Use platform data to pass the irq mode argument. > > Signed-off-by: Ivan Gorinov > Signed-off-by: Li Ning > Signed-off-by: David Cohen ... > +++ b/include/linux/serial_max3110.h > @@ -0,0 +1,16 @@ > +#ifndef _LINUX_SERIAL_MAX3110_H > +#define _LINUX_SERIAL_MAX3110_H > + > +/** > + * struct plat_max3110 - MAX3110 SPI UART platform data > + * @irq_edge_trigger: if IRQ is edge triggered > + * > + * You should use this structure in your machine description to specify > + * how the MAX3110 is connected. > + * > + */ > +struct plat_max3110 { > + int irq_edge_triggered; > +}; > + > +#endif > -- Is just resource->flags for IRQ can be reused for handle such case? --- ????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?