From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcel Ziswiler Subject: Re: [PATCH 2/3] arm: tegra: enable igb, stmpe, i2c chardev, spidev, lm95245, pwm leds Date: Wed, 04 Jun 2014 08:20:59 +0200 Message-ID: <538EBACB.70100@ziswiler.com> References: <39a8704a4c8170d6b0620a1e5e44042eae6d8810.1401665237.git.marcel@ziswiler.com> <538CA24B.1010602@wwwdotorg.org> <538CA635.4050502@ziswiler.com> <20140602221627.GP31751@sirena.org.uk> <538D64FD.2010909@ziswiler.com> <20140603094537.GQ31751@sirena.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20140603094537.GQ31751-GFdadSzt00ze9xe1eoZjHA@public.gmane.org> Sender: linux-tegra-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Mark Brown Cc: Stephen Warren , thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, stefan-XLVq0VzYD2Y@public.gmane.org List-Id: linux-tegra@vger.kernel.org On 06/03/2014 11:45 AM, Mark Brown wrote: > When you say "generic user space access" you are describing a specific > detail of how this device happens to be controlled with your software. No, not at all. In fact I did not even specify neither the exact type of device apart from it being a SPI device nor any property of the software apart from the generic user space access thereof implemented in the Linux kernel. I really don't see any difference to i2c chardev which is already enabled in multi_v7_defconfig. > This is not a description of your hardware, it is a description of how > it is controlled with your current software. Sorry, but I really don't know what you are referring to. It's a pure hardware description of some pins being the SPI bus namely MISO/MOSI and the clock plus an accompanying chip-select pin. I fear for some reason or another you have some affinity against spidev which strikes me odd. Admittedly it is not perfect but it is the only generic SPI user space access currently implemented in the Linux kernel and so far did its job perfectly for many of our customers. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932394AbaFDGWE (ORCPT ); Wed, 4 Jun 2014 02:22:04 -0400 Received: from mout.perfora.net ([74.208.4.194]:54835 "EHLO mout.perfora.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755415AbaFDGWB (ORCPT ); Wed, 4 Jun 2014 02:22:01 -0400 Message-ID: <538EBACB.70100@ziswiler.com> Date: Wed, 04 Jun 2014 08:20:59 +0200 From: Marcel Ziswiler User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Mark Brown CC: Stephen Warren , thierry.reding@gmail.com, linux@arm.linux.org.uk, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org, stefan@agner.ch Subject: Re: [PATCH 2/3] arm: tegra: enable igb, stmpe, i2c chardev, spidev, lm95245, pwm leds References: <39a8704a4c8170d6b0620a1e5e44042eae6d8810.1401665237.git.marcel@ziswiler.com> <538CA24B.1010602@wwwdotorg.org> <538CA635.4050502@ziswiler.com> <20140602221627.GP31751@sirena.org.uk> <538D64FD.2010909@ziswiler.com> <20140603094537.GQ31751@sirena.org.uk> In-Reply-To: <20140603094537.GQ31751@sirena.org.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:kBmjMysnWWJm6WjrLtnBtS4JXldtz2J6Ynb3a2cI49X UbqOFSVyNJaIJyJOmq7lOXousQLXBPJmK1YNJN8UXrARiZ1sj0 aG95EMpAy26PQ20F0yZtYOBklwPVlMnL7yugIMh/RdVMN9CB+t 0qXnoYyzrEunpZ5wY97wgZZn1GtJFUANg/eMim3FM4dqoF6ntt qbu9aX/+HPdmOspB8ZPR0NQt/l5hnwzalAMu2SOIqJByvfOQUc ck4wsiew4QuS0IkndpNhIt8SSUgUdtSSc8KGieumHT+WqfND5T pWCr7fiJHsyZCre1sxYyxhLafsRY8ytXv0RMLL2q3Qbe3Q0zI0 t0B/8CqeaSRfcTLfui9s= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/03/2014 11:45 AM, Mark Brown wrote: > When you say "generic user space access" you are describing a specific > detail of how this device happens to be controlled with your software. No, not at all. In fact I did not even specify neither the exact type of device apart from it being a SPI device nor any property of the software apart from the generic user space access thereof implemented in the Linux kernel. I really don't see any difference to i2c chardev which is already enabled in multi_v7_defconfig. > This is not a description of your hardware, it is a description of how > it is controlled with your current software. Sorry, but I really don't know what you are referring to. It's a pure hardware description of some pins being the SPI bus namely MISO/MOSI and the clock plus an accompanying chip-select pin. I fear for some reason or another you have some affinity against spidev which strikes me odd. Admittedly it is not perfect but it is the only generic SPI user space access currently implemented in the Linux kernel and so far did its job perfectly for many of our customers. From mboxrd@z Thu Jan 1 00:00:00 1970 From: marcel@ziswiler.com (Marcel Ziswiler) Date: Wed, 04 Jun 2014 08:20:59 +0200 Subject: [PATCH 2/3] arm: tegra: enable igb, stmpe, i2c chardev, spidev, lm95245, pwm leds In-Reply-To: <20140603094537.GQ31751@sirena.org.uk> References: <39a8704a4c8170d6b0620a1e5e44042eae6d8810.1401665237.git.marcel@ziswiler.com> <538CA24B.1010602@wwwdotorg.org> <538CA635.4050502@ziswiler.com> <20140602221627.GP31751@sirena.org.uk> <538D64FD.2010909@ziswiler.com> <20140603094537.GQ31751@sirena.org.uk> Message-ID: <538EBACB.70100@ziswiler.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 06/03/2014 11:45 AM, Mark Brown wrote: > When you say "generic user space access" you are describing a specific > detail of how this device happens to be controlled with your software. No, not at all. In fact I did not even specify neither the exact type of device apart from it being a SPI device nor any property of the software apart from the generic user space access thereof implemented in the Linux kernel. I really don't see any difference to i2c chardev which is already enabled in multi_v7_defconfig. > This is not a description of your hardware, it is a description of how > it is controlled with your current software. Sorry, but I really don't know what you are referring to. It's a pure hardware description of some pins being the SPI bus namely MISO/MOSI and the clock plus an accompanying chip-select pin. I fear for some reason or another you have some affinity against spidev which strikes me odd. Admittedly it is not perfect but it is the only generic SPI user space access currently implemented in the Linux kernel and so far did its job perfectly for many of our customers.