Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 08 2月, 2021 1 次提交
  3. 22 1月, 2021 1 次提交
  5. 15 1月, 2021 1 次提交
  7. 05 1月, 2021 1 次提交
  9. 04 1月, 2021 1 次提交
  11. 30 12月, 2020 1 次提交
  13. 28 12月, 2020 2 次提交
  15. 11 12月, 2020 1 次提交
  17. 01 12月, 2020 1 次提交
  19. 30 11月, 2020 1 次提交
  21. 24 11月, 2020 2 次提交
    • J
      regulator: Kconfig: Fix REGULATOR_QCOM_RPMH dependencies to avoid build error · 34c5aa26
      由 John Stultz 提交于 
      The kernel test robot reported the following build error:

All errors (new ones prefixed by >>):

   xtensa-linux-ld: drivers/regulator/qcom-rpmh-regulator.o: in function `rpmh_regulator_vrm_get_voltage_sel':
   qcom-rpmh-regulator.c:(.text+0x270): undefined reference to `rpmh_write'
   xtensa-linux-ld: drivers/regulator/qcom-rpmh-regulator.o: in function `rpmh_regulator_send_request':
   qcom-rpmh-regulator.c:(.text+0x2f2): undefined reference to `rpmh_write'
   xtensa-linux-ld: drivers/regulator/qcom-rpmh-regulator.o: in function `rpmh_regulator_vrm_get_voltage_sel':
>> qcom-rpmh-regulator.c:(.text+0x274): undefined reference to `rpmh_write_async'
   xtensa-linux-ld: drivers/regulator/qcom-rpmh-regulator.o: in function `rpmh_regulator_send_request':
   qcom-rpmh-regulator.c:(.text+0x2fc): undefined reference to `rpmh_write_async'

Which is due to REGULATOR_QCOM_RPMH depending on
QCOM_RPMH || COMPILE_TEST. The problem is that QOM_RPMH can now
be a module, which in that case requires REGULATOR_QCOM_RPMH=m
to build.

However, if COMPILE_TEST is enabled, REGULATOR_QCOM_RPMH can be
set to =y while QCOM_RPMH=m which will cause build failures.

The fix here is to add (QCOM_RPMH=n && COMPILE_TEST) to the
dependency.

Feedback would be appreciated!

Cc: Todd Kjos <tkjos@google.com>
Cc: Saravana Kannan <saravanak@google.com>
Cc: Andy Gross <agross@kernel.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Rajendra Nayak <rnayak@codeaurora.org>
Cc: Maulik Shah <mkshah@codeaurora.org>
Cc: Stephen Boyd <swboyd@chromium.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>
Cc: Mark Brown <broonie@kernel.org>
Cc: linux-arm-msm@vger.kernel.org
Reported-by: Nkernel test robot <lkp@intel.com>
Signed-off-by: NJohn Stultz <john.stultz@linaro.org>
Reviewed-by: NBjorn Andersson <bjorn.andersson@linaro.org>
Link: https://lore.kernel.org/r/20201123222359.103822-1-john.stultz@linaro.orgSigned-off-by: NMark Brown <broonie@kernel.org>
      34c5aa26
    • C
      regulator: add SCMI driver · 0fbeae70
      由 Cristian Marussi 提交于 
      Add a simple regulator based on SCMI Voltage Domain Protocol.
Signed-off-by: NCristian Marussi <cristian.marussi@arm.com>
----
v6 --> v7
- add proper blank lines between semantic blocks
- fix return value on error path of scmi_reg_is_enabled()
- use generic Failure message on err path of info_get()
- fix comment containing apostrophe

v3 --> v4
- using of_match_full_name core regulator flag
- avoid coccinelle falde complaints about pointer-sized allocations

v2 --> v3
- remove multiple linear mappings support
- removed duplicated voltage name printout
- added a few comments
- simplified return path in scmi_reg_set_voltage_sel()

v1 --> v2
- removed duplicate regulator naming
- removed redundant .get/set_voltage ops: only _sel variants implemented
- removed condexpr on fail path to increase readability

v0 --> v1
- fixed init_data constraint parsing
- fixes for v5.8 (linear_range.h)
- fixed commit message content and subject line format
- factored out SCMI core specific changes to distinct patch
- reworked Kconfig and Makefile to keep proper alphabetic order
- fixed SPDX comment style
- removed unneeded inline functions
- reworked conditionals for legibility
- fixed some return paths to properly report SCMI original errors codes
- added some more descriptive error messages when fw returns invalid ranges
- removed unneeded explicit devm_regulator_unregister from .remove()
Link: https://lore.kernel.org/r/20201123202336.46701-4-cristian.marussi@arm.comSigned-off-by: NMark Brown <broonie@kernel.org>
      0fbeae70
  23. 03 11月, 2020 1 次提交
  25. 29 9月, 2020 1 次提交
  27. 22 9月, 2020 1 次提交
  29. 18 9月, 2020 1 次提交
  31. 26 8月, 2020 1 次提交
  33. 19 8月, 2020 3 次提交
  35. 15 7月, 2020 1 次提交
  37. 07 7月, 2020 1 次提交
  39. 06 7月, 2020 1 次提交
  41. 04 7月, 2020 1 次提交
  43. 02 7月, 2020 2 次提交
  45. 17 6月, 2020 1 次提交
  47. 16 6月, 2020 1 次提交
  49. 09 5月, 2020 1 次提交
  51. 15 4月, 2020 1 次提交
  53. 17 3月, 2020 1 次提交
  55. 02 3月, 2020 1 次提交
  57. 11 2月, 2020 1 次提交
  59. 24 1月, 2020 1 次提交
  61. 13 1月, 2020 1 次提交
  63. 10 1月, 2020 1 次提交
  65. 08 1月, 2020 1 次提交
  67. 17 12月, 2019 1 次提交
  69. 21 11月, 2019 1 次提交