summaryrefslogtreecommitdiff
path: root/board/nautilus
Commit message (Collapse)AuthorAgeFilesLines
* nautilus: Enable CONFIG_BATTERY_HW_PRESENT_CUSTOMFurquan Shaikh2017-11-031-0/+1
| | | | | | | | | | | | | | Similar to poppy, enable CONFIG_BATTERY_HW_PRESENT_CUSTOM for nautilus. BUG=None BRANCH=None TEST=make -j buildall Change-Id: Iba2b17a335fa70495306af181d19fbfacdff9520 Signed-off-by: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/752687 Reviewed-by: Philip Chen <philipchen@chromium.org> Reviewed-by: Nicolas Boichat <drinkcat@chromium.org>
* nautilus: Support keyboard matrixPhilip Chen2017-11-034-35/+13
| | | | | | | | | | | | | | | Also fix the strapping pins for board id. BUG=b:68684486 BRANCH=none TEST=build Nautilus Change-Id: I9e9b5fe73efc85456f87355524de3e7ff7a592fb Signed-off-by: Philip Chen <philipchen@google.com> Reviewed-on: https://chromium-review.googlesource.com/746562 Commit-Ready: Philip Chen <philipchen@chromium.org> Tested-by: Philip Chen <philipchen@chromium.org> Reviewed-by: Shawn N <shawnn@chromium.org>
* charge_manager: Enter safe mode at bootShawn Nematbakhsh2017-11-021-9/+0
| | | | | | | | | | | | | | | | | | | | | | | | Charge port / current selection often needs to be significantly altered when a battery cannot provide sufficient charge, so have charge_manager initially enter safe mode. After a battery with sufficient capacity has been identified, charge manager will leave safe mode, and port / current selection will return to standard rules. BUG=chromium:777596 BRANCH=None TEST=Pass charge_manager unit tests. On kevin, remove battery, attach Apple PD charger, verify safe mode is not exited and device does not brown out. Hot-plug battery and verify safe mode is exited. Next, remove battery, attach to Samus, verify safe mode is not exited and device doesn't brown out. Hot-plug battery, verify that safe mode is exited and no active charge port, due to dual-role exclusion. Change-Id: I7784865750087a037aad8dbbac058b22c77ba6d4 Signed-off-by: Shawn Nematbakhsh <shawnn@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/733954 Commit-Ready: Shawn N <shawnn@chromium.org> Tested-by: Shawn N <shawnn@chromium.org> Reviewed-by: Vincent Palatin <vpalatin@chromium.org>
* chg_ramp: Add charge_is_consuming_full_input_current().Aseda Aboagye2017-11-011-11/+0
| | | | | | | | | | | | | | | | | | | Most boards had an identical implementation for this function, previously known as board_is_consuming_full_charge(). To reduce copy paste, let's just move it to common code. Boards that charge ramp without a battery will have to define their own implementation, but there probably won't be any boards like that in the near future. BUG=None BRANCH=None TEST=make -j buildall Change-Id: Ic99a378ac26dfd35d7d718bf9376eacfa8609166 Signed-off-by: Aseda Aboagye <aaboagye@google.com> Reviewed-on: https://chromium-review.googlesource.com/748919 Commit-Ready: Aseda Aboagye <aaboagye@chromium.org> Tested-by: Aseda Aboagye <aaboagye@chromium.org> Reviewed-by: Shawn N <shawnn@chromium.org>
* poppy/nautilus: Move pmic vr decay enable/disable to suspend/resume hooksFurquan Shaikh2017-10-311-8/+2
| | | | | | | | | | | | | | | | Now that chipset suspend/resume hooks are called only once per S0ix entry/exit, move the calls to enable/disable PMIC VR decay to suspend/resume hooks. BUG=None BRANCH=None TEST=Verified that PMIC VR decay enable/disable are called only once during one S0ix entry/exit. Change-Id: Ie01c083963efeacaf0092927f5778b7c1cebf74f Signed-off-by: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/745981 Reviewed-by: Aaron Durbin <adurbin@chromium.org>
* poppy/nautilus: Increase port80 buffer sizeFurquan Shaikh2017-10-311-0/+4
| | | | | | | | | | | | | | Bump up port80 buffer size to 256. BUG=None BRANCH=None TEST=Verified that all port80 messages from a boot-up or S3 resume are present in port80 history buffer. Change-Id: I76c95f308eaa30cc3789b93e59235a2dac0f632f Signed-off-by: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/747121 Reviewed-by: Aaron Durbin <adurbin@chromium.org>
* nautilus: Correct the year in the headersPhilip Chen2017-10-317-7/+7
| | | | | | | | | | | | | | | This is a 2017 project. BUG=none BRANCH=none TEST=build Nautilus Change-Id: I46db0cd84379f98f3170d4aa426ec58b75f9a129 Signed-off-by: Philip Chen <philipchen@google.com> Reviewed-on: https://chromium-review.googlesource.com/746581 Commit-Ready: Philip Chen <philipchen@chromium.org> Tested-by: Philip Chen <philipchen@chromium.org> Reviewed-by: Nicolas Boichat <drinkcat@chromium.org>
* driver: BMM150: Set max frequency based on repetitions settingGwendal Grignou2017-10-301-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | The compass uses oversampling to produce accurate values. MAX_ODR is functions of the repetitions setting. 80Hz is too high, calculate the frequency based on preset setting. Currently, we use 'SPECIAL' that was calculated for Ryu. BUG=b:68394559 BRANCH=eve,reef,poppy TEST=Check with ectool motionsense info 3 the frequency is around 30Hz. Before: Min Frequency: 781 mHz Max Frequency: 80000 mHz After: Min Frequency: 781 mHz Max Frequency: 29579 mHz Check with AIDA64 the compass is not stuck and return changing values. Fixup of CL/570482 Change-Id: Idcfed1418f59e755e5647d018351c6a7397ffe1b Signed-off-by: Gwendal Grignou <gwendal@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/742146 Reviewed-by: Aseda Aboagye <aaboagye@chromium.org>
* ec: add initial nautilus boardChris Wang2017-10-238-0/+2280
For now use the files from poppy. To be changed later on. BUG=b:66458931 TEST=emerge-nautilus chromeos-ec/make buildall -j Change-Id: If829d7307f834f1f30878934623c0e9ee77b907d Signed-off-by: Chris Wang <chriswang@ami.corp-partner.google.com> Reviewed-on: https://chromium-review.googlesource.com/701996 Commit-Ready: Grace Kao <grace.kao@intel.com> Tested-by: Grace Kao <grace.kao@intel.com> Reviewed-by: Philip Chen <philipchen@chromium.org>
View Lorry Controller Status