From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752699AbaEOLas (ORCPT ); Thu, 15 May 2014 07:30:48 -0400 Received: from rhcavuit02.kulnet.kuleuven.be ([134.58.240.130]:56457 "EHLO cavuit02.kulnet.kuleuven.be" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752463AbaEOLaq (ORCPT ); Thu, 15 May 2014 07:30:46 -0400 X-KULeuven-Envelope-From: bart.tanghe@thomasmore.be X-KULeuven-Scanned: Found to be clean X-KULeuven-ID: 92B681280EF.A1BA4 X-KULeuven-Information: Katholieke Universiteit Leuven Message-ID: <5374A55A.4080906@thomasmore.be> Date: Thu, 15 May 2014 13:30:34 +0200 X-Kuleuven: This mail passed the K.U.Leuven mailcluster From: Bart Tanghe User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Michal Simek , Arnd Bergmann CC: thierry.reding@gmail.com, robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com, ijc+devicetree@hellion.org.uk, galak@codeaurora.org, rob@landley.net, grant.likely@linaro.org, linux-pwm@vger.kernel.org, devicetree@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [rfc]pwm: add xilinx pwm driver References: <1400066773-14393-1-git-send-email-bart.tanghe@thomasmore.be> <4262573.aEBTd7FzV5@wuerfel> <53747FB8.2090706@thomasmore.be> <33a1dbfc-bacb-4804-a83a-9915eca3183b@BY2FFO11FD032.protection.gbl> In-Reply-To: <33a1dbfc-bacb-4804-a83a-9915eca3183b@BY2FFO11FD032.protection.gbl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/15/2014 12:33 PM, Michal Simek wrote: > On 05/15/2014 10:50 AM, Bart Tanghe wrote: >> On 05/15/2014 09:23 AM, Arnd Bergmann wrote: >>> On Wednesday 14 May 2014 13:26:13 Bart Tanghe wrote: >>>> @@ -0,0 +1,20 @@ >>>> +Xilinx PWM controller >>>> + >>>> +Required properties: >>>> +- compatible: should be "xlnx,pwm-xlnx" >>>> +- add a clock source to the description >>>> + >>>> +Examples: >>>> + >>>> + axi_timer_0: timer@42800000 { >>>> + clock-frequency = <100000000>; >>>> + clocks = <&clkc 15>; >>>> + compatible = "xlnx,xlnx-pwm"; >>>> + reg = <0x42800000 0x10000>; >>>> + xlnx,count-width = <0x20>; >>>> + xlnx,gen0-assert = <0x1>; >>>> + xlnx,gen1-assert = <0x1>; >>>> + xlnx,one-timer-only = <0x0>; >>>> + xlnx,trig0-assert = <0x1>; >>>> + xlnx,trig1-assert = <0x1>; >>>> + } ; >>>> >>> >>> It seems you are missing a mandatory "#pwm-cells" property. >>> How is anybody supposed to use this? >>> >>> Arnd >>> >> >> I've added some additional information in the documentation >> >> >> >> Xilinx PWM controller >> >> This driver works together with the Xilinx Axi timer hardware core. >> The core is available for the microblaze, powerpc and arm based Xilinx >> platforms. >> >> The axi timer core is implemented in the pl (programmable logic) of the >> fpga. The amount is user defined. Each core has two timers and one pwm output. > > For PWM you have to have 2 timers but core itself can be configured > to any configuration and I expect that any output has to be used. > > Can you describe me your testing enviroment with zedboard? > Do you use any additional hw or are using just leds or any device > on zedboard? > > Thanks, > Michal > > I'm using the 2 internal timers of the axi_timer core. I've attached the pwm output of the timer core to one of the leds. The generate out0 and generate out1 signals aren't attached. I've added 4 axi timers to the design, so I can use the 4 leds of zedboard to visualize and measure the pwm signal. Regards, Bart