Difference between revisions of "Qualcomm SOC Mainlining Project"

From eLinux.org
Jump to: navigation, search
(Project List: add data)
(Project List: add more stuff)
Line 6: Line 6:
 
List of items that need to be mainlined, or are "in flight" (as of June, 2014):
 
List of items that need to be mainlined, or are "in flight" (as of June, 2014):
  
* regulators
+
* regulators - Josh Cartwright?, Bjorn Andersson?
 +
* clocks - Stephen Boyd
 
* RPM
 
* RPM
* 8084 clock controller, Georgi Djakov
+
* SD Card Controller - Srinivas Kandagatla
 +
* 8084 clock controller - Georgi Djakov
 +
* dma engine - Andy Gross
 
* SOC-specific
 
* SOC-specific
 
** 8084
 
** 8084
 
** 8974
 
** 8974
* SOC DT file?
+
* SOC DT file? - Kumar Gala?
 
* USB support
 
* USB support
 
** USB host mode for HS port - Tim Bird
 
** USB host mode for HS port - Tim Bird
 
** dwc3 (superspeed) USB driver
 
** dwc3 (superspeed) USB driver
* spmi
+
* spmi - ??
 
*  
 
*  
  
 +
== Project Table ==
 +
This might be too time-consuming to maintain?
 
{|  border="1" cellspacing="0" cellpadding="4"
 
{|  border="1" cellspacing="0" cellpadding="4"
 
|- bgcolor="#c0e0e0"
 
|- bgcolor="#c0e0e0"

Revision as of 17:42, 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 - Josh Cartwright?, Bjorn Andersson?
  • clocks - Stephen Boyd
  • RPM
  • SD Card Controller - Srinivas Kandagatla
  • 8084 clock controller - Georgi Djakov
  • dma engine - Andy Gross
  • SOC-specific
    • 8084
    • 8974
  • SOC DT file? - Kumar Gala?
  • USB support
    • USB host mode for HS port - Tim Bird
    • dwc3 (superspeed) USB driver
  • spmi - ??

Project Table

This might be too time-consuming to maintain?

Feature or Item Person Notes Link Last activity
USB - msm_otg host mode Tim Bird I'm currently working on the pmic_id_irq, which require spmi support.

I got stuck on the DT EPROBE_DEFER support issue.

<no links yet> none yet
SD card controller Srinivas Kandagatla This patch series adds Qualcomm SD Card Controller support in pl180 mmci

driver. QCom SDCC is basically a pl180, but bit more customized, some of the register layouts and offsets are different to the ones mentioned in pl180 datasheet. The plan is to totally remove the standalone SDCC driver drivers/mmc/host/msm_sdcc.* and start using generic mmci driver for all Qualcomm parts, as we get chance to test on other Qcom boards.

http://thread.gmane.org/gmane.linux.ports.arm.msm/7706

https://www.mail-archive.com/linux-arm-msm@vger.kernel.org/msg09059.html

2014-06-02
DT stuff for 8084 Georgi Djakov Adds DT nodes for the APQ8084 global clock controller and serial port. https://www.mail-archive.com/linux-arm-msm@vger.kernel.org/msg09096.html 2014-06-03

[ 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

Status

[Figure out a metric for what remains to be done]

  • brainstorming ideas for metric to measure:
    • # of features out of tree (should be going down)
    • size of diff between latest msm tree and server it was based on? (should be going down)