meta-ingrasys: zaius: no longer need to set VDN VOUT_MAX during host boot
This was a requirement only for EVT boards and is no longer needed.
(and no longer works with 4.10 since the kernel driver support was removed)
Signed-off-by: Robert Lippert <rlippert@google.com>
Signed-off-by: Patrick Venture <venture@google.com>
Change-Id: I72b3f1ad20423a997003cfc66e6904d430c2f578
diff --git a/meta-zaius/recipes-phosphor/chassis/avsbus-control/avsbus-enable@.service b/meta-zaius/recipes-phosphor/chassis/avsbus-control/avsbus-enable@.service
index 24aadf5..f0d14d2 100644
--- a/meta-zaius/recipes-phosphor/chassis/avsbus-control/avsbus-enable@.service
+++ b/meta-zaius/recipes-phosphor/chassis/avsbus-control/avsbus-enable@.service
@@ -6,7 +6,6 @@
ConditionPathExists=!/run/openbmc/chassis@%i-on
[Service]
-ExecStart=/usr/bin/env zaius_avsbus.sh vdn_max
ExecStart=/usr/bin/env zaius_avsbus.sh enable
SyslogIdentifier=zaius_avsbus.sh
Type=oneshot
diff --git a/meta-zaius/recipes-phosphor/chassis/avsbus-control/zaius_avsbus.sh b/meta-zaius/recipes-phosphor/chassis/avsbus-control/zaius_avsbus.sh
index d960ba7..57e7f99 100755
--- a/meta-zaius/recipes-phosphor/chassis/avsbus-control/zaius_avsbus.sh
+++ b/meta-zaius/recipes-phosphor/chassis/avsbus-control/zaius_avsbus.sh
@@ -33,14 +33,6 @@
echo 0 > $(echo ${i2c_path}/$1-$(printf "%04x" $2)/hwmon/hwmon*/avs$(printf "%d" $3)_enable)
}
-# Usage: vrm_vout_max_1v1 <bus> <i2c_address> <page>
-# Sets VOUT_MAX to 1.1V
-vrm_vout_max_1v1()
-{
- echo Setting VOUT_MAX=[1.1V] on bus $1 VRM @$2 rail $3...
- echo 1100 > ${i2c_path}/$1-$(printf "%04x" $2)/vout$(printf "%d" $3)_max
-}
-
# Usage: for_each_rail <command>
# <command> will be invoked with <bus> <i2c_address> <page>
for_each_rail()
@@ -60,10 +52,6 @@
elif [ "$1" == "disable" ]
then
for_each_rail vrm_avs_disable
-elif [ "$1" == "vdn_max" ]
-then
- addrs_pages="$vdn_i2c_addr_page"
- for_each_rail vrm_vout_max_1v1
else
echo "\"$0 <enable|disable>\" to control whether VRMs use AVSBus"
echo "\"$0 <vdn_max>\" to set VDN rails VOUT_MAX to 1.1V"