summaryrefslogtreecommitdiff
path: root/board/makomo/board.h
diff options
context:
space:
mode:
authorTristan Honscheid <honscheid@google.com>2023-01-11 15:01:38 -0700
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>2023-01-12 22:15:17 +0000
commit9a9669c83100f8833d066e8a0e58a561075c3e9f (patch)
tree7b09dcba14576a8a753337238e55b869054cfdbf /board/makomo/board.h
parent493e8606c0f33da752e77f267d08f0e88f841cb6 (diff)
downloadchrome-ec-9a9669c83100f8833d066e8a0e58a561075c3e9f.tar.gz
dts: Remove upstream SHI driver in favor of our own
The upstream commit 3ae105e76b1a47c013d6982a79b3f2fa36b19963 introduces an upstream driver that is conflicting with what we have locally in our device tree by merging in some properties (buffer-rx-size) that we don't have declared in our YAML yet. It also creates a naming conflict with our own `struct shi_reg`. This is blocking downstreaming so delete the device tree nodes introduced by the upstream code for now. Rename our structure to `struct cros_shi_reg`. BUG=None BRANCH=None TEST=Built several boards against Zephyr ToT TEST=./twister -T zephyr/test/drivers/ Signed-off-by: Tristan Honscheid <honscheid@google.com> Cq-Depend: chromium:4155744 Cq-Depend: chromium:4155745 Cq-Depend: chromium:4155746 Change-Id: I3c4b44eaf9692fd0411ef7eee411c1fa0eb1f58e Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/4158571 Tested-by: Tristan Honscheid <honscheid@google.com> Commit-Queue: Tristan Honscheid <honscheid@google.com> Reviewed-by: Keith Short <keithshort@chromium.org> Code-Coverage: Zoss <zoss-cl-coverage@prod.google.com>
Diffstat (limited to 'board/makomo/board.h')
0 files changed, 0 insertions, 0 deletions