Re: binding gb gpio device to gb-phy driver?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Christopher,
Just getting back from some time off and catching up with the
greybus movements. I was the guy that have implemented some of the
protocols and maintain/used the gbsim more.

On Thu 15 Aug 2019 at 20:46, Christopher Friedt wrote:
> On Thu, Aug 15, 2019 at 3:39 PM Greg KH <greg@xxxxxxxxx> wrote:
>> On Thu, Aug 15, 2019 at 12:49:51PM -0400, Christopher Friedt wrote:
>> > Is anyone aware if a separate step that is required to bind the device
>> > to the driver?
>> > I've tried
>> >
>> > sudo sh -c 'echo -n 1-2.2.1 > /sys/bus/gbphy/drivers/gpio/bind'
>> >
>> > but that gives me -ENODEV
>>
>> It should "just work" if the manifest signatures match the what the
>> greybus gpio driver expects.
>>
>> Do you get any logging messages in your kernel log when you do this?
>
> The bundle class in the manifest was incorrect. Should have been 0x0a
> (bridged phy) - GPIO protocol is a go ;-)

Great to see someone trying to use it, let me know if you need
anything more and I will try to have more attention to this list.

Cheers,
   Rui
_______________________________________________
greybus-dev mailing list
greybus-dev@xxxxxxxxxxxxxxxx
https://lists.linaro.org/mailman/listinfo/greybus-dev




[Index of Archives]     [Asterisk App Development]     [PJ SIP]     [Gnu Gatekeeper]     [IETF Sipping]     [Info Cyrus]     [ALSA User]     [Fedora Linux Users]     [Linux SCTP]     [DCCP]     [Gimp]     [Yosemite News]     [Deep Creek Hot Springs]     [Yosemite Campsites]     [ISDN Cause Codes]     [Asterisk Books]

  Powered by Linux