/dts-v1/;
/plugin/;
/ {
compatible = "ti,beaglebone", "ti,beaglebone-black";
part-number = "BB-W1";
version = "00A0";
exclusive-use =
"P9.22",
"gpio0_2";
fragment@0 {
target = <&am33xx_pinmux>;
__overlay__ {
dallas_w1_pins: pinmux_dallas_w1_pins {
pinctrl-single,pins = < 0x150 0x37 >; };
};
};
fragment@1 {
target = <&ocp>;
__overlay__ {
onewire@0 {
compatible = "w1-gpio";
pinctrl-names = "default";
pinctrl-0 = <&dallas_w1_pins>;
status = "okay";
gpios = <&gpio1 2 0>;
};
};
};
};
On Thu, May 12, 2016 at 11:07 AM, William Hermans <[email protected]> wrote:
> *That's correct, every pin is configured. And the load the driver for
>> PWM, or SPI, or ... but it is not configured to load the OneWire driver for
>> the pin. All of the config-pin options are for standard drivers. The
>> point is, if you want to use the pin to another device that is not a built
>> in device then one needs to do something different.*
>>
>
> How was the pin configured before ? There is no one wire peripheral
> module, so it must have been configured as GPIO. As far as one-wire goes I
> have never used it before, but have read it is basically a modified I2C
> protocol(somehow ).
>
> If I was able to look at the device tree file you use before. Perhaps I
> could offer assistance.
>
> On Thu, May 12, 2016 at 10:38 AM, Ray Madigan <[email protected]>
> wrote:
>
>> That's correct, every pin is configured. And the load the driver for
>> PWM, or SPI, or ... but it is not configured to load the OneWire driver for
>> the pin. All of the config-pin options are for standard drivers. The
>> point is, if you want to use the pin to another device that is not a built
>> in device then one needs to do something different.
>>
>> On Thursday, May 12, 2016 at 10:20:37 AM UTC-7, William Hermans wrote:
>>>
>>> *Because the universal overlay causes my one wire overlay to be
>>>> rejected. The error is File Exists and dmesg points to the conflict with
>>>> the slots entry that has the conflict. I am probably doing something
>>>> wrons, even when I delete the P9_22 from the universal overlay and reapply
>>>> it, it rejects my overlay.*
>>>
>>>
>>> Because the pin is already configured. *Every* pin is configured when
>>> you use universal io. Plus the point of using universal io is so you do not
>>> have to configure the pin through an overlay. So learn how to use universal
>>> io + config-pin to configure the pin.
>>>
>>>
>>> On Thu, May 12, 2016 at 9:05 AM, Ray Madigan <[email protected]>
>>> wrote:
>>>
>>>> Because the universal overlay causes my one wire overlay to be
>>>> rejected. The error is File Exists and dmesg points to the conflict with
>>>> the slots entry that has the conflict. I am probably doing something
>>>> wrons, even when I delete the P9_22 from the universal overlay and reapply
>>>> it, it rejects my overlay.
>>>>
>>>> I am working on this from two perspectives, i need to be able to get
>>>> back to work :). I am building a non universal overlay that will include
>>>> my one wire pin, the pwm pins I need, and others as I work out my
>>>> application. I will use this until I figure out the universal overlay
>>>> issue.
>>>>
>>>> I have never written an overlay that uses two pins on the same device,
>>>> I am working that out now.
>>>>
>>>> On Thursday, May 12, 2016 at 8:41:41 AM UTC-7, TJF wrote:
>>>>>
>>>>> Why don't you adapt the 1-wire overlay? It should be easy to use a pin
>>>>> not connected to any PWMSS. Ie. use P9_11 or P8_07.
>>>>>
>>>> --
>>>> For more options, visit http://beagleboard.org/discuss
>>>> ---
>>>> You received this message because you are subscribed to the Google
>>>> Groups "BeagleBoard" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to [email protected].
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/beagleboard/5dc3979a-1d78-45d1-82d0-dea8b8004a14%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/beagleboard/5dc3979a-1d78-45d1-82d0-dea8b8004a14%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beagleboard/b53b6116-848f-4e97-8f68-34164f115300%40googlegroups.com
>> <https://groups.google.com/d/msgid/beagleboard/b53b6116-848f-4e97-8f68-34164f115300%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/1iSthWho2yE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CALHSORrbbScPNEEN4KAop8KJ9S5NmOLqZ633ig%2BTjXhe9UAvNg%40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CALHSORrbbScPNEEN4KAop8KJ9S5NmOLqZ633ig%2BTjXhe9UAvNg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/CAEKowXD4Q%3D92CM9weewehbwGUes%2B_nqz4pjjxoEewuxaWMf29Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
