1. 15 8月, 2018 2 次提交
  2. 03 8月, 2018 2 次提交
  3. 07 6月, 2018 3 次提交
  4. 20 3月, 2018 1 次提交
  5. 01 3月, 2018 1 次提交
  6. 04 2月, 2018 1 次提交
  7. 27 12月, 2017 1 次提交
  8. 16 12月, 2017 1 次提交
  9. 07 12月, 2017 1 次提交
  10. 10 11月, 2017 1 次提交
  11. 14 6月, 2017 1 次提交
  12. 29 3月, 2017 2 次提交
  13. 15 11月, 2016 1 次提交
  14. 01 11月, 2016 1 次提交
  15. 07 9月, 2016 1 次提交
  16. 28 7月, 2016 1 次提交
  17. 21 3月, 2016 1 次提交
  18. 11 3月, 2016 1 次提交
  19. 04 3月, 2016 2 次提交
  20. 15 2月, 2016 1 次提交
  21. 23 10月, 2015 1 次提交
    • D
      mailbox/omap: Add ti,mbox-send-noirq quirk to fix AM33xx CPU Idle · 8e3c5952
      Dave Gerlach 提交于
      The mailbox framework controls the transmission queue and requires
      either its controller implementations or clients to run the state
      machine for the Tx queue. The OMAP mailbox controller uses a Tx-ready
      interrupt as the equivalent of a Tx-done interrupt to run this Tx
      queue state-machine.
      
      The WkupM3 processor on AM33xx and AM43xx SoCs is used to offload
      certain PM tasks, like doing the necessary operations for Device
      PM suspend/resume or for entering lower c-states during cpuidle.
      
      The CPUIdle on AM33xx requires the messages to be sent without
      having to trigger the Tx-ready interrupts, as the interrupt
      would immediately terminate the CPUIdle operation. Support for
      this has been added by introducing a DT quirk, "ti,mbox-send-noirq"
      and using it to modify the normal OMAP mailbox controller behavior
      on the sub-mailboxes used to communicate with the WkupM3 remote
      processor. This also requires the wkup_m3_ipc driver to adjust
      its mailbox usage logic to run the Tx state machine.
      
      NOTE:
      - AM43xx does not communicate with WkupM3 for CPU Idle, so is
        not affected by this behavior. But, it uses the same IPC driver
        for PM suspend/resume functionality, so requires the quirk as
        well, because of changes to the common wkup_m3_ipc driver.
      Signed-off-by: NDave Gerlach <d-gerlach@ti.com>
      [s-anna@ti.com: revise logic and update comments/patch description]
      Signed-off-by: NSuman Anna <s-anna@ti.com>
      Signed-off-by: NJassi Brar <jaswinder.singh@linaro.org>
      8e3c5952
  22. 17 10月, 2015 1 次提交
  23. 12 6月, 2015 1 次提交
  24. 09 6月, 2015 1 次提交
  25. 17 3月, 2015 1 次提交
  26. 06 2月, 2015 1 次提交
  27. 27 11月, 2014 1 次提交
    • S
      mailbox/omap: adapt to the new mailbox framework · 8841a66a
      Suman Anna 提交于
      The OMAP mailbox driver and its existing clients (remoteproc
      for OMAP4+) are adapted to use the generic mailbox framework.
      
      The main changes for the adaptation are:
        - The tasklet used for Tx is replaced with the state machine from
          the generic mailbox framework. The workqueue used for processing
          the received messages stays intact for minimizing the effects on
          the OMAP mailbox clients.
        - The existing exported client API, omap_mbox_get, omap_mbox_put and
          omap_mbox_send_msg are deleted, as the framework provides equivalent
          functionality. A OMAP-specific omap_mbox_request_channel is added
          though to support non-DT way of requesting mailboxes.
        - The OMAP mailbox driver is integrated with the mailbox framework
          through the proper implementations of mbox_chan_ops, except for
          .last_tx_done and .peek_data. The OMAP mailbox driver does not need
          these ops, as it is completely interrupt driven.
        - The OMAP mailbox driver uses a custom of_xlate controller ops that
          allows phandles for the pargs specifier instead of indexing to avoid
          any channel registration order dependencies.
        - The new framework does not support multiple clients operating on a
          single channel, so the reference counting logic is simplified.
        - The remoteproc driver (current client) is adapted to use the new API.
          The notifier callbacks used within this client is replaced with the
          regular callbacks from the newer framework.
        - The exported OMAP mailbox API are limited to omap_mbox_save_ctx,
          omap_mbox_restore_ctx, omap_mbox_enable_irq & omap_mbox_disable_irq,
          with the signature modified to take in the new mbox_chan handle instead
          of the OMAP specific omap_mbox handle. The first 2 will be removed when
          the OMAP mailbox driver is adapted to runtime_pm. The other exported
          API omap_mbox_request_channel will be removed once existing legacy
          users are converted to DT.
      Signed-off-by: NSuman Anna <s-anna@ti.com>
      Cc: Ohad Ben-Cohen <ohad@wizery.com>
      Signed-off-by: NJassi Brar <jaswinder.singh@linaro.org>
      8841a66a
  28. 08 10月, 2014 1 次提交
  29. 12 9月, 2014 1 次提交