ARM: omap-common: Add standard access for board description EEPROM
Several TI EVMs have EEPROM that can contain board description information
such as revision, DDR definition, serial number, etc. In just about all
cases, these EEPROM are on the I2C bus and provides us the opportunity
to centralize the generic operations involved.
The on-board EEPROM on the BeagleBone Black, BeagleBone, AM335x EVM,
AM43x GP EVM, AM57xx-evm, BeagleBoard-X15 share the same format.
However, DRA-7* EVMs, OMAP4SDP use a modified format.
We hence introduce logic which is generic between these platforms
without enforcing any specific format. This allows the boards to use the
relevant format for operations that they might choose.
This module will compile for all TI SoC based boards when
CONFIG_TI_I2C_BOARD_DETECT is enabled to have optimal build times for
platforms that require this support.
It is important to note that this logic is fundamental to the board
configuration process such as DDR configuration which is needed in
SPL, hence cannot be part of the standard u-boot driver model (which
is available later in the process). Hence, to aid efficiency, the
eeprom contents are copied over to SRAM scratchpad memory area at the
first invocation to retrieve data.
To prevent churn with cases such as DRA7, where eeprom format maybe
incompatible, we introduce a generic common format in eeprom which
is made available over accessor functions for usage.
Special handling for BBG1 EEPROM had to be introduced thanks to the
weird eeprom rev contents used.
The follow on patches introduce the use of this library for AM335x,
AM437x, and AM57xx.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Steve Kipisz <s-kipisz2@ti.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
8 years ago
|
|
|
/*
|
|
|
|
|
* Library to support early TI EVM EEPROM handling
|
|
|
|
|
*
|
|
|
|
|
* Copyright (C) 2015-2016 Texas Instruments Incorporated - http://www.ti.com/
|
|
|
|
|
* Lokesh Vutla
|
|
|
|
|
* Steve Kipisz
|
|
|
|
|
*
|
|
|
|
|
* SPDX-License-Identifier: GPL-2.0+
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#include <common.h>
|
|
|
|
|
#include <asm/omap_common.h>
|
|
|
|
|
#include <dm/uclass.h>
|
ARM: omap-common: Add standard access for board description EEPROM
Several TI EVMs have EEPROM that can contain board description information
such as revision, DDR definition, serial number, etc. In just about all
cases, these EEPROM are on the I2C bus and provides us the opportunity
to centralize the generic operations involved.
The on-board EEPROM on the BeagleBone Black, BeagleBone, AM335x EVM,
AM43x GP EVM, AM57xx-evm, BeagleBoard-X15 share the same format.
However, DRA-7* EVMs, OMAP4SDP use a modified format.
We hence introduce logic which is generic between these platforms
without enforcing any specific format. This allows the boards to use the
relevant format for operations that they might choose.
This module will compile for all TI SoC based boards when
CONFIG_TI_I2C_BOARD_DETECT is enabled to have optimal build times for
platforms that require this support.
It is important to note that this logic is fundamental to the board
configuration process such as DDR configuration which is needed in
SPL, hence cannot be part of the standard u-boot driver model (which
is available later in the process). Hence, to aid efficiency, the
eeprom contents are copied over to SRAM scratchpad memory area at the
first invocation to retrieve data.
To prevent churn with cases such as DRA7, where eeprom format maybe
incompatible, we introduce a generic common format in eeprom which
is made available over accessor functions for usage.
Special handling for BBG1 EEPROM had to be introduced thanks to the
weird eeprom rev contents used.
The follow on patches introduce the use of this library for AM335x,
AM437x, and AM57xx.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Steve Kipisz <s-kipisz2@ti.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
8 years ago
|
|
|
#include <i2c.h>
|
|
|
|
|
|
|
|
|
|
#include "board_detect.h"
|
|
|
|
|
|
|
|
|
|
#if defined(CONFIG_DM_I2C_COMPAT)
|
|
|
|
|
/**
|
|
|
|
|
* ti_i2c_set_alen - Set chip's i2c address length
|
|
|
|
|
* @bus_addr - I2C bus number
|
|
|
|
|
* @dev_addr - I2C eeprom id
|
|
|
|
|
* @alen - I2C address length in bytes
|
|
|
|
|
*
|
|
|
|
|
* DM_I2C by default sets the address length to be used to 1. This
|
|
|
|
|
* function allows this address length to be changed to match the
|
|
|
|
|
* eeprom used for board detection.
|
|
|
|
|
*/
|
|
|
|
|
int __maybe_unused ti_i2c_set_alen(int bus_addr, int dev_addr, int alen)
|
|
|
|
|
{
|
|
|
|
|
struct udevice *dev;
|
|
|
|
|
struct udevice *bus;
|
|
|
|
|
int rc;
|
|
|
|
|
|
|
|
|
|
rc = uclass_get_device_by_seq(UCLASS_I2C, bus_addr, &bus);
|
|
|
|
|
if (rc)
|
|
|
|
|
return rc;
|
|
|
|
|
rc = i2c_get_chip(bus, dev_addr, 1, &dev);
|
|
|
|
|
if (rc)
|
|
|
|
|
return rc;
|
|
|
|
|
rc = i2c_set_chip_offset_len(dev, alen);
|
|
|
|
|
if (rc)
|
|
|
|
|
return rc;
|
|
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
|
}
|
|
|
|
|
#else
|
|
|
|
|
int __maybe_unused ti_i2c_set_alen(int bus_addr, int dev_addr, int alen)
|
|
|
|
|
{
|
|
|
|
|
return 0;
|
|
|
|
|
}
|
|
|
|
|
#endif
|
|
|
|
|
|
ARM: omap-common: Add standard access for board description EEPROM
Several TI EVMs have EEPROM that can contain board description information
such as revision, DDR definition, serial number, etc. In just about all
cases, these EEPROM are on the I2C bus and provides us the opportunity
to centralize the generic operations involved.
The on-board EEPROM on the BeagleBone Black, BeagleBone, AM335x EVM,
AM43x GP EVM, AM57xx-evm, BeagleBoard-X15 share the same format.
However, DRA-7* EVMs, OMAP4SDP use a modified format.
We hence introduce logic which is generic between these platforms
without enforcing any specific format. This allows the boards to use the
relevant format for operations that they might choose.
This module will compile for all TI SoC based boards when
CONFIG_TI_I2C_BOARD_DETECT is enabled to have optimal build times for
platforms that require this support.
It is important to note that this logic is fundamental to the board
configuration process such as DDR configuration which is needed in
SPL, hence cannot be part of the standard u-boot driver model (which
is available later in the process). Hence, to aid efficiency, the
eeprom contents are copied over to SRAM scratchpad memory area at the
first invocation to retrieve data.
To prevent churn with cases such as DRA7, where eeprom format maybe
incompatible, we introduce a generic common format in eeprom which
is made available over accessor functions for usage.
Special handling for BBG1 EEPROM had to be introduced thanks to the
weird eeprom rev contents used.
The follow on patches introduce the use of this library for AM335x,
AM437x, and AM57xx.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Steve Kipisz <s-kipisz2@ti.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
8 years ago
|
|
|
/**
|
|
|
|
|
* ti_i2c_eeprom_init - Initialize an i2c bus and probe for a device
|
|
|
|
|
* @i2c_bus: i2c bus number to initialize
|
|
|
|
|
* @dev_addr: Device address to probe for
|
|
|
|
|
*
|
|
|
|
|
* Return: 0 on success or corresponding error on failure.
|
|
|
|
|
*/
|
|
|
|
|
static int __maybe_unused ti_i2c_eeprom_init(int i2c_bus, int dev_addr)
|
|
|
|
|
{
|
|
|
|
|
int rc;
|
|
|
|
|
|
|
|
|
|
if (i2c_bus >= 0) {
|
|
|
|
|
rc = i2c_set_bus_num(i2c_bus);
|
|
|
|
|
if (rc)
|
|
|
|
|
return rc;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return i2c_probe(dev_addr);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* ti_i2c_eeprom_read - Read data from an EEPROM
|
|
|
|
|
* @dev_addr: The device address of the EEPROM
|
|
|
|
|
* @offset: Offset to start reading in the EEPROM
|
|
|
|
|
* @ep: Pointer to a buffer to read into
|
|
|
|
|
* @epsize: Size of buffer
|
|
|
|
|
*
|
|
|
|
|
* Return: 0 on success or corresponding result of i2c_read
|
|
|
|
|
*/
|
|
|
|
|
static int __maybe_unused ti_i2c_eeprom_read(int dev_addr, int offset,
|
|
|
|
|
uchar *ep, int epsize)
|
|
|
|
|
{
|
|
|
|
|
int bus_num, rc, alen;
|
|
|
|
|
|
|
|
|
|
bus_num = i2c_get_bus_num();
|
|
|
|
|
|
|
|
|
|
alen = 2;
|
|
|
|
|
|
|
|
|
|
rc = ti_i2c_set_alen(bus_num, dev_addr, alen);
|
|
|
|
|
if (rc)
|
|
|
|
|
return rc;
|
|
|
|
|
|
|
|
|
|
return i2c_read(dev_addr, offset, alen, ep, epsize);
|
ARM: omap-common: Add standard access for board description EEPROM
Several TI EVMs have EEPROM that can contain board description information
such as revision, DDR definition, serial number, etc. In just about all
cases, these EEPROM are on the I2C bus and provides us the opportunity
to centralize the generic operations involved.
The on-board EEPROM on the BeagleBone Black, BeagleBone, AM335x EVM,
AM43x GP EVM, AM57xx-evm, BeagleBoard-X15 share the same format.
However, DRA-7* EVMs, OMAP4SDP use a modified format.
We hence introduce logic which is generic between these platforms
without enforcing any specific format. This allows the boards to use the
relevant format for operations that they might choose.
This module will compile for all TI SoC based boards when
CONFIG_TI_I2C_BOARD_DETECT is enabled to have optimal build times for
platforms that require this support.
It is important to note that this logic is fundamental to the board
configuration process such as DDR configuration which is needed in
SPL, hence cannot be part of the standard u-boot driver model (which
is available later in the process). Hence, to aid efficiency, the
eeprom contents are copied over to SRAM scratchpad memory area at the
first invocation to retrieve data.
To prevent churn with cases such as DRA7, where eeprom format maybe
incompatible, we introduce a generic common format in eeprom which
is made available over accessor functions for usage.
Special handling for BBG1 EEPROM had to be introduced thanks to the
weird eeprom rev contents used.
The follow on patches introduce the use of this library for AM335x,
AM437x, and AM57xx.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Steve Kipisz <s-kipisz2@ti.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
8 years ago
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* ti_eeprom_string_cleanup() - Handle eeprom programming errors
|
|
|
|
|
* @s: eeprom string (should be NULL terminated)
|
|
|
|
|
*
|
|
|
|
|
* Some Board manufacturers do not add a NULL termination at the
|
|
|
|
|
* end of string, instead some binary information is kludged in, hence
|
|
|
|
|
* convert the string to just printable characters of ASCII chart.
|
|
|
|
|
*/
|
|
|
|
|
static void __maybe_unused ti_eeprom_string_cleanup(char *s)
|
|
|
|
|
{
|
|
|
|
|
int i, l;
|
|
|
|
|
|
|
|
|
|
l = strlen(s);
|
|
|
|
|
for (i = 0; i < l; i++, s++)
|
|
|
|
|
if (*s < ' ' || *s > '~') {
|
|
|
|
|
*s = 0;
|
|
|
|
|
break;
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
__weak void gpi2c_init(void)
|
|
|
|
|
{
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static int __maybe_unused ti_i2c_eeprom_get(int bus_addr, int dev_addr,
|
|
|
|
|
u32 header, u32 size, uint8_t *ep)
|
|
|
|
|
{
|
|
|
|
|
u32 byte, hdr_read;
|
|
|
|
|
int rc;
|
|
|
|
|
|
|
|
|
|
gpi2c_init();
|
|
|
|
|
rc = ti_i2c_eeprom_init(bus_addr, dev_addr);
|
|
|
|
|
if (rc)
|
|
|
|
|
return rc;
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Read the header first then only read the other contents.
|
|
|
|
|
*/
|
|
|
|
|
byte = 2;
|
|
|
|
|
|
|
|
|
|
rc = ti_i2c_set_alen(bus_addr, dev_addr, byte);
|
|
|
|
|
if (rc)
|
|
|
|
|
return rc;
|
|
|
|
|
|
ARM: omap-common: Add standard access for board description EEPROM
Several TI EVMs have EEPROM that can contain board description information
such as revision, DDR definition, serial number, etc. In just about all
cases, these EEPROM are on the I2C bus and provides us the opportunity
to centralize the generic operations involved.
The on-board EEPROM on the BeagleBone Black, BeagleBone, AM335x EVM,
AM43x GP EVM, AM57xx-evm, BeagleBoard-X15 share the same format.
However, DRA-7* EVMs, OMAP4SDP use a modified format.
We hence introduce logic which is generic between these platforms
without enforcing any specific format. This allows the boards to use the
relevant format for operations that they might choose.
This module will compile for all TI SoC based boards when
CONFIG_TI_I2C_BOARD_DETECT is enabled to have optimal build times for
platforms that require this support.
It is important to note that this logic is fundamental to the board
configuration process such as DDR configuration which is needed in
SPL, hence cannot be part of the standard u-boot driver model (which
is available later in the process). Hence, to aid efficiency, the
eeprom contents are copied over to SRAM scratchpad memory area at the
first invocation to retrieve data.
To prevent churn with cases such as DRA7, where eeprom format maybe
incompatible, we introduce a generic common format in eeprom which
is made available over accessor functions for usage.
Special handling for BBG1 EEPROM had to be introduced thanks to the
weird eeprom rev contents used.
The follow on patches introduce the use of this library for AM335x,
AM437x, and AM57xx.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Steve Kipisz <s-kipisz2@ti.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
8 years ago
|
|
|
rc = i2c_read(dev_addr, 0x0, byte, (uint8_t *)&hdr_read, 4);
|
|
|
|
|
if (rc)
|
|
|
|
|
return rc;
|
|
|
|
|
|
|
|
|
|
/* Corrupted data??? */
|
|
|
|
|
if (hdr_read != header) {
|
|
|
|
|
rc = i2c_read(dev_addr, 0x0, byte, (uint8_t *)&hdr_read, 4);
|
|
|
|
|
/*
|
|
|
|
|
* read the eeprom header using i2c again, but use only a
|
|
|
|
|
* 1 byte address (some legacy boards need this..)
|
|
|
|
|
*/
|
|
|
|
|
byte = 1;
|
|
|
|
|
if (rc) {
|
|
|
|
|
rc = ti_i2c_set_alen(bus_addr, dev_addr, byte);
|
|
|
|
|
if (rc)
|
|
|
|
|
return rc;
|
|
|
|
|
|
ARM: omap-common: Add standard access for board description EEPROM
Several TI EVMs have EEPROM that can contain board description information
such as revision, DDR definition, serial number, etc. In just about all
cases, these EEPROM are on the I2C bus and provides us the opportunity
to centralize the generic operations involved.
The on-board EEPROM on the BeagleBone Black, BeagleBone, AM335x EVM,
AM43x GP EVM, AM57xx-evm, BeagleBoard-X15 share the same format.
However, DRA-7* EVMs, OMAP4SDP use a modified format.
We hence introduce logic which is generic between these platforms
without enforcing any specific format. This allows the boards to use the
relevant format for operations that they might choose.
This module will compile for all TI SoC based boards when
CONFIG_TI_I2C_BOARD_DETECT is enabled to have optimal build times for
platforms that require this support.
It is important to note that this logic is fundamental to the board
configuration process such as DDR configuration which is needed in
SPL, hence cannot be part of the standard u-boot driver model (which
is available later in the process). Hence, to aid efficiency, the
eeprom contents are copied over to SRAM scratchpad memory area at the
first invocation to retrieve data.
To prevent churn with cases such as DRA7, where eeprom format maybe
incompatible, we introduce a generic common format in eeprom which
is made available over accessor functions for usage.
Special handling for BBG1 EEPROM had to be introduced thanks to the
weird eeprom rev contents used.
The follow on patches introduce the use of this library for AM335x,
AM437x, and AM57xx.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Steve Kipisz <s-kipisz2@ti.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
8 years ago
|
|
|
rc = i2c_read(dev_addr, 0x0, byte, (uint8_t *)&hdr_read,
|
|
|
|
|
4);
|
|
|
|
|
}
|
ARM: omap-common: Add standard access for board description EEPROM
Several TI EVMs have EEPROM that can contain board description information
such as revision, DDR definition, serial number, etc. In just about all
cases, these EEPROM are on the I2C bus and provides us the opportunity
to centralize the generic operations involved.
The on-board EEPROM on the BeagleBone Black, BeagleBone, AM335x EVM,
AM43x GP EVM, AM57xx-evm, BeagleBoard-X15 share the same format.
However, DRA-7* EVMs, OMAP4SDP use a modified format.
We hence introduce logic which is generic between these platforms
without enforcing any specific format. This allows the boards to use the
relevant format for operations that they might choose.
This module will compile for all TI SoC based boards when
CONFIG_TI_I2C_BOARD_DETECT is enabled to have optimal build times for
platforms that require this support.
It is important to note that this logic is fundamental to the board
configuration process such as DDR configuration which is needed in
SPL, hence cannot be part of the standard u-boot driver model (which
is available later in the process). Hence, to aid efficiency, the
eeprom contents are copied over to SRAM scratchpad memory area at the
first invocation to retrieve data.
To prevent churn with cases such as DRA7, where eeprom format maybe
incompatible, we introduce a generic common format in eeprom which
is made available over accessor functions for usage.
Special handling for BBG1 EEPROM had to be introduced thanks to the
weird eeprom rev contents used.
The follow on patches introduce the use of this library for AM335x,
AM437x, and AM57xx.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Steve Kipisz <s-kipisz2@ti.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
8 years ago
|
|
|
if (rc)
|
|
|
|
|
return rc;
|
|
|
|
|
}
|
|
|
|
|
if (hdr_read != header)
|
|
|
|
|
return -1;
|
|
|
|
|
|
|
|
|
|
rc = i2c_read(dev_addr, 0x0, byte, ep, size);
|
|
|
|
|
if (rc)
|
|
|
|
|
return rc;
|
|
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
int __maybe_unused ti_i2c_eeprom_am_set(const char *name, const char *rev)
|
|
|
|
|
{
|
|
|
|
|
struct ti_common_eeprom *ep;
|
|
|
|
|
|
|
|
|
|
if (!name || !rev)
|
|
|
|
|
return -1;
|
|
|
|
|
|
|
|
|
|
ep = TI_EEPROM_DATA;
|
|
|
|
|
if (ep->header == TI_EEPROM_HEADER_MAGIC)
|
|
|
|
|
goto already_set;
|
|
|
|
|
|
|
|
|
|
/* Set to 0 all fields */
|
|
|
|
|
memset(ep, 0, sizeof(*ep));
|
|
|
|
|
strncpy(ep->name, name, TI_EEPROM_HDR_NAME_LEN);
|
|
|
|
|
strncpy(ep->version, rev, TI_EEPROM_HDR_REV_LEN);
|
|
|
|
|
/* Some dummy serial number to identify the platform */
|
|
|
|
|
strncpy(ep->serial, "0000", TI_EEPROM_HDR_SERIAL_LEN);
|
|
|
|
|
/* Mark it with a valid header */
|
|
|
|
|
ep->header = TI_EEPROM_HEADER_MAGIC;
|
|
|
|
|
|
|
|
|
|
already_set:
|
|
|
|
|
return 0;
|
|
|
|
|
}
|
|
|
|
|
|
ARM: omap-common: Add standard access for board description EEPROM
Several TI EVMs have EEPROM that can contain board description information
such as revision, DDR definition, serial number, etc. In just about all
cases, these EEPROM are on the I2C bus and provides us the opportunity
to centralize the generic operations involved.
The on-board EEPROM on the BeagleBone Black, BeagleBone, AM335x EVM,
AM43x GP EVM, AM57xx-evm, BeagleBoard-X15 share the same format.
However, DRA-7* EVMs, OMAP4SDP use a modified format.
We hence introduce logic which is generic between these platforms
without enforcing any specific format. This allows the boards to use the
relevant format for operations that they might choose.
This module will compile for all TI SoC based boards when
CONFIG_TI_I2C_BOARD_DETECT is enabled to have optimal build times for
platforms that require this support.
It is important to note that this logic is fundamental to the board
configuration process such as DDR configuration which is needed in
SPL, hence cannot be part of the standard u-boot driver model (which
is available later in the process). Hence, to aid efficiency, the
eeprom contents are copied over to SRAM scratchpad memory area at the
first invocation to retrieve data.
To prevent churn with cases such as DRA7, where eeprom format maybe
incompatible, we introduce a generic common format in eeprom which
is made available over accessor functions for usage.
Special handling for BBG1 EEPROM had to be introduced thanks to the
weird eeprom rev contents used.
The follow on patches introduce the use of this library for AM335x,
AM437x, and AM57xx.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Steve Kipisz <s-kipisz2@ti.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
8 years ago
|
|
|
int __maybe_unused ti_i2c_eeprom_am_get(int bus_addr, int dev_addr)
|
|
|
|
|
{
|
|
|
|
|
int rc;
|
|
|
|
|
struct ti_am_eeprom am_ep;
|
|
|
|
|
struct ti_common_eeprom *ep;
|
|
|
|
|
|
|
|
|
|
ep = TI_EEPROM_DATA;
|
|
|
|
|
#ifndef CONFIG_SPL_BUILD
|
ARM: omap-common: Add standard access for board description EEPROM
Several TI EVMs have EEPROM that can contain board description information
such as revision, DDR definition, serial number, etc. In just about all
cases, these EEPROM are on the I2C bus and provides us the opportunity
to centralize the generic operations involved.
The on-board EEPROM on the BeagleBone Black, BeagleBone, AM335x EVM,
AM43x GP EVM, AM57xx-evm, BeagleBoard-X15 share the same format.
However, DRA-7* EVMs, OMAP4SDP use a modified format.
We hence introduce logic which is generic between these platforms
without enforcing any specific format. This allows the boards to use the
relevant format for operations that they might choose.
This module will compile for all TI SoC based boards when
CONFIG_TI_I2C_BOARD_DETECT is enabled to have optimal build times for
platforms that require this support.
It is important to note that this logic is fundamental to the board
configuration process such as DDR configuration which is needed in
SPL, hence cannot be part of the standard u-boot driver model (which
is available later in the process). Hence, to aid efficiency, the
eeprom contents are copied over to SRAM scratchpad memory area at the
first invocation to retrieve data.
To prevent churn with cases such as DRA7, where eeprom format maybe
incompatible, we introduce a generic common format in eeprom which
is made available over accessor functions for usage.
Special handling for BBG1 EEPROM had to be introduced thanks to the
weird eeprom rev contents used.
The follow on patches introduce the use of this library for AM335x,
AM437x, and AM57xx.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Steve Kipisz <s-kipisz2@ti.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
8 years ago
|
|
|
if (ep->header == TI_EEPROM_HEADER_MAGIC)
|
|
|
|
|
return 0; /* EEPROM has already been read */
|
|
|
|
|
#endif
|
ARM: omap-common: Add standard access for board description EEPROM
Several TI EVMs have EEPROM that can contain board description information
such as revision, DDR definition, serial number, etc. In just about all
cases, these EEPROM are on the I2C bus and provides us the opportunity
to centralize the generic operations involved.
The on-board EEPROM on the BeagleBone Black, BeagleBone, AM335x EVM,
AM43x GP EVM, AM57xx-evm, BeagleBoard-X15 share the same format.
However, DRA-7* EVMs, OMAP4SDP use a modified format.
We hence introduce logic which is generic between these platforms
without enforcing any specific format. This allows the boards to use the
relevant format for operations that they might choose.
This module will compile for all TI SoC based boards when
CONFIG_TI_I2C_BOARD_DETECT is enabled to have optimal build times for
platforms that require this support.
It is important to note that this logic is fundamental to the board
configuration process such as DDR configuration which is needed in
SPL, hence cannot be part of the standard u-boot driver model (which
is available later in the process). Hence, to aid efficiency, the
eeprom contents are copied over to SRAM scratchpad memory area at the
first invocation to retrieve data.
To prevent churn with cases such as DRA7, where eeprom format maybe
incompatible, we introduce a generic common format in eeprom which
is made available over accessor functions for usage.
Special handling for BBG1 EEPROM had to be introduced thanks to the
weird eeprom rev contents used.
The follow on patches introduce the use of this library for AM335x,
AM437x, and AM57xx.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Steve Kipisz <s-kipisz2@ti.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
8 years ago
|
|
|
|
|
|
|
|
/* Initialize with a known bad marker for i2c fails.. */
|
|
|
|
|
ep->header = TI_DEAD_EEPROM_MAGIC;
|
|
|
|
|
ep->name[0] = 0x0;
|
|
|
|
|
ep->version[0] = 0x0;
|
|
|
|
|
ep->serial[0] = 0x0;
|
|
|
|
|
ep->config[0] = 0x0;
|
ARM: omap-common: Add standard access for board description EEPROM
Several TI EVMs have EEPROM that can contain board description information
such as revision, DDR definition, serial number, etc. In just about all
cases, these EEPROM are on the I2C bus and provides us the opportunity
to centralize the generic operations involved.
The on-board EEPROM on the BeagleBone Black, BeagleBone, AM335x EVM,
AM43x GP EVM, AM57xx-evm, BeagleBoard-X15 share the same format.
However, DRA-7* EVMs, OMAP4SDP use a modified format.
We hence introduce logic which is generic between these platforms
without enforcing any specific format. This allows the boards to use the
relevant format for operations that they might choose.
This module will compile for all TI SoC based boards when
CONFIG_TI_I2C_BOARD_DETECT is enabled to have optimal build times for
platforms that require this support.
It is important to note that this logic is fundamental to the board
configuration process such as DDR configuration which is needed in
SPL, hence cannot be part of the standard u-boot driver model (which
is available later in the process). Hence, to aid efficiency, the
eeprom contents are copied over to SRAM scratchpad memory area at the
first invocation to retrieve data.
To prevent churn with cases such as DRA7, where eeprom format maybe
incompatible, we introduce a generic common format in eeprom which
is made available over accessor functions for usage.
Special handling for BBG1 EEPROM had to be introduced thanks to the
weird eeprom rev contents used.
The follow on patches introduce the use of this library for AM335x,
AM437x, and AM57xx.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Steve Kipisz <s-kipisz2@ti.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
8 years ago
|
|
|
|
|
|
|
|
rc = ti_i2c_eeprom_get(bus_addr, dev_addr, TI_EEPROM_HEADER_MAGIC,
|
|
|
|
|
sizeof(am_ep), (uint8_t *)&am_ep);
|
|
|
|
|
if (rc)
|
|
|
|
|
return rc;
|
|
|
|
|
|
|
|
|
|
ep->header = am_ep.header;
|
|
|
|
|
strlcpy(ep->name, am_ep.name, TI_EEPROM_HDR_NAME_LEN + 1);
|
|
|
|
|
ti_eeprom_string_cleanup(ep->name);
|
|
|
|
|
|
|
|
|
|
/* BeagleBone Green '1' eeprom, board_rev: 0x1a 0x00 0x00 0x00 */
|
|
|
|
|
if (am_ep.version[0] == 0x1a && am_ep.version[1] == 0x00 &&
|
|
|
|
|
am_ep.version[2] == 0x00 && am_ep.version[3] == 0x00)
|
|
|
|
|
strlcpy(ep->version, "BBG1", TI_EEPROM_HDR_REV_LEN + 1);
|
|
|
|
|
else
|
|
|
|
|
strlcpy(ep->version, am_ep.version, TI_EEPROM_HDR_REV_LEN + 1);
|
|
|
|
|
ti_eeprom_string_cleanup(ep->version);
|
|
|
|
|
strlcpy(ep->serial, am_ep.serial, TI_EEPROM_HDR_SERIAL_LEN + 1);
|
|
|
|
|
ti_eeprom_string_cleanup(ep->serial);
|
|
|
|
|
strlcpy(ep->config, am_ep.config, TI_EEPROM_HDR_CONFIG_LEN + 1);
|
|
|
|
|
ti_eeprom_string_cleanup(ep->config);
|
|
|
|
|
|
|
|
|
|
memcpy(ep->mac_addr, am_ep.mac_addr,
|
|
|
|
|
TI_EEPROM_HDR_NO_OF_MAC_ADDR * TI_EEPROM_HDR_ETH_ALEN);
|
|
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
int __maybe_unused ti_i2c_eeprom_dra7_get(int bus_addr, int dev_addr)
|
|
|
|
|
{
|
|
|
|
|
int rc, offset = 0;
|
|
|
|
|
struct dra7_eeprom dra7_ep;
|
|
|
|
|
struct ti_common_eeprom *ep;
|
|
|
|
|
|
|
|
|
|
ep = TI_EEPROM_DATA;
|
|
|
|
|
#ifndef CONFIG_SPL_BUILD
|
|
|
|
|
if (ep->header == DRA7_EEPROM_HEADER_MAGIC)
|
|
|
|
|
return 0; /* EEPROM has already been read */
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
/* Initialize with a known bad marker for i2c fails.. */
|
|
|
|
|
ep->header = TI_DEAD_EEPROM_MAGIC;
|
|
|
|
|
ep->name[0] = 0x0;
|
|
|
|
|
ep->version[0] = 0x0;
|
|
|
|
|
ep->serial[0] = 0x0;
|
|
|
|
|
ep->config[0] = 0x0;
|
|
|
|
|
ep->emif1_size = 0;
|
|
|
|
|
ep->emif2_size = 0;
|
|
|
|
|
|
|
|
|
|
rc = ti_i2c_eeprom_get(bus_addr, dev_addr, DRA7_EEPROM_HEADER_MAGIC,
|
|
|
|
|
sizeof(dra7_ep), (uint8_t *)&dra7_ep);
|
|
|
|
|
if (rc)
|
|
|
|
|
return rc;
|
|
|
|
|
|
|
|
|
|
ep->header = dra7_ep.header;
|
|
|
|
|
strlcpy(ep->name, dra7_ep.name, TI_EEPROM_HDR_NAME_LEN + 1);
|
|
|
|
|
ti_eeprom_string_cleanup(ep->name);
|
|
|
|
|
|
|
|
|
|
offset = dra7_ep.version_major - 1;
|
|
|
|
|
|
|
|
|
|
/* Rev F is skipped */
|
|
|
|
|
if (offset >= 5)
|
|
|
|
|
offset = offset + 1;
|
|
|
|
|
snprintf(ep->version, TI_EEPROM_HDR_REV_LEN + 1, "%c.%d",
|
|
|
|
|
'A' + offset, dra7_ep.version_minor);
|
|
|
|
|
ti_eeprom_string_cleanup(ep->version);
|
|
|
|
|
ep->emif1_size = (u64)dra7_ep.emif1_size;
|
|
|
|
|
ep->emif2_size = (u64)dra7_ep.emif2_size;
|
|
|
|
|
strlcpy(ep->config, dra7_ep.config, TI_EEPROM_HDR_CONFIG_LEN + 1);
|
|
|
|
|
ti_eeprom_string_cleanup(ep->config);
|
|
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
|
}
|
|
|
|
|
|
ARM: omap-common: Add standard access for board description EEPROM
Several TI EVMs have EEPROM that can contain board description information
such as revision, DDR definition, serial number, etc. In just about all
cases, these EEPROM are on the I2C bus and provides us the opportunity
to centralize the generic operations involved.
The on-board EEPROM on the BeagleBone Black, BeagleBone, AM335x EVM,
AM43x GP EVM, AM57xx-evm, BeagleBoard-X15 share the same format.
However, DRA-7* EVMs, OMAP4SDP use a modified format.
We hence introduce logic which is generic between these platforms
without enforcing any specific format. This allows the boards to use the
relevant format for operations that they might choose.
This module will compile for all TI SoC based boards when
CONFIG_TI_I2C_BOARD_DETECT is enabled to have optimal build times for
platforms that require this support.
It is important to note that this logic is fundamental to the board
configuration process such as DDR configuration which is needed in
SPL, hence cannot be part of the standard u-boot driver model (which
is available later in the process). Hence, to aid efficiency, the
eeprom contents are copied over to SRAM scratchpad memory area at the
first invocation to retrieve data.
To prevent churn with cases such as DRA7, where eeprom format maybe
incompatible, we introduce a generic common format in eeprom which
is made available over accessor functions for usage.
Special handling for BBG1 EEPROM had to be introduced thanks to the
weird eeprom rev contents used.
The follow on patches introduce the use of this library for AM335x,
AM437x, and AM57xx.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Steve Kipisz <s-kipisz2@ti.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
8 years ago
|
|
|
bool __maybe_unused board_ti_is(char *name_tag)
|
|
|
|
|
{
|
|
|
|
|
struct ti_common_eeprom *ep = TI_EEPROM_DATA;
|
|
|
|
|
|
|
|
|
|
if (ep->header == TI_DEAD_EEPROM_MAGIC)
|
|
|
|
|
return false;
|
|
|
|
|
return !strncmp(ep->name, name_tag, TI_EEPROM_HDR_NAME_LEN);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
bool __maybe_unused board_ti_rev_is(char *rev_tag, int cmp_len)
|
|
|
|
|
{
|
|
|
|
|
struct ti_common_eeprom *ep = TI_EEPROM_DATA;
|
|
|
|
|
int l;
|
|
|
|
|
|
|
|
|
|
if (ep->header == TI_DEAD_EEPROM_MAGIC)
|
|
|
|
|
return false;
|
|
|
|
|
|
|
|
|
|
l = cmp_len > TI_EEPROM_HDR_REV_LEN ? TI_EEPROM_HDR_REV_LEN : cmp_len;
|
|
|
|
|
return !strncmp(ep->version, rev_tag, l);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
char * __maybe_unused board_ti_get_rev(void)
|
|
|
|
|
{
|
|
|
|
|
struct ti_common_eeprom *ep = TI_EEPROM_DATA;
|
|
|
|
|
|
|
|
|
|
/* if ep->header == TI_DEAD_EEPROM_MAGIC, this is empty already */
|
ARM: omap-common: Add standard access for board description EEPROM
Several TI EVMs have EEPROM that can contain board description information
such as revision, DDR definition, serial number, etc. In just about all
cases, these EEPROM are on the I2C bus and provides us the opportunity
to centralize the generic operations involved.
The on-board EEPROM on the BeagleBone Black, BeagleBone, AM335x EVM,
AM43x GP EVM, AM57xx-evm, BeagleBoard-X15 share the same format.
However, DRA-7* EVMs, OMAP4SDP use a modified format.
We hence introduce logic which is generic between these platforms
without enforcing any specific format. This allows the boards to use the
relevant format for operations that they might choose.
This module will compile for all TI SoC based boards when
CONFIG_TI_I2C_BOARD_DETECT is enabled to have optimal build times for
platforms that require this support.
It is important to note that this logic is fundamental to the board
configuration process such as DDR configuration which is needed in
SPL, hence cannot be part of the standard u-boot driver model (which
is available later in the process). Hence, to aid efficiency, the
eeprom contents are copied over to SRAM scratchpad memory area at the
first invocation to retrieve data.
To prevent churn with cases such as DRA7, where eeprom format maybe
incompatible, we introduce a generic common format in eeprom which
is made available over accessor functions for usage.
Special handling for BBG1 EEPROM had to be introduced thanks to the
weird eeprom rev contents used.
The follow on patches introduce the use of this library for AM335x,
AM437x, and AM57xx.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Steve Kipisz <s-kipisz2@ti.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
8 years ago
|
|
|
return ep->version;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
char * __maybe_unused board_ti_get_config(void)
|
|
|
|
|
{
|
|
|
|
|
struct ti_common_eeprom *ep = TI_EEPROM_DATA;
|
|
|
|
|
|
|
|
|
|
/* if ep->header == TI_DEAD_EEPROM_MAGIC, this is empty already */
|
ARM: omap-common: Add standard access for board description EEPROM
Several TI EVMs have EEPROM that can contain board description information
such as revision, DDR definition, serial number, etc. In just about all
cases, these EEPROM are on the I2C bus and provides us the opportunity
to centralize the generic operations involved.
The on-board EEPROM on the BeagleBone Black, BeagleBone, AM335x EVM,
AM43x GP EVM, AM57xx-evm, BeagleBoard-X15 share the same format.
However, DRA-7* EVMs, OMAP4SDP use a modified format.
We hence introduce logic which is generic between these platforms
without enforcing any specific format. This allows the boards to use the
relevant format for operations that they might choose.
This module will compile for all TI SoC based boards when
CONFIG_TI_I2C_BOARD_DETECT is enabled to have optimal build times for
platforms that require this support.
It is important to note that this logic is fundamental to the board
configuration process such as DDR configuration which is needed in
SPL, hence cannot be part of the standard u-boot driver model (which
is available later in the process). Hence, to aid efficiency, the
eeprom contents are copied over to SRAM scratchpad memory area at the
first invocation to retrieve data.
To prevent churn with cases such as DRA7, where eeprom format maybe
incompatible, we introduce a generic common format in eeprom which
is made available over accessor functions for usage.
Special handling for BBG1 EEPROM had to be introduced thanks to the
weird eeprom rev contents used.
The follow on patches introduce the use of this library for AM335x,
AM437x, and AM57xx.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Steve Kipisz <s-kipisz2@ti.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
8 years ago
|
|
|
return ep->config;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
char * __maybe_unused board_ti_get_name(void)
|
|
|
|
|
{
|
|
|
|
|
struct ti_common_eeprom *ep = TI_EEPROM_DATA;
|
|
|
|
|
|
|
|
|
|
/* if ep->header == TI_DEAD_EEPROM_MAGIC, this is empty already */
|
ARM: omap-common: Add standard access for board description EEPROM
Several TI EVMs have EEPROM that can contain board description information
such as revision, DDR definition, serial number, etc. In just about all
cases, these EEPROM are on the I2C bus and provides us the opportunity
to centralize the generic operations involved.
The on-board EEPROM on the BeagleBone Black, BeagleBone, AM335x EVM,
AM43x GP EVM, AM57xx-evm, BeagleBoard-X15 share the same format.
However, DRA-7* EVMs, OMAP4SDP use a modified format.
We hence introduce logic which is generic between these platforms
without enforcing any specific format. This allows the boards to use the
relevant format for operations that they might choose.
This module will compile for all TI SoC based boards when
CONFIG_TI_I2C_BOARD_DETECT is enabled to have optimal build times for
platforms that require this support.
It is important to note that this logic is fundamental to the board
configuration process such as DDR configuration which is needed in
SPL, hence cannot be part of the standard u-boot driver model (which
is available later in the process). Hence, to aid efficiency, the
eeprom contents are copied over to SRAM scratchpad memory area at the
first invocation to retrieve data.
To prevent churn with cases such as DRA7, where eeprom format maybe
incompatible, we introduce a generic common format in eeprom which
is made available over accessor functions for usage.
Special handling for BBG1 EEPROM had to be introduced thanks to the
weird eeprom rev contents used.
The follow on patches introduce the use of this library for AM335x,
AM437x, and AM57xx.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Steve Kipisz <s-kipisz2@ti.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
8 years ago
|
|
|
return ep->name;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
void __maybe_unused
|
|
|
|
|
board_ti_get_eth_mac_addr(int index,
|
|
|
|
|
u8 mac_addr[TI_EEPROM_HDR_ETH_ALEN])
|
|
|
|
|
{
|
|
|
|
|
struct ti_common_eeprom *ep = TI_EEPROM_DATA;
|
|
|
|
|
|
|
|
|
|
if (ep->header == TI_DEAD_EEPROM_MAGIC)
|
|
|
|
|
goto fail;
|
|
|
|
|
|
|
|
|
|
if (index < 0 || index >= TI_EEPROM_HDR_NO_OF_MAC_ADDR)
|
|
|
|
|
goto fail;
|
|
|
|
|
|
|
|
|
|
memcpy(mac_addr, ep->mac_addr[index], TI_EEPROM_HDR_ETH_ALEN);
|
|
|
|
|
return;
|
|
|
|
|
|
|
|
|
|
fail:
|
|
|
|
|
memset(mac_addr, 0, TI_EEPROM_HDR_ETH_ALEN);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
u64 __maybe_unused board_ti_get_emif1_size(void)
|
|
|
|
|
{
|
|
|
|
|
struct ti_common_eeprom *ep = TI_EEPROM_DATA;
|
|
|
|
|
|
|
|
|
|
if (ep->header != DRA7_EEPROM_HEADER_MAGIC)
|
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
|
|
return ep->emif1_size;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
u64 __maybe_unused board_ti_get_emif2_size(void)
|
|
|
|
|
{
|
|
|
|
|
struct ti_common_eeprom *ep = TI_EEPROM_DATA;
|
|
|
|
|
|
|
|
|
|
if (ep->header != DRA7_EEPROM_HEADER_MAGIC)
|
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
|
|
return ep->emif2_size;
|
|
|
|
|
}
|
|
|
|
|
|
ARM: omap-common: Add standard access for board description EEPROM
Several TI EVMs have EEPROM that can contain board description information
such as revision, DDR definition, serial number, etc. In just about all
cases, these EEPROM are on the I2C bus and provides us the opportunity
to centralize the generic operations involved.
The on-board EEPROM on the BeagleBone Black, BeagleBone, AM335x EVM,
AM43x GP EVM, AM57xx-evm, BeagleBoard-X15 share the same format.
However, DRA-7* EVMs, OMAP4SDP use a modified format.
We hence introduce logic which is generic between these platforms
without enforcing any specific format. This allows the boards to use the
relevant format for operations that they might choose.
This module will compile for all TI SoC based boards when
CONFIG_TI_I2C_BOARD_DETECT is enabled to have optimal build times for
platforms that require this support.
It is important to note that this logic is fundamental to the board
configuration process such as DDR configuration which is needed in
SPL, hence cannot be part of the standard u-boot driver model (which
is available later in the process). Hence, to aid efficiency, the
eeprom contents are copied over to SRAM scratchpad memory area at the
first invocation to retrieve data.
To prevent churn with cases such as DRA7, where eeprom format maybe
incompatible, we introduce a generic common format in eeprom which
is made available over accessor functions for usage.
Special handling for BBG1 EEPROM had to be introduced thanks to the
weird eeprom rev contents used.
The follow on patches introduce the use of this library for AM335x,
AM437x, and AM57xx.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Steve Kipisz <s-kipisz2@ti.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
8 years ago
|
|
|
void __maybe_unused set_board_info_env(char *name)
|
|
|
|
|
{
|
|
|
|
|
char *unknown = "unknown";
|
|
|
|
|
struct ti_common_eeprom *ep = TI_EEPROM_DATA;
|
|
|
|
|
|
|
|
|
|
if (name)
|
|
|
|
|
env_set("board_name", name);
|
ARM: omap-common: Add standard access for board description EEPROM
Several TI EVMs have EEPROM that can contain board description information
such as revision, DDR definition, serial number, etc. In just about all
cases, these EEPROM are on the I2C bus and provides us the opportunity
to centralize the generic operations involved.
The on-board EEPROM on the BeagleBone Black, BeagleBone, AM335x EVM,
AM43x GP EVM, AM57xx-evm, BeagleBoard-X15 share the same format.
However, DRA-7* EVMs, OMAP4SDP use a modified format.
We hence introduce logic which is generic between these platforms
without enforcing any specific format. This allows the boards to use the
relevant format for operations that they might choose.
This module will compile for all TI SoC based boards when
CONFIG_TI_I2C_BOARD_DETECT is enabled to have optimal build times for
platforms that require this support.
It is important to note that this logic is fundamental to the board
configuration process such as DDR configuration which is needed in
SPL, hence cannot be part of the standard u-boot driver model (which
is available later in the process). Hence, to aid efficiency, the
eeprom contents are copied over to SRAM scratchpad memory area at the
first invocation to retrieve data.
To prevent churn with cases such as DRA7, where eeprom format maybe
incompatible, we introduce a generic common format in eeprom which
is made available over accessor functions for usage.
Special handling for BBG1 EEPROM had to be introduced thanks to the
weird eeprom rev contents used.
The follow on patches introduce the use of this library for AM335x,
AM437x, and AM57xx.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Steve Kipisz <s-kipisz2@ti.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
8 years ago
|
|
|
else if (ep->name)
|
|
|
|
|
env_set("board_name", ep->name);
|
ARM: omap-common: Add standard access for board description EEPROM
Several TI EVMs have EEPROM that can contain board description information
such as revision, DDR definition, serial number, etc. In just about all
cases, these EEPROM are on the I2C bus and provides us the opportunity
to centralize the generic operations involved.
The on-board EEPROM on the BeagleBone Black, BeagleBone, AM335x EVM,
AM43x GP EVM, AM57xx-evm, BeagleBoard-X15 share the same format.
However, DRA-7* EVMs, OMAP4SDP use a modified format.
We hence introduce logic which is generic between these platforms
without enforcing any specific format. This allows the boards to use the
relevant format for operations that they might choose.
This module will compile for all TI SoC based boards when
CONFIG_TI_I2C_BOARD_DETECT is enabled to have optimal build times for
platforms that require this support.
It is important to note that this logic is fundamental to the board
configuration process such as DDR configuration which is needed in
SPL, hence cannot be part of the standard u-boot driver model (which
is available later in the process). Hence, to aid efficiency, the
eeprom contents are copied over to SRAM scratchpad memory area at the
first invocation to retrieve data.
To prevent churn with cases such as DRA7, where eeprom format maybe
incompatible, we introduce a generic common format in eeprom which
is made available over accessor functions for usage.
Special handling for BBG1 EEPROM had to be introduced thanks to the
weird eeprom rev contents used.
The follow on patches introduce the use of this library for AM335x,
AM437x, and AM57xx.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Steve Kipisz <s-kipisz2@ti.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
8 years ago
|
|
|
else
|
|
|
|
|
env_set("board_name", unknown);
|
ARM: omap-common: Add standard access for board description EEPROM
Several TI EVMs have EEPROM that can contain board description information
such as revision, DDR definition, serial number, etc. In just about all
cases, these EEPROM are on the I2C bus and provides us the opportunity
to centralize the generic operations involved.
The on-board EEPROM on the BeagleBone Black, BeagleBone, AM335x EVM,
AM43x GP EVM, AM57xx-evm, BeagleBoard-X15 share the same format.
However, DRA-7* EVMs, OMAP4SDP use a modified format.
We hence introduce logic which is generic between these platforms
without enforcing any specific format. This allows the boards to use the
relevant format for operations that they might choose.
This module will compile for all TI SoC based boards when
CONFIG_TI_I2C_BOARD_DETECT is enabled to have optimal build times for
platforms that require this support.
It is important to note that this logic is fundamental to the board
configuration process such as DDR configuration which is needed in
SPL, hence cannot be part of the standard u-boot driver model (which
is available later in the process). Hence, to aid efficiency, the
eeprom contents are copied over to SRAM scratchpad memory area at the
first invocation to retrieve data.
To prevent churn with cases such as DRA7, where eeprom format maybe
incompatible, we introduce a generic common format in eeprom which
is made available over accessor functions for usage.
Special handling for BBG1 EEPROM had to be introduced thanks to the
weird eeprom rev contents used.
The follow on patches introduce the use of this library for AM335x,
AM437x, and AM57xx.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Steve Kipisz <s-kipisz2@ti.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
8 years ago
|
|
|
|
|
|
|
|
if (ep->version)
|
|
|
|
|
env_set("board_rev", ep->version);
|
ARM: omap-common: Add standard access for board description EEPROM
Several TI EVMs have EEPROM that can contain board description information
such as revision, DDR definition, serial number, etc. In just about all
cases, these EEPROM are on the I2C bus and provides us the opportunity
to centralize the generic operations involved.
The on-board EEPROM on the BeagleBone Black, BeagleBone, AM335x EVM,
AM43x GP EVM, AM57xx-evm, BeagleBoard-X15 share the same format.
However, DRA-7* EVMs, OMAP4SDP use a modified format.
We hence introduce logic which is generic between these platforms
without enforcing any specific format. This allows the boards to use the
relevant format for operations that they might choose.
This module will compile for all TI SoC based boards when
CONFIG_TI_I2C_BOARD_DETECT is enabled to have optimal build times for
platforms that require this support.
It is important to note that this logic is fundamental to the board
configuration process such as DDR configuration which is needed in
SPL, hence cannot be part of the standard u-boot driver model (which
is available later in the process). Hence, to aid efficiency, the
eeprom contents are copied over to SRAM scratchpad memory area at the
first invocation to retrieve data.
To prevent churn with cases such as DRA7, where eeprom format maybe
incompatible, we introduce a generic common format in eeprom which
is made available over accessor functions for usage.
Special handling for BBG1 EEPROM had to be introduced thanks to the
weird eeprom rev contents used.
The follow on patches introduce the use of this library for AM335x,
AM437x, and AM57xx.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Steve Kipisz <s-kipisz2@ti.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
8 years ago
|
|
|
else
|
|
|
|
|
env_set("board_rev", unknown);
|
ARM: omap-common: Add standard access for board description EEPROM
Several TI EVMs have EEPROM that can contain board description information
such as revision, DDR definition, serial number, etc. In just about all
cases, these EEPROM are on the I2C bus and provides us the opportunity
to centralize the generic operations involved.
The on-board EEPROM on the BeagleBone Black, BeagleBone, AM335x EVM,
AM43x GP EVM, AM57xx-evm, BeagleBoard-X15 share the same format.
However, DRA-7* EVMs, OMAP4SDP use a modified format.
We hence introduce logic which is generic between these platforms
without enforcing any specific format. This allows the boards to use the
relevant format for operations that they might choose.
This module will compile for all TI SoC based boards when
CONFIG_TI_I2C_BOARD_DETECT is enabled to have optimal build times for
platforms that require this support.
It is important to note that this logic is fundamental to the board
configuration process such as DDR configuration which is needed in
SPL, hence cannot be part of the standard u-boot driver model (which
is available later in the process). Hence, to aid efficiency, the
eeprom contents are copied over to SRAM scratchpad memory area at the
first invocation to retrieve data.
To prevent churn with cases such as DRA7, where eeprom format maybe
incompatible, we introduce a generic common format in eeprom which
is made available over accessor functions for usage.
Special handling for BBG1 EEPROM had to be introduced thanks to the
weird eeprom rev contents used.
The follow on patches introduce the use of this library for AM335x,
AM437x, and AM57xx.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Steve Kipisz <s-kipisz2@ti.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
8 years ago
|
|
|
|
|
|
|
|
if (ep->serial)
|
|
|
|
|
env_set("board_serial", ep->serial);
|
ARM: omap-common: Add standard access for board description EEPROM
Several TI EVMs have EEPROM that can contain board description information
such as revision, DDR definition, serial number, etc. In just about all
cases, these EEPROM are on the I2C bus and provides us the opportunity
to centralize the generic operations involved.
The on-board EEPROM on the BeagleBone Black, BeagleBone, AM335x EVM,
AM43x GP EVM, AM57xx-evm, BeagleBoard-X15 share the same format.
However, DRA-7* EVMs, OMAP4SDP use a modified format.
We hence introduce logic which is generic between these platforms
without enforcing any specific format. This allows the boards to use the
relevant format for operations that they might choose.
This module will compile for all TI SoC based boards when
CONFIG_TI_I2C_BOARD_DETECT is enabled to have optimal build times for
platforms that require this support.
It is important to note that this logic is fundamental to the board
configuration process such as DDR configuration which is needed in
SPL, hence cannot be part of the standard u-boot driver model (which
is available later in the process). Hence, to aid efficiency, the
eeprom contents are copied over to SRAM scratchpad memory area at the
first invocation to retrieve data.
To prevent churn with cases such as DRA7, where eeprom format maybe
incompatible, we introduce a generic common format in eeprom which
is made available over accessor functions for usage.
Special handling for BBG1 EEPROM had to be introduced thanks to the
weird eeprom rev contents used.
The follow on patches introduce the use of this library for AM335x,
AM437x, and AM57xx.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Steve Kipisz <s-kipisz2@ti.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
8 years ago
|
|
|
else
|
|
|
|
|
env_set("board_serial", unknown);
|
ARM: omap-common: Add standard access for board description EEPROM
Several TI EVMs have EEPROM that can contain board description information
such as revision, DDR definition, serial number, etc. In just about all
cases, these EEPROM are on the I2C bus and provides us the opportunity
to centralize the generic operations involved.
The on-board EEPROM on the BeagleBone Black, BeagleBone, AM335x EVM,
AM43x GP EVM, AM57xx-evm, BeagleBoard-X15 share the same format.
However, DRA-7* EVMs, OMAP4SDP use a modified format.
We hence introduce logic which is generic between these platforms
without enforcing any specific format. This allows the boards to use the
relevant format for operations that they might choose.
This module will compile for all TI SoC based boards when
CONFIG_TI_I2C_BOARD_DETECT is enabled to have optimal build times for
platforms that require this support.
It is important to note that this logic is fundamental to the board
configuration process such as DDR configuration which is needed in
SPL, hence cannot be part of the standard u-boot driver model (which
is available later in the process). Hence, to aid efficiency, the
eeprom contents are copied over to SRAM scratchpad memory area at the
first invocation to retrieve data.
To prevent churn with cases such as DRA7, where eeprom format maybe
incompatible, we introduce a generic common format in eeprom which
is made available over accessor functions for usage.
Special handling for BBG1 EEPROM had to be introduced thanks to the
weird eeprom rev contents used.
The follow on patches introduce the use of this library for AM335x,
AM437x, and AM57xx.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Steve Kipisz <s-kipisz2@ti.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
8 years ago
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static u64 mac_to_u64(u8 mac[6])
|
|
|
|
|
{
|
|
|
|
|
int i;
|
|
|
|
|
u64 addr = 0;
|
|
|
|
|
|
|
|
|
|
for (i = 0; i < 6; i++) {
|
|
|
|
|
addr <<= 8;
|
|
|
|
|
addr |= mac[i];
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return addr;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static void u64_to_mac(u64 addr, u8 mac[6])
|
|
|
|
|
{
|
|
|
|
|
mac[5] = addr;
|
|
|
|
|
mac[4] = addr >> 8;
|
|
|
|
|
mac[3] = addr >> 16;
|
|
|
|
|
mac[2] = addr >> 24;
|
|
|
|
|
mac[1] = addr >> 32;
|
|
|
|
|
mac[0] = addr >> 40;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
void board_ti_set_ethaddr(int index)
|
|
|
|
|
{
|
|
|
|
|
uint8_t mac_addr[6];
|
|
|
|
|
int i;
|
|
|
|
|
u64 mac1, mac2;
|
|
|
|
|
u8 mac_addr1[6], mac_addr2[6];
|
|
|
|
|
int num_macs;
|
|
|
|
|
/*
|
|
|
|
|
* Export any Ethernet MAC addresses from EEPROM.
|
|
|
|
|
* The 2 MAC addresses in EEPROM define the address range.
|
|
|
|
|
*/
|
|
|
|
|
board_ti_get_eth_mac_addr(0, mac_addr1);
|
|
|
|
|
board_ti_get_eth_mac_addr(1, mac_addr2);
|
|
|
|
|
|
|
|
|
|
if (is_valid_ethaddr(mac_addr1) && is_valid_ethaddr(mac_addr2)) {
|
|
|
|
|
mac1 = mac_to_u64(mac_addr1);
|
|
|
|
|
mac2 = mac_to_u64(mac_addr2);
|
|
|
|
|
|
|
|
|
|
/* must contain an address range */
|
|
|
|
|
num_macs = mac2 - mac1 + 1;
|
|
|
|
|
if (num_macs <= 0)
|
|
|
|
|
return;
|
|
|
|
|
|
|
|
|
|
if (num_macs > 50) {
|
|
|
|
|
printf("%s: Too many MAC addresses: %d. Limiting to 50\n",
|
|
|
|
|
__func__, num_macs);
|
|
|
|
|
num_macs = 50;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
for (i = 0; i < num_macs; i++) {
|
|
|
|
|
u64_to_mac(mac1 + i, mac_addr);
|
|
|
|
|
if (is_valid_ethaddr(mac_addr)) {
|
|
|
|
|
eth_setenv_enetaddr_by_index("eth", i + index,
|
|
|
|
|
mac_addr);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
bool __maybe_unused board_ti_was_eeprom_read(void)
|
|
|
|
|
{
|
|
|
|
|
struct ti_common_eeprom *ep = TI_EEPROM_DATA;
|
|
|
|
|
|
|
|
|
|
if (ep->header == TI_EEPROM_HEADER_MAGIC)
|
|
|
|
|
return true;
|
|
|
|
|
else
|
|
|
|
|
return false;
|
|
|
|
|
}
|
