From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [PATCH] drivers/char/mem.c: Add /dev/ioports, supporting 16-bit and 32-bit ports Date: Tue, 22 Dec 2015 23:11:37 +0100 Message-ID: <201512222311.37683.arnd@arndb.de> References: <20140509191914.GA7286@jtriplet-mobl1> <201512222256.20580.arnd@arndb.de> <1592CC7D-B2F2-4E8B-BB90-4A20682B1FEE@zytor.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1592CC7D-B2F2-4E8B-BB90-4A20682B1FEE-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org> Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: "H. Peter Anvin" Cc: Santosh Shukla , josh-iaAMLnmF4UmaiuxdJuQwMA@public.gmane.org, Greg Kroah-Hartman , akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org, Linux Kernel Mailing List , linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-api@vger.kernel.org On Tuesday 22 December 2015, H. Peter Anvin wrote: > On that subject, shouldn't we have common infrastructure to deal with memory > mapped I/O ports in the kernel? Or do we have that now? I obviously don't > pay too much attention... We don't have it at the moment, though some of the code that we introduced for arm64 is defined in common code, just not shared with anything else. Changing other architectures over to use this is painful and gains the architectures very little, so I doubt it is going to happen. Arnd From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934026AbbLVWMu (ORCPT ); Tue, 22 Dec 2015 17:12:50 -0500 Received: from mout.kundenserver.de ([212.227.126.130]:51500 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933068AbbLVWMs (ORCPT ); Tue, 22 Dec 2015 17:12:48 -0500 From: Arnd Bergmann To: "H. Peter Anvin" Subject: Re: [PATCH] drivers/char/mem.c: Add /dev/ioports, supporting 16-bit and 32-bit ports Date: Tue, 22 Dec 2015 23:11:37 +0100 User-Agent: KMail/1.12.2 (Linux/3.19.0-27-generic; KDE/4.3.2; x86_64; ; ) Cc: Santosh Shukla , josh@joshtriplett.org, "Greg Kroah-Hartman" , akpm@linux-foundation.org, Linux Kernel Mailing List , linux-api@vger.kernel.org References: <20140509191914.GA7286@jtriplet-mobl1> <201512222256.20580.arnd@arndb.de> <1592CC7D-B2F2-4E8B-BB90-4A20682B1FEE@zytor.com> In-Reply-To: <1592CC7D-B2F2-4E8B-BB90-4A20682B1FEE@zytor.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201512222311.37683.arnd@arndb.de> X-Provags-ID: V03:K0:/pIjEY890xwQtRz1neAf/YDsVXGJMVWVvCxU7OE/YmYBm49s6RI Yv7kRwPj54MZbOG38OMvDcyex+8yaJWqhoBMh99Dj5gou9S/+VsiNB1fGQaonWToY3csg08 mx0sfXgL9k7cqXFq0T1/vFAdJRb/XG5EAr/fyy7Obcx3VKjNY+6p/aWOZx4oqd2nLtj1rES NeNK06SYrSnvUQghm1jlw== X-UI-Out-Filterresults: notjunk:1;V01:K0:UGEZ4fn5ZbQ=:F/THygVlbtZv9aODKvCJ0i FIMKysdcAbe2FCFRbssHAfC4sAIyftj9+Ino9EAqIBdeNwQ3Y7FmHH7Kp2W900joIC3TRNBUD HsUFJmg/FKXB48mWe1osdOJOUqv6Hjur8Nei9+9l3DBxllBpr/vnvdkF8fSQwhmJBY+0oHm/p awFh6cKlI8u8dNT1P42xVBj1rCZeeAh3gpqggT2XPCKq+LoQy6GaZexJ+iIxBSi4eC82CUGs8 cGI6tkzGH4fet4u2YRdOxitOI94KwnAY4JZapLKoRO+7rogLR5QSTT/6xxzOc04MXxbhwR+mq LIS+ve9HnXfN7YxIVXseVhkwczzWRvHopFKy5q+cd9Ltll0KGlaSm/947SdLOzelL5O5X1Jn3 ZRD9vsqyx3Pe6VqluN3CdJrC6caU/okE+QRDwYOw4Kc2gi+iPKRvb4/Ue0iVX4F4DAKV04IVv k2DkntytqSag35L/L6alBrQsp1SXlbz87559i2Kd2d1P8Aethk7Ohm4QNsu2LF2/1E9C1MurU D5KySENs7yaJ4IInxRHiojFmOxeW2lMss4uLMTnQazSLStJBTz/rpiNxhv9rhJqT1jggqH3WF 6t0fZL5E3CL0Od1j1PyBSP4H9P7Auvs/EGORKAzRZzO/Rn9KP3RWBjoMNGxL3mcWqq8G9bIVk v+U9Ae66ms37lAubkhXGZqsQ7BqJwH0EHDcY0/seAHFwA41AQ1lVyMC6dlXbzPk/ijxlr+5Th t/amd3TiWGZlMM1c Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday 22 December 2015, H. Peter Anvin wrote: > On that subject, shouldn't we have common infrastructure to deal with memory > mapped I/O ports in the kernel? Or do we have that now? I obviously don't > pay too much attention... We don't have it at the moment, though some of the code that we introduced for arm64 is defined in common code, just not shared with anything else. Changing other architectures over to use this is painful and gains the architectures very little, so I doubt it is going to happen. Arnd