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

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

 



On Thu, Aug 15, 2019 at 12:49:51PM -0400, Christopher Friedt wrote:
> Hi List!
> 
> I'm currently using gbridge / tcpip with the
> IID1-simple-gpio-module.mnfs example to hook up a fake module that
> just responds to socket I/O.
> 
> A couple of small changes were required, but everything seems to be
> parsed, bundles, cports are all created.
> 
> However, for some reason, greybus does not seem to automatically bind
> the device to the gb-gpio driver, nor does it probe the device. I only
> see pings after the svc has inserted my fake module and handshake is
> complete.
> 
> 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?

thanks,

greg k-h
_______________________________________________
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