Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754698Ab2KMTZi (ORCPT ); Tue, 13 Nov 2012 14:25:38 -0500 Received: from vsp-authed02.binero.net ([195.74.38.226]:31187 "HELO vsp-authed-03-02.binero.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1752261Ab2KMTZh (ORCPT ); Tue, 13 Nov 2012 14:25:37 -0500 From: Andreas Larsson To: Wolfram Sang , Ben Dooks , Peter Korsgaard Cc: linux-i2c@vger.kernel.org, Grant Likely , devicetree-discuss@lists.ozlabs.org, linux-kernel@vger.kernel.org, software@gaisler.com Subject: [PATCH v3 0/2] i2c: i2c-ocores: Add support for sparc, custom set and get functions, and the GRLIB port of the controller Date: Tue, 13 Nov 2012 20:25:25 +0100 Message-Id: <1352834727-16368-1-git-send-email-andreas@gaisler.com> X-Mailer: git-send-email 1.7.0.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1175 Lines: 29 On sparc, irqs are not present as an IORESOURCE in the struct platform_device representation. By using platform_get_irq instead of platform_get_resource the driver works for sparc. The GRLIB port of the ocores i2c controller needs custom getreg and setreg functions to allow for big endian register access and to deal with the fact that the PRELOW and PREHIGH registers have been merged into one register. Signed-off-by: Andreas Larsson Changes since v2: - Return error from platform_get_irq on error - Trigger usage of the grlib specific functions on compatible property instead of name Andreas Larsson (2): i2c: i2c-ocores: Add irq support for sparc i2c: i2c-ocores: Add support for the GRLIB port of the controller and custom getreg and setreg functions drivers/i2c/busses/i2c-ocores.c | 66 ++++++++++++++++++++++++++++++++++---- 1 files changed, 59 insertions(+), 7 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/