2016-03-02 11:38:40 +01:00
|
|
|
/*
|
|
|
|
* This file is part of the coreboot project.
|
|
|
|
*
|
|
|
|
* Copyright 2016 Rockchip Inc.
|
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or modify
|
|
|
|
* it under the terms of the GNU General Public License as published by
|
|
|
|
* the Free Software Foundation; version 2 of the License.
|
|
|
|
*
|
|
|
|
* This program is distributed in the hope that it will be useful,
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
* GNU General Public License for more details.
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
|
2016-04-22 21:25:07 +02:00
|
|
|
#include <boardid.h>
|
2016-03-31 12:44:13 +02:00
|
|
|
#include <delay.h>
|
2016-03-02 11:38:40 +01:00
|
|
|
#include <device/device.h>
|
2016-03-31 12:44:13 +02:00
|
|
|
#include <device/i2c.h>
|
2016-03-28 09:44:54 +02:00
|
|
|
#include <gpio.h>
|
2016-05-17 09:45:53 +02:00
|
|
|
#include <soc/bl31_plat_params.h>
|
2016-03-28 09:44:54 +02:00
|
|
|
#include <soc/clock.h>
|
2016-03-31 12:44:13 +02:00
|
|
|
#include <soc/display.h>
|
2016-03-28 09:44:54 +02:00
|
|
|
#include <soc/grf.h>
|
2016-03-31 12:44:13 +02:00
|
|
|
#include <soc/i2c.h>
|
2016-05-26 10:06:58 +02:00
|
|
|
#include <soc/usb.h>
|
2016-06-20 00:09:21 +02:00
|
|
|
#include <vendorcode/google/chromeos/chromeos.h>
|
2016-03-28 09:44:54 +02:00
|
|
|
|
2016-05-23 00:53:37 +02:00
|
|
|
#include "board.h"
|
|
|
|
|
2016-09-22 03:16:54 +02:00
|
|
|
/*
|
|
|
|
* Wifi's PDN/RST line is pulled down by its (unpowered) voltage rails, but
|
|
|
|
* this reset pin is pulled up by default. Let's drive it low as early as we
|
|
|
|
* can.
|
|
|
|
*/
|
|
|
|
static void deassert_wifi_power(void)
|
|
|
|
{
|
|
|
|
gpio_output(GPIO(1, B, 3), 0); /* Assert WLAN_MODULE_RST# */
|
|
|
|
}
|
|
|
|
|
2016-04-08 12:56:20 +02:00
|
|
|
static void configure_emmc(void)
|
|
|
|
{
|
|
|
|
/* Host controller does not support programmable clock generator.
|
|
|
|
* If we don't do this setting, when we use phy to control the
|
|
|
|
* emmc clock(when clock exceed 50MHz), it will get wrong clock.
|
|
|
|
*
|
|
|
|
* Refer to TRM V0.3 Part 1 Chapter 15 PAGE 782 for this register.
|
|
|
|
* Please search "_CON11[7:0]" to locate register description.
|
|
|
|
*/
|
|
|
|
write32(&rk3399_grf->emmccore_con[11], RK_CLRSETBITS(0xff, 0));
|
|
|
|
|
|
|
|
rkclk_configure_emmc();
|
|
|
|
}
|
|
|
|
|
2016-08-31 00:34:42 +02:00
|
|
|
static void register_apio_suspend(void)
|
|
|
|
{
|
|
|
|
static struct bl31_apio_param param_apio = {
|
|
|
|
.h = {
|
|
|
|
.type = PARAM_SUSPEND_APIO,
|
|
|
|
},
|
|
|
|
.apio = {
|
|
|
|
.apio1 = 1,
|
|
|
|
.apio2 = 1,
|
|
|
|
.apio3 = 1,
|
|
|
|
.apio4 = 1,
|
|
|
|
.apio5 = 1,
|
|
|
|
},
|
|
|
|
};
|
|
|
|
register_bl31_param(¶m_apio.h);
|
|
|
|
}
|
|
|
|
|
2016-08-23 02:35:40 +02:00
|
|
|
static void register_gpio_suspend(void)
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
* These three GPIO params are used to shut down the 1.5V, 1.8V and
|
|
|
|
* 3.3V power rails, which need to be shut down ordered by voltage,
|
|
|
|
* with highest voltage first.
|
|
|
|
* Since register_bl31() appends to the front of the list, we need to
|
|
|
|
* register them backwards, with 1.5V coming first.
|
|
|
|
*/
|
|
|
|
static struct bl31_gpio_param param_p15_en = {
|
|
|
|
.h = {
|
|
|
|
.type = PARAM_SUSPEND_GPIO,
|
|
|
|
},
|
|
|
|
.gpio = {
|
|
|
|
.polarity = BL31_GPIO_LEVEL_LOW,
|
|
|
|
},
|
|
|
|
};
|
|
|
|
param_p15_en.gpio.index = GET_GPIO_NUM(GPIO_P15V_EN);
|
|
|
|
register_bl31_param(¶m_p15_en.h);
|
|
|
|
|
|
|
|
static struct bl31_gpio_param param_p18_audio_en = {
|
|
|
|
.h = {
|
|
|
|
.type = PARAM_SUSPEND_GPIO,
|
|
|
|
},
|
|
|
|
.gpio = {
|
|
|
|
.polarity = BL31_GPIO_LEVEL_LOW,
|
|
|
|
},
|
|
|
|
};
|
|
|
|
param_p18_audio_en.gpio.index = GET_GPIO_NUM(GPIO_P18V_AUDIO_PWREN);
|
|
|
|
register_bl31_param(¶m_p18_audio_en.h);
|
|
|
|
|
|
|
|
static struct bl31_gpio_param param_p30_en = {
|
|
|
|
.h = {
|
|
|
|
.type = PARAM_SUSPEND_GPIO,
|
|
|
|
},
|
|
|
|
.gpio = {
|
|
|
|
.polarity = BL31_GPIO_LEVEL_LOW,
|
|
|
|
},
|
|
|
|
};
|
|
|
|
param_p30_en.gpio.index = GET_GPIO_NUM(GPIO_P30V_EN);
|
|
|
|
register_bl31_param(¶m_p30_en.h);
|
|
|
|
}
|
|
|
|
|
2016-05-17 09:45:53 +02:00
|
|
|
static void register_reset_to_bl31(void)
|
|
|
|
{
|
|
|
|
static struct bl31_gpio_param param_reset = {
|
|
|
|
.h = {
|
|
|
|
.type = PARAM_RESET,
|
|
|
|
},
|
|
|
|
.gpio = {
|
|
|
|
.polarity = 1,
|
|
|
|
},
|
|
|
|
};
|
|
|
|
|
|
|
|
/* gru/kevin reset pin: gpio0b3 */
|
|
|
|
param_reset.gpio.index = GET_GPIO_NUM(GPIO_RESET),
|
|
|
|
|
|
|
|
register_bl31_param(¶m_reset.h);
|
|
|
|
}
|
|
|
|
|
2016-05-19 05:11:23 +02:00
|
|
|
static void register_poweroff_to_bl31(void)
|
|
|
|
{
|
|
|
|
static struct bl31_gpio_param param_poweroff = {
|
|
|
|
.h = {
|
|
|
|
.type = PARAM_POWEROFF,
|
|
|
|
},
|
|
|
|
.gpio = {
|
|
|
|
.polarity = 1,
|
|
|
|
},
|
|
|
|
};
|
|
|
|
|
|
|
|
/*
|
|
|
|
* gru/kevin power off pin: gpio1a6,
|
|
|
|
* reuse with tsadc int pin, so iomux need set back to
|
|
|
|
* gpio in BL31 and depthcharge before you setting this gpio
|
|
|
|
*/
|
|
|
|
param_poweroff.gpio.index = GET_GPIO_NUM(GPIO_POWEROFF),
|
|
|
|
|
|
|
|
register_bl31_param(¶m_poweroff.h);
|
|
|
|
}
|
|
|
|
|
2016-03-28 09:44:54 +02:00
|
|
|
static void configure_sdmmc(void)
|
|
|
|
{
|
|
|
|
gpio_output(GPIO(4, D, 5), 1); /* SDMMC_PWR_EN */
|
|
|
|
gpio_output(GPIO(2, A, 2), 1); /* SDMMC_SDIO_PWR_EN */
|
2016-05-11 09:03:44 +02:00
|
|
|
|
|
|
|
/* SDMMC_DET_L is different on Kevin board revision 0. */
|
|
|
|
if (IS_ENABLED(CONFIG_BOARD_GOOGLE_KEVIN) && (board_id() == 0))
|
2016-04-22 21:25:07 +02:00
|
|
|
gpio_input(GPIO(4, D, 2));
|
2016-05-11 09:03:44 +02:00
|
|
|
else
|
2016-04-22 21:25:07 +02:00
|
|
|
gpio_input(GPIO(4, D, 0));
|
2016-05-11 09:03:44 +02:00
|
|
|
|
2016-03-28 09:44:54 +02:00
|
|
|
gpio_output(GPIO(2, D, 4), 0); /* Keep the max voltage */
|
2016-04-22 21:25:07 +02:00
|
|
|
|
2016-09-02 20:25:56 +02:00
|
|
|
gpio_input(GPIO(4, B, 0)); /* SDMMC0_D0 remove pull-up */
|
|
|
|
gpio_input(GPIO(4, B, 1)); /* SDMMC0_D1 remove pull-up */
|
|
|
|
gpio_input(GPIO(4, B, 2)); /* SDMMC0_D2 remove pull-up */
|
|
|
|
gpio_input(GPIO(4, B, 3)); /* SDMMC0_D3 remove pull-up */
|
|
|
|
gpio_input(GPIO(4, B, 4)); /* SDMMC0_CLK remove pull-down */
|
|
|
|
gpio_input(GPIO(4, B, 5)); /* SDMMC0_CMD remove pull-up */
|
|
|
|
|
2016-05-12 10:54:00 +02:00
|
|
|
write32(&rk3399_grf->gpio2_p[2][1], RK_CLRSETBITS(0xfff, 0));
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Set all outputs' drive strength to 8 mA. Group 4 bank B driver
|
|
|
|
* strength requires three bits per pin. Value of 2 written in that
|
|
|
|
* three bit field means '8 mA', as deduced from the kernel code.
|
|
|
|
*
|
|
|
|
* Thus the six pins involved in SDMMC interface require 18 bits to
|
|
|
|
* configure drive strength, but each 32 bit register provides only 16
|
|
|
|
* bits for this setting, this covers 5 pins fully and one bit from
|
|
|
|
* the 6th pin. Two more bits spill over to the next register. This is
|
|
|
|
* described on page 378 of rk3399 TRM Version 0.3 Part 1.
|
|
|
|
*/
|
|
|
|
write32(&rk3399_grf->gpio4b_e01,
|
|
|
|
RK_CLRSETBITS(0xffff,
|
|
|
|
(2 << 0) | (2 << 3) |
|
|
|
|
(2 << 6) | (2 << 9) | (2 << 12)));
|
|
|
|
write32(&rk3399_grf->gpio4b_e2, RK_CLRSETBITS(3, 1));
|
|
|
|
|
|
|
|
/* And now set the multiplexor to enable SDMMC0. */
|
2016-03-28 09:44:54 +02:00
|
|
|
write32(&rk3399_grf->iomux_sdmmc, IOMUX_SDMMC);
|
|
|
|
}
|
2016-03-02 11:38:40 +01:00
|
|
|
|
2016-05-19 05:39:20 +02:00
|
|
|
static void configure_codec(void)
|
|
|
|
{
|
2016-09-02 20:25:56 +02:00
|
|
|
gpio_input(GPIO(3, D, 0)); /* I2S0_SCLK remove pull-up */
|
|
|
|
gpio_input(GPIO(3, D, 1)); /* I2S0_RX remove pull-up */
|
|
|
|
gpio_input(GPIO(3, D, 2)); /* I2S0_TX remove pull-up */
|
|
|
|
gpio_input(GPIO(3, D, 3)); /* I2S0_SDI0 remove pull-up */
|
|
|
|
gpio_input(GPIO(3, D, 4)); /* I2S0_SDI1 remove pull-up */
|
|
|
|
/* GPIO3_D5 (I2S0_SDI2SDO2) not connected */
|
|
|
|
gpio_input(GPIO(3, D, 6)); /* I2S0_SDO1 remove pull-up */
|
|
|
|
gpio_input(GPIO(3, D, 7)); /* I2S0_SDO0 remove pull-up */
|
|
|
|
gpio_input(GPIO(4, A, 0)); /* I2S0_MCLK remove pull-up */
|
|
|
|
|
2016-05-19 05:39:20 +02:00
|
|
|
write32(&rk3399_grf->iomux_i2s0, IOMUX_I2S0);
|
|
|
|
write32(&rk3399_grf->iomux_i2sclk, IOMUX_I2SCLK);
|
|
|
|
|
|
|
|
/* AUDIO IO domain 1.8V voltage selection */
|
|
|
|
write32(&rk3399_grf->io_vsel, RK_SETBITS(1 << 1));
|
|
|
|
|
|
|
|
/* CPU1_P1.8V_AUDIO_PWREN for P1.8_AUDIO */
|
|
|
|
gpio_output(GPIO(0, A, 2), 1);
|
|
|
|
|
|
|
|
/* set CPU1_SPK_PA_EN output */
|
|
|
|
gpio_output(GPIO(1, A, 2), 0);
|
|
|
|
|
|
|
|
rkclk_configure_i2s(12288000);
|
|
|
|
}
|
|
|
|
|
2016-03-31 12:44:13 +02:00
|
|
|
static void configure_display(void)
|
|
|
|
{
|
|
|
|
/* set pinmux for edp HPD*/
|
|
|
|
gpio_input_pulldown(GPIO(4, C, 7));
|
|
|
|
write32(&rk3399_grf->iomux_edp_hotplug, IOMUX_EDP_HOTPLUG);
|
|
|
|
|
|
|
|
gpio_output(GPIO(4, D, 3), 1); /* CPU3_EDP_VDDEN for P3.3V_DISP */
|
|
|
|
}
|
|
|
|
|
2016-05-26 10:06:58 +02:00
|
|
|
static void setup_usb(void)
|
|
|
|
{
|
2016-08-16 02:58:05 +02:00
|
|
|
/* A few magic PHY tuning values that improve eye diagram amplitude
|
|
|
|
* and make it extra sure we get reliable communication in firmware. */
|
|
|
|
/* Set max ODT compensation voltage and current tuning reference. */
|
google/gru: Tune USB 2.0 PHY to increase compatibility
When testing USB 2.0 compatibility with different kinds
of USB 2.0 devices on Kevin board, we find that some
USB HDDs (e.g. seagate SRD00F1 1TB HDD) and some smart
phones (e.g. galaxy A5 smart phone) can't be detected.
And according to the error log, this issue is related
to USB 2.0 PHY signal problem.
For the USB HDD, error log is:
[ 592.557724] usb 5-1: new high-speed USB device number 2 using xhci-hcd
[ 592.847735] usb 5-1: new high-speed USB device number 3 using xhci-hcd
[ 593.473720] usb 5-1: new high-speed USB device number 6 using xhci-hcd
[ 594.187717] usb 5-1: new high-speed USB device number 9 using xhci-hcd
[ 595.020717] usb 5-1: new high-speed USB device number 13 using xhci-hcd
[ 595.284730] usb 5-1: new high-speed USB device number 14 using xhci-hcd
[ 595.574816] usb 5-1: new high-speed USB device number 15 using xhci-hcd
The log shows that HDD failed to high-speed handshake.
For the smart phone, error log is:
[ 1145.661625] usb 5-1: new high-speed USB device number 2 using xhci-hcd
[ 1145.771674] usb 5-1: device descriptor read/64, error -71
[ 1145.979752] usb 5-1: device descriptor read/64, error -71
[ 1146.187721] usb 5-1: new high-speed USB device number 3 using xhci-hcd
[ 1146.301754] usb 5-1: device descriptor read/64, error -71
[ 1146.509750] usb 5-1: device descriptor read/64, error -71
[ 1146.717722] usb 5-1: new high-speed USB device number 4 using xhci-hcd
[ 1146.724393] usb 5-1: Device not responding to setup address.
[ 1146.930795] usb 5-1: Device not responding to setup address.
[ 1147.137720] usb 5-1: device not accepting address 4, error -71
[ 1147.246644] usb 5-1: new high-speed USB device number 5 using xhci-hcd
[ 1147.253336] usb 5-1: Device not responding to setup address.
[ 1147.459786] usb 5-1: Device not responding to setup address.
[ 1147.665712] usb 5-1: device not accepting address 5, error -71
[ 1147.671789] usb usb5-port1: unable to enumerate USB device
The log shows that smart phone failed to read device
descriptor, error -71 may be caused by PHY signal problem.
This patch aims to tune USB 2.0 PHY with the following
parameters to support USB HDD, smart phone and some other
potential USB 2.0 devices.
1. Disable the pre-emphasize in chirp state to avoid
high-speed handshake failure.
2. Bypass ODT auto compensation to enable set max driver
strength manually. (Bit[42] of usbphy_ctrl register is
1'b1 for bypass, and Bit[41:37] of usbphy_ctrl register
is 5'b10000 for max driver strength).
3. Bypass ODT auto refresh, and set the max bias current
tuning reference. (Bit[57] of usbphy_ctrl register is
1'b1 for bypass, and Bit[52:50] of usbphy_ctrl register
is 3b'100 for max bias current tuning reference).
We have done the USB 2.0 compliance test and compatibility test
with this patch, it works well.
BRANCH=gru
BUG=chrome-os-partner:59623
TEST=plug/unplug USB HDD or smart phone in Type-C port,
check if they can be detected successfully.
Change-Id: I275c2236b8e469bfd04e9184d007eb095657225e
Signed-off-by: Patrick Georgi <pgeorgi@chromium.org>
Original-Commit-Id: 7735c514d4136978133c2299f2f58da8320bb89f
Original-Change-Id: I4e6c10faa1c03af9880a89afe4731a7065eb1e4e
Original-Signed-off-by: William wu <wulf@rock-chips.com>
Original-Reviewed-on: https://chromium-review.googlesource.com/409856
Original-Commit-Ready: Eddie Cai <eddie.cai.rk@gmail.com>
Original-Tested-by: Cindy Han <cindy.han@samsung.com>
Original-Reviewed-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://review.coreboot.org/17566
Tested-by: build bot (Jenkins)
Reviewed-by: Martin Roth <martinroth@google.com>
2016-11-10 12:34:45 +01:00
|
|
|
write32(&rk3399_grf->usbphy0_ctrl[3], RK_CLRSETBITS(0xfff, 0x2e3));
|
|
|
|
write32(&rk3399_grf->usbphy1_ctrl[3], RK_CLRSETBITS(0xfff, 0x2e3));
|
|
|
|
|
2016-09-29 09:18:41 +02:00
|
|
|
if (IS_ENABLED(CONFIG_BOARD_GOOGLE_KEVIN)) {
|
google/gru: Tune USB 2.0 PHY to increase compatibility
When testing USB 2.0 compatibility with different kinds
of USB 2.0 devices on Kevin board, we find that some
USB HDDs (e.g. seagate SRD00F1 1TB HDD) and some smart
phones (e.g. galaxy A5 smart phone) can't be detected.
And according to the error log, this issue is related
to USB 2.0 PHY signal problem.
For the USB HDD, error log is:
[ 592.557724] usb 5-1: new high-speed USB device number 2 using xhci-hcd
[ 592.847735] usb 5-1: new high-speed USB device number 3 using xhci-hcd
[ 593.473720] usb 5-1: new high-speed USB device number 6 using xhci-hcd
[ 594.187717] usb 5-1: new high-speed USB device number 9 using xhci-hcd
[ 595.020717] usb 5-1: new high-speed USB device number 13 using xhci-hcd
[ 595.284730] usb 5-1: new high-speed USB device number 14 using xhci-hcd
[ 595.574816] usb 5-1: new high-speed USB device number 15 using xhci-hcd
The log shows that HDD failed to high-speed handshake.
For the smart phone, error log is:
[ 1145.661625] usb 5-1: new high-speed USB device number 2 using xhci-hcd
[ 1145.771674] usb 5-1: device descriptor read/64, error -71
[ 1145.979752] usb 5-1: device descriptor read/64, error -71
[ 1146.187721] usb 5-1: new high-speed USB device number 3 using xhci-hcd
[ 1146.301754] usb 5-1: device descriptor read/64, error -71
[ 1146.509750] usb 5-1: device descriptor read/64, error -71
[ 1146.717722] usb 5-1: new high-speed USB device number 4 using xhci-hcd
[ 1146.724393] usb 5-1: Device not responding to setup address.
[ 1146.930795] usb 5-1: Device not responding to setup address.
[ 1147.137720] usb 5-1: device not accepting address 4, error -71
[ 1147.246644] usb 5-1: new high-speed USB device number 5 using xhci-hcd
[ 1147.253336] usb 5-1: Device not responding to setup address.
[ 1147.459786] usb 5-1: Device not responding to setup address.
[ 1147.665712] usb 5-1: device not accepting address 5, error -71
[ 1147.671789] usb usb5-port1: unable to enumerate USB device
The log shows that smart phone failed to read device
descriptor, error -71 may be caused by PHY signal problem.
This patch aims to tune USB 2.0 PHY with the following
parameters to support USB HDD, smart phone and some other
potential USB 2.0 devices.
1. Disable the pre-emphasize in chirp state to avoid
high-speed handshake failure.
2. Bypass ODT auto compensation to enable set max driver
strength manually. (Bit[42] of usbphy_ctrl register is
1'b1 for bypass, and Bit[41:37] of usbphy_ctrl register
is 5'b10000 for max driver strength).
3. Bypass ODT auto refresh, and set the max bias current
tuning reference. (Bit[57] of usbphy_ctrl register is
1'b1 for bypass, and Bit[52:50] of usbphy_ctrl register
is 3b'100 for max bias current tuning reference).
We have done the USB 2.0 compliance test and compatibility test
with this patch, it works well.
BRANCH=gru
BUG=chrome-os-partner:59623
TEST=plug/unplug USB HDD or smart phone in Type-C port,
check if they can be detected successfully.
Change-Id: I275c2236b8e469bfd04e9184d007eb095657225e
Signed-off-by: Patrick Georgi <pgeorgi@chromium.org>
Original-Commit-Id: 7735c514d4136978133c2299f2f58da8320bb89f
Original-Change-Id: I4e6c10faa1c03af9880a89afe4731a7065eb1e4e
Original-Signed-off-by: William wu <wulf@rock-chips.com>
Original-Reviewed-on: https://chromium-review.googlesource.com/409856
Original-Commit-Ready: Eddie Cai <eddie.cai.rk@gmail.com>
Original-Tested-by: Cindy Han <cindy.han@samsung.com>
Original-Reviewed-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://review.coreboot.org/17566
Tested-by: build bot (Jenkins)
Reviewed-by: Martin Roth <martinroth@google.com>
2016-11-10 12:34:45 +01:00
|
|
|
/* Set max pre-emphasis level, only on Kevin PHY0 and PHY1 */
|
|
|
|
write32(&rk3399_grf->usbphy0_ctrl[12],
|
|
|
|
RK_CLRSETBITS(0xffff, 0xa7));
|
|
|
|
write32(&rk3399_grf->usbphy1_ctrl[12],
|
|
|
|
RK_CLRSETBITS(0xffff, 0xa7));
|
|
|
|
|
|
|
|
/* Disable the pre-emphasize in eop state and chirp
|
|
|
|
* state to avoid mis-trigger the disconnect detection
|
|
|
|
* and also avoid high-speed handshake fail */
|
|
|
|
write32(&rk3399_grf->usbphy0_ctrl[0], RK_CLRBITS(0x3));
|
|
|
|
write32(&rk3399_grf->usbphy1_ctrl[0], RK_CLRBITS(0x3));
|
|
|
|
write32(&rk3399_grf->usbphy0_ctrl[13], RK_CLRBITS(0x3));
|
|
|
|
write32(&rk3399_grf->usbphy1_ctrl[13], RK_CLRBITS(0x3));
|
|
|
|
|
|
|
|
/* ODT auto compensation bypass, set max driver strength */
|
|
|
|
write32(&rk3399_grf->usbphy0_ctrl[2],
|
|
|
|
RK_CLRSETBITS(0x7e << 4, 0x60 << 4));
|
|
|
|
write32(&rk3399_grf->usbphy1_ctrl[2],
|
|
|
|
RK_CLRSETBITS(0x7e << 4, 0x60 << 4));
|
|
|
|
|
|
|
|
/* ODT auto refresh bypass, and set the max
|
|
|
|
* bias current tuning reference */
|
|
|
|
write32(&rk3399_grf->usbphy0_ctrl[3],
|
|
|
|
RK_CLRSETBITS(0x21c, 1 << 4));
|
|
|
|
write32(&rk3399_grf->usbphy1_ctrl[3],
|
|
|
|
RK_CLRSETBITS(0x21c, 1 << 4));
|
2016-09-29 09:18:41 +02:00
|
|
|
}
|
2016-08-16 02:58:05 +02:00
|
|
|
|
2016-08-04 04:18:39 +02:00
|
|
|
setup_usb_otg0();
|
|
|
|
setup_usb_otg1();
|
2016-05-26 10:06:58 +02:00
|
|
|
}
|
|
|
|
|
2016-03-02 11:38:40 +01:00
|
|
|
static void mainboard_init(device_t dev)
|
|
|
|
{
|
2016-09-22 03:16:54 +02:00
|
|
|
deassert_wifi_power();
|
2016-03-28 09:44:54 +02:00
|
|
|
configure_sdmmc();
|
2016-04-08 12:56:20 +02:00
|
|
|
configure_emmc();
|
2016-05-19 05:39:20 +02:00
|
|
|
configure_codec();
|
2016-03-31 12:44:13 +02:00
|
|
|
configure_display();
|
2016-05-26 10:06:58 +02:00
|
|
|
setup_usb();
|
2016-05-17 09:45:53 +02:00
|
|
|
register_reset_to_bl31();
|
2016-05-19 05:11:23 +02:00
|
|
|
register_poweroff_to_bl31();
|
2016-08-23 02:35:40 +02:00
|
|
|
register_gpio_suspend();
|
2016-08-31 00:34:42 +02:00
|
|
|
register_apio_suspend();
|
2016-03-31 12:44:13 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
static void enable_backlight_booster(void)
|
|
|
|
{
|
|
|
|
const struct {
|
|
|
|
uint8_t reg;
|
|
|
|
uint8_t value;
|
|
|
|
} i2c_writes[] = {
|
|
|
|
{1, 0x84},
|
|
|
|
{1, 0x85},
|
|
|
|
{0, 0x26}
|
|
|
|
};
|
|
|
|
int i;
|
|
|
|
const int booster_i2c_port = 0;
|
|
|
|
uint8_t i2c_buf[2];
|
|
|
|
struct i2c_seg i2c_command = { .read = 0, .chip = 0x2c,
|
|
|
|
.buf = i2c_buf, .len = sizeof(i2c_buf)
|
|
|
|
};
|
|
|
|
|
|
|
|
/*
|
|
|
|
* This function is called on Gru right after BL_EN is asserted. It
|
|
|
|
* takes time for the switcher chip to come online, let's wait a bit
|
|
|
|
* to let the voltage settle, so that the chip can be accessed.
|
|
|
|
*/
|
|
|
|
udelay(1000);
|
|
|
|
|
2016-09-02 20:25:56 +02:00
|
|
|
gpio_input(GPIO(1, B, 7)); /* I2C0_SDA remove pull_up */
|
|
|
|
gpio_input(GPIO(1, C, 0)); /* I2C0_SCL remove pull_up */
|
|
|
|
|
|
|
|
i2c_init(0, 100*KHz);
|
|
|
|
|
2016-03-31 12:44:13 +02:00
|
|
|
write32(&rk3399_pmugrf->iomux_i2c0_sda, IOMUX_I2C0_SDA);
|
|
|
|
write32(&rk3399_pmugrf->iomux_i2c0_scl, IOMUX_I2C0_SCL);
|
|
|
|
|
|
|
|
for (i = 0; i < ARRAY_SIZE(i2c_writes); i++) {
|
|
|
|
i2c_buf[0] = i2c_writes[i].reg;
|
|
|
|
i2c_buf[1] = i2c_writes[i].value;
|
|
|
|
i2c_transfer(booster_i2c_port, &i2c_command, 1);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
void mainboard_power_on_backlight(void)
|
|
|
|
{
|
|
|
|
gpio_output(GPIO(1, C, 1), 1); /* BL_EN */
|
|
|
|
|
2016-07-30 01:15:04 +02:00
|
|
|
if (IS_ENABLED(CONFIG_BOARD_GOOGLE_GRU) && board_id() == 0)
|
2016-03-31 12:44:13 +02:00
|
|
|
enable_backlight_booster();
|
2016-03-02 11:38:40 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
static void mainboard_enable(device_t dev)
|
|
|
|
{
|
|
|
|
dev->ops->init = &mainboard_init;
|
|
|
|
}
|
|
|
|
|
|
|
|
struct chip_operations mainboard_ops = {
|
|
|
|
.name = CONFIG_MAINBOARD_PART_NUMBER,
|
|
|
|
.enable_dev = mainboard_enable,
|
|
|
|
};
|