Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

usb gadget on rpi A #324

Closed
prudy opened this issue Mar 11, 2016 · 12 comments
Closed

usb gadget on rpi A #324

prudy opened this issue Mar 11, 2016 · 12 comments

Comments

@prudy
Copy link

@prudy prudy commented Mar 11, 2016

The rpi A could be used in device mode as the rpi Zero model. However as its otgid pin is permanently grounded it must force the HW/SW fixed device mode, not dual/otg.
Currently dwc2 driver gadget does not allow it as the gadget initialization overrides necessary settings.
Moreover, if dwc2 is compiled not in gadget-only but in dual-mode, the device mode must be forced with 'dtoverlay=dwc2,dr_mode=peripheral' in config.txt. Currently setting dr_mode parameter is ignored.
I'll issue the pull request fixing these, so gadgets with dwc2 work on raspberry A.

@francesco-vannini
Copy link

@francesco-vannini francesco-vannini commented May 7, 2016

Prudy is there any workaround to make the A+ work as a peripheral till this is fixed?

@JamesH65
Copy link
Contributor

@JamesH65 JamesH65 commented Mar 2, 2017

@prudy Did you ever supply a PR for this? Cannot find one. Which part of the documentation are you suggesting needs updating?

@prudy
Copy link
Author

@prudy prudy commented Mar 6, 2017

Hi, actually I did not, I solved the problem and sent a patch.
For the documentation - I think the mystery of otg pin routing should be described/explained. All settings go the DeviceTree thus this could be good place. If I'm not wrong some description was already there, the functionality was just broken.

@JamesH65
Copy link
Contributor

@JamesH65 JamesH65 commented Mar 7, 2017

@prudy Do you have a PR number? Will make it easier to dig up.

@prudy
Copy link
Author

@prudy prudy commented Mar 7, 2017

Only the patch mailing list story:
https://lists.gt.net/linux/kernel/2404917

@JamesH65
Copy link
Contributor

@JamesH65 JamesH65 commented Mar 15, 2017

@ghollingworth @pelwell Is there any documentation covering this, if not should we have some. It's out of my knowledge base...

@JamesH65 JamesH65 assigned ghollingworth and pelwell and unassigned prudy Mar 15, 2017
@bennuttall
Copy link
Contributor

@bennuttall bennuttall commented Mar 15, 2017

@JamesH65
Copy link
Contributor

@JamesH65 JamesH65 commented Apr 20, 2017

So, what is actually required here? Do we need some documentation that parallels Ben's linked article?

@JamesH65
Copy link
Contributor

@JamesH65 JamesH65 commented May 12, 2017

I'd really like some confirmation on what needs/remains to be done here. Is there actually something that needs doing, if so what, or can this issue be closed?

@prudy
Copy link
Author

@prudy prudy commented May 12, 2017

James, I raised this ticket to start the process of pulling changes to the code. Sine this is already done in upstream there is no real need of having this opened.

@JamesH65
Copy link
Contributor

@JamesH65 JamesH65 commented May 12, 2017

Ok, this is the documentation repo, so that has confused me. I'll close.

@JamesH65 JamesH65 closed this May 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants
You can’t perform that action at this time.