From: eric@anholt.net (Eric Anholt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: bcm2837-rpi-3-b: fix pwm1 pin
Date: Fri, 09 Feb 2018 21:28:55 +0000 [thread overview]
Message-ID: <877erlett4.fsf@anholt.net> (raw)
In-Reply-To: <726612883.202327.1514736894033@email.1und1.de>
Stefan Wahren <stefan.wahren@i2se.com> writes:
> Hi Baruch,
>
>> Baruch Siach <baruch@tkos.co.il> hat am 31. Dezember 2017 um 16:12 geschrieben:
>>
>>
>> Raspberry Pi 3 uses GPIO45 for I2C SCL0. pwm1 is on GPIO41. Update the
>> DT description accordingly. Fix the following error that shows when
>> GPIO44 and GPIO45 are configured to I2C:
>>
>> [ 1.751563] pinctrl-bcm2835 3f200000.gpio: pin gpio45 already requested by 3f205000.i2c; cannot claim for 3f20c000.pwm
>> [ 1.762474] pinctrl-bcm2835 3f200000.gpio: pin-45 (3f20c000.pwm) status -22
>> [ 1.775176] pinctrl-bcm2835 3f200000.gpio: could not request pin 45 (gpio45) from group gpio45 on device pinctrl-bcm2835
>> [ 1.786344] bcm2835-pwm 3f20c000.pwm: Error applying setting, reverse things back
>> [ 1.793980] bcm2835-pwm: probe of 3f20c000.pwm failed with error -22
>>
>> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
>> ---
>> arch/arm/boot/dts/bcm2837-rpi-3-b.dts | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/bcm2837-rpi-3-b.dts b/arch/arm/boot/dts/bcm2837-rpi-3-b.dts
>> index a8844d033b3f..b44b3b5af00d 100644
>> --- a/arch/arm/boot/dts/bcm2837-rpi-3-b.dts
>> +++ b/arch/arm/boot/dts/bcm2837-rpi-3-b.dts
>> @@ -60,3 +60,9 @@
>> status = "okay";
>> bus-width = <4>;
>> };
>> +
>> +&pwm {
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&pwm0_gpio40 &pwm1_gpio41>;
>> + status = "okay";
>> +};
>
> thanks for addressing this old issue. Unfortunately this is only a part of the solution. The real problem is the definition of pinctrl in a very common dtsi file (bcm2835-rpi.dtsi). Based on the Firmware dt-blob i created a pin usage map [1], which also shows a potential conflict on RPI Zero W.
>
> So i think we should remove the pwm part from bcm2835-rpi.dtsi and define it on board level like in your patch, but also for the other boards. My suggestion would be the following (based on Firmware):
>
> A Plus -> PWM on pin 40,45
> A -> PWM on pin 40,45
> B Plus -> PWM on pin 40,45
> B Rev 2 -> PWM on pin 40,45
> B -> PWM on pin 40,45
> 2 b -> PWM on pin 40,45
> 3 b -> PWM on pin 40,41
> Zero -> No PWM
> Zero W -> No PWM
>
> But i think we should wait for Eric's opinion.
This seems like a reasonable plan for resolving the boot error. The
alternative I can see would be to drop our pwm pinmux setup, in the
absence of any consumer of pwm trying to use it for some specific
purpose.
(Some day it would be nice to have an analog audio driver using pwm on
these pins, but I'm not volunteering to write that code either)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180209/b5189393/attachment.sig>
prev parent reply other threads:[~2018-02-09 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-31 15:12 [PATCH] ARM: dts: bcm2837-rpi-3-b: fix pwm1 pin Baruch Siach
2017-12-31 16:14 ` Stefan Wahren
2018-02-09 17:01 ` Stefan Wahren
2018-02-09 21:28 ` Eric Anholt [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=877erlett4.fsf@anholt.net \
--to=eric@anholt.net \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.