Difference between revisions of "Qualcomm SOC Mainlining Project"

From eLinux.org
Jump to: navigation, search
(add IRC channel)
Line 60: Line 60:
 
*** Sony maintains this tree by keeping patch sets for individual technology areas or features in separate git branches.  We have an internal tool called 'splash', that is used to integrate the separate branches into a single integration branch (the "next" branch).  This tool is available upon request, if you want to use the same workflow as Sony.
 
*** Sony maintains this tree by keeping patch sets for individual technology areas or features in separate git branches.  We have an internal tool called 'splash', that is used to integrate the separate branches into a single integration branch (the "next" branch).  This tool is available upon request, if you want to use the same workflow as Sony.
 
** Code Aurora git trees: https://www.codeaurora.org/cgit/quic/kernel
 
** Code Aurora git trees: https://www.codeaurora.org/cgit/quic/kernel
 
  
 
=== Other resources ===
 
=== Other resources ===

Revision as of 17:08, 6 June 2014

Here is some information about the Qualcomm SOC mainlining project.

[ this page is currently a stub ]

Project List

List of items that need to be mainlined, or are "in flight" (as of June, 2014):

  • regulators
  • RPM
  • clocks?
  • SOC-specific
    • 8064
    • 8974
  • SOC DT file?
  • USB support
    • USB host mode support for the high-speed port
    • dwc3 (superspeed) USB driver
  • spmi
Feature or Item Person Notes Link
Put Stuff Here Tim space for lots of notes,

including multiple lines, here

link to git branch or e-mail patches, if available, online

[ add links to most recently posted patches] [ add person who is working on each part ]

Specific chips

Not sure what to put in this section:

  • 8974

8064?

Resources

mailing list

IRC channel

You can access the IRC channel from inside a corporate firewall using the web interface.

git trees

  • git trees:
    • Sony github integration ("next") tree: https://github.com/andersson/kernel/tree/next
      • Sony maintains this tree by keeping patch sets for individual technology areas or features in separate git branches. We have an internal tool called 'splash', that is used to integrate the separate branches into a single integration branch (the "next" branch). This tool is available upon request, if you want to use the same workflow as Sony.
    • Code Aurora git trees: https://www.codeaurora.org/cgit/quic/kernel

Other resources

Stakeholders

This is a list of parties who are (or should be) interested in the progress of this work:

  • QualComm
  • Code Aurora Forum
  • Linaro
  • QICC (QualComm Innovation Center)
  • Sony
  • Samsung
  • LG
  • HTC
  • Motorola