devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Tanghe <bart.tanghe@thomasmore.be>
To: Stephen Warren <swarren@wwwdotorg.org>,
	lee@kernel.org, devicetree@vger.kernel.org
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, linux@arm.linux.org.uk,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH]dts: add bcm2835-pwm bindings
Date: Wed, 14 Jan 2015 09:16:31 +0100	[thread overview]
Message-ID: <54B625DF.4030801@thomasmore.be> (raw)
In-Reply-To: <54B54597.3010508@wwwdotorg.org>

On 01/13/2015 05:19 PM, Stephen Warren wrote:
> On 01/13/2015 08:40 AM, Bart Tanghe wrote:
>> On 01/10/2015 05:38 PM, Stephen Warren wrote:
>>> On 01/05/2015 08:33 AM, Bart Tanghe wrote:
>>>> To probe the bcm2835-pwm driver properly, this dts bindings has to be added
>>>> to the bcm2835 dtsi file.
>>>> In expectation of a bcm2835 clock driver, I've added fixed-clock clock binding.
>>>> To change the status of the gpio pins into pwm output pins, some additional
>>>> bindings has to be added but this has not to be done automatically.
>>>> Is it possible to document this bindings somewhere?
>>>
>>> The pinctrl bindings allow you to do this. They're documented in:
>>>
>>> Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt
>>> Documentation/devicetree/bindings/pinctrl/brcm,bcm2835-gpio.txt
>>>
>>> pinctrl setup would typically be added to the board file (i.e.
>>> arch/arm/boot/dts/bcm2835-rpi-b.dts) rather than the SoC file. I think
>>> on the RPi, the pins that can generate PWM aren't dedicated to PWM by
>>> the RPi board design (they could be GPIOs and probably other functions
>>> too) so we probably need to leave it up to individual users to add PWM
>>> configuration to their DT, if/when they use the PWM feature.
>>>
>>
>> Indeed, the pins aren't dedicated to pwm and can be used for other functions.
>> Is it usefull to add  the pwm pinctrl description to
>> Documentation/devicetree/bindings/pinctrl/brcm,bcm2835-gpio.txt or is this
>> useless?
> 
> As far as I can tell, that file already describes everything required to configure those pins as PWM (or indeed any pins as any function). Can you expand on what you think is missing?
Indeed, everything is described in the file. I thought about a specific pwm pinctrl section but it's the same for i2c and spi. This will just make the file unclear. 
No need to add documentation.

Regards,

Bart

      reply	other threads:[~2015-01-14  8:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 15:33 [PATCH]dts: add bcm2835-pwm bindings Bart Tanghe
2015-01-10 16:38 ` Stephen Warren
2015-01-13 15:40   ` Bart Tanghe
     [not found]     ` <54B53C86.4030903-2dq7lIxLGp5qkBXjtECzWg@public.gmane.org>
2015-01-13 16:19       ` Stephen Warren
2015-01-14  8:16         ` Bart Tanghe [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54B625DF.4030801@thomasmore.be \
    --to=bart.tanghe@thomasmore.be \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=lee@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=swarren@wwwdotorg.org \
    --cc=thierry.reding@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).