From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754363Ab3AUNVP (ORCPT ); Mon, 21 Jan 2013 08:21:15 -0500 Received: from kiruna.synopsys.com ([198.182.44.80]:45127 "EHLO kiruna.synopsys.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752612Ab3AUNVN (ORCPT ); Mon, 21 Jan 2013 08:21:13 -0500 Message-ID: <50FD40B3.804@synopsys.com> Date: Mon, 21 Jan 2013 18:50:51 +0530 From: Vineet Gupta User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1 MIME-Version: 1.0 To: Grant Likely CC: Alexey Brodkin , "linux-arch@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Benjamin Herrenschmidt , Michal Simek , "Geert Uytterhoeven" Subject: Query on I/O accessors used by Xilinx SystemACE Driver Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.12.197.205] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Synopsys has Xilinx ML50x boards with our internal FPGA workflows, which we sometimes use for internal development and customer evaluations. In that light Alexey has been working on getting the stock systemACE driver to work with ARC Linux Port. One of things that he wants me to fix is introduce the PPC/m68k/microblaze style in_8, in_le16, .... I/O accessors in ARC port, used specifically by driver. I'm not an expert in that driver or the specific needs of those accessors on respective arches, but was wondering, if it would be possible to convert the driver to use the vanilla IO accessors (read{b,w,l}. Microblaze at least, seem to be defining them as straight wrappers over the standard raw accessors. Ben, Geert could you please comment ? Thx, -Vineet