summaryrefslogtreecommitdiffstats
path: root/board/BuR
Commit message (Collapse)AuthorAgeFilesLines
* board/BuR/brppt1: add makerule for generating production filesHannes Schmelzer2018-07-191-0/+36
| | | | Signed-off-by: Hannes Schmelzer <oe5hpm@oevsv.at>
* board/BuR/brppt1: convert brppt1 boards to driver modelHannes Schmelzer2018-07-192-101/+24
| | | | | | | | | | - add a devicetree for each variant (mmc, spi, nand) - drop unneeded code from board and bur/common - drop unneeded stuff from config header files - minor adaptions to be compliant with driver model (requesting gpio,..) - harmonize the commandset over all brppt1 targets Signed-off-by: Hannes Schmelzer <oe5hpm@oevsv.at>
* board/BuR/brppt1: implement more flexible boot processHannes Schmelzer2018-07-191-3/+25
| | | | | | | | | | | | | | | | | | | | | | | | | With this commit we do: - set the bootdelay in all brppt1 defconfigs to 0, this makes development easier, since we can break into serial console. - move CONFIG_BOOTCOMMAND from header file to defconfig - introduce b_mode variable for selecting the final boot-target. This b_mode represents the boot-switch, which can found on most b&r targets. On the brppt1 this boot-switch is derived from some gpio and the bootcounter within the RTC block, making it so possible to force a boot-target (as example for repair-case). - refactor the environment for booting new flexible way primary we want to get some bootscr.img within the mass-storage, this script then loads everything needed for the boot. For legacy reason we implement the t30lgcy#x boot targets, booting the already delivered linux-images. - make space for the cfgscr within mtdparts on brppt1_nand Signed-off-by: Hannes Schmelzer <oe5hpm@oevsv.at>
* board/BuR/common: refactor ft_board_setup(...)Hannes Schmelzer2018-07-191-5/+10
| | | | | | | | | | | | | | | | | | | | On other OS, not one provided by B&R, it is not guaranteed that there are factory-settings within a devicetree. So we must not treat the absence of them as error. Further we've the fact that on different version of the device-tree files there are different namings of the factory-settings, we consider this with searching for an alternative name. changing things as following: - don't treat as error if the bootloader version cannot written into devicetree. - since the naming of the factory-settings are different in different versions of the provided device-tree we search for the alternate name "/fset" Signed-off-by: Hannes Schmelzer <oe5hpm@oevsv.at>
* board/BuR/brppt1: drop dead code (CONFIG_SPL_OS_BOOT)Hannes Schmelzer2018-07-191-16/+0
| | | | | | | The falcon mode was never used on this board, there is also no plan to use it. So drop this dead code. Signed-off-by: Hannes Schmelzer <oe5hpm@oevsv.at>
* board/BuR/common: fix PMIC mpu-pll setupHannes Schmelzer2018-07-191-1/+1
| | | | | | | | | | | If a board-code calls the pmicsetup(u32 mpupll) with a mpupll value != 0 it wants to force some frequency with the value provided by mpupll. Setting up 1 GHz is wrong here. Nobody did take notice about that yet, since every board calls this function with zero. Signed-off-by: Hannes Schmelzer <oe5hpm@oevsv.at>
* board/BuR/common: remove interface Label from summary screenHannes Schmelzer2018-07-191-2/+2
| | | | | | | | This interface names may vary over different products, to consider this fact we replace the interface label "IF1" and "IF2" on the summary screen with some more generic wording "MAC1" and "MAC2". Signed-off-by: Hannes Schmelzer <oe5hpm@oevsv.at>
* board/BuR/brppt1: drop LCD-supportHannes Schmelzer2018-07-191-4/+0
| | | | | | | | | On this linux target long time ago the OS is using DRM driver for handling video output, the pre initialization of u-boot and the display summary screen is obsolete. With this patch we drop the LCD-support from thisd board. Signed-off-by: Hannes Schmelzer <oe5hpm@oevsv.at>
* board/BuR/common: make CONFIG_LCD optionalHannes Schmelzer2018-07-191-21/+18
| | | | | | | | | | | Since we're going to drop LCD-support on brppt1 boards, we have to make this stuff here optional and remove the #error path. We also move out the ft_board_setup(...) from this #ifdef because there's no relationship with the LCD-code and on the other hand this is still needed in future even with LCD-support off. Signed-off-by: Hannes Schmelzer <oe5hpm@oevsv.at>
* board/BuR/common: drop simple-framebuffer setupHannes Schmelzer2018-07-191-26/+0
| | | | | | | | | The linux systems running on the brppt1 targets are using modern DRM drivers since long time ago. Further we are going to drop the LCD support completely on this board, so the simple-framebuffer setup becomes obsolete. Signed-off-by: Hannes Schmelzer <oe5hpm@oevsv.at>
* board/BuR: drop devicetree loading and lcd setup for linux-targetsHannes Schmelzer2018-07-191-224/+6
| | | | | | | | | | | | | This patch drops the lcd-screen setup, the summary screen and getting mac-addresses based on a previous loaded device-tree for linux targets. Selecting those linux target is simple, since we have only the brppt1. In detail we do: - drop the common lcd-setup code which relys on a fdt_blob - drop the common dtb loading mechanism - drop the now obsolete CONFIG_USE_FDT from board header and whitelist. Signed-off-by: Hannes Schmelzer <oe5hpm@oevsv.at>
* SPDX: Convert all of our single license tags to Linux Kernel styleTom Rini2018-05-078-18/+8
| | | | | | | | | | | | | | | | | | | | When U-Boot started using SPDX tags we were among the early adopters and there weren't a lot of other examples to borrow from. So we picked the area of the file that usually had a full license text and replaced it with an appropriate SPDX-License-Identifier: entry. Since then, the Linux Kernel has adopted SPDX tags and they place it as the very first line in a file (except where shebangs are used, then it's second line) and with slightly different comment styles than us. In part due to community overlap, in part due to better tag visibility and in part for other minor reasons, switch over to that style. This commit changes all instances where we have a single declared license in the tag as both the before and after are identical in tag contents. There's also a few places where I found we did not have a tag and have introduced one. Signed-off-by: Tom Rini <trini@konsulko.com>
* net: Move enetaddr env access code to env config instead of net configAlex Kiernan2018-04-081-0/+1
| | | | | | | | | | | | | | | | | | | | In order that we can use eth_env_* even when CONFIG_NET isn't set, move these functions to environment code from net code. This fixes failures such as: board/ti/am335x/built-in.o: In function `board_late_init': board/ti/am335x/board.c:752: undefined reference to `eth_env_set_enetaddr' u-boot/board/ti/am335x/board.c:766: undefined reference to `eth_env_set_enetaddr' which caters for use cases such as: commit f411b5cca48f ("board: am335x: Always set eth/eth1addr environment variable") when Ethernet is required in Linux, but not U-Boot. Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com>
* board/BuR: drop LCDC clock manipulation from board codeHannes Schmelzer2018-01-112-5/+0
| | | | | | | | The clock selection is done now from the am335x-fb code, so there is no more need doing this in the board code. Signed-off-by: Hannes Schmelzer <oe5hpm@oevsv.at> Reviewed-by: Anatolij Gustschin <agust@denx.de>
* board/BuR: provide real clock-frequency instead a dividerHannes Schmelzer2018-01-111-10/+4
| | | | | | | | | Actual am335x-fb implementation takes now a real clock frequency instead a divider. So this component doesn't need to know anymore some base frequency of the LCDC, we simply provide the pixel-clock frequency. Signed-off-by: Hannes Schmelzer <oe5hpm@oevsv.at> Reviewed-by: Anatolij Gustschin <agust@denx.de>
* env: Rename getenv_hex(), getenv_yesno(), getenv_ulong()Simon Glass2017-08-162-23/+23
| | | | | | | | We are now using an env_ prefix for environment functions. Rename these for consistency. Also add function comments in common.h. Suggested-by: Wolfgang Denk <wd@denx.de> Signed-off-by: Simon Glass <sjg@chromium.org>
* env: Rename getenv/_f() to env_get()Simon Glass2017-08-161-6/+6
| | | | | | | | | | | We are now using an env_ prefix for environment functions. Rename these two functions for consistency. Also add function comments in common.h. Quite a few places use getenv() in a condition context, provoking a warning from checkpatch. These are fixed up in this patch also. Suggested-by: Wolfgang Denk <wd@denx.de> Signed-off-by: Simon Glass <sjg@chromium.org>
* env: Rename eth_setenv_enetaddr() to eth_env_set_enetaddr()Simon Glass2017-08-161-1/+1
| | | | | | Rename this function for consistency with env_set(). Signed-off-by: Simon Glass <sjg@chromium.org>
* env: Rename setenv() to env_set()Simon Glass2017-08-163-10/+10
| | | | | | | | We are now using an env_ prefix for environment functions. Rename setenv() for consistency. Also add function comments in common.h. Suggested-by: Wolfgang Denk <wd@denx.de> Signed-off-by: Simon Glass <sjg@chromium.org>
* board: BuR: use get_nand_dev_by_index()Grygorii Strashko2017-07-111-1/+2
| | | | | | | | | | As part of preparation for nand DM conversion the new API has been introduced to remove direct access to nand_info array. So, use it here instead of accessing to nand_info array directly. Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com> Reviewed-by: Hannes Schmelzer <hannes.schmelzer@br-automation.com> Reviewed-by: Simon Glass <sjg@chromium.org>
* board/BuR/brxre1: fix MMC bootHannes Schmelzer2017-06-161-1/+6
| | | | | | | | | | | | | | since commit 'd5abcf94c7123167725fc22ace342f0d455093c1' - ti: boot: Register the MMC controllers in SPL in the same way as in u-boot MMC boot on brxre1 board is broken, with this commit we make our board working again. Signed-off-by: Hannes Schmelzer <hannes.schmelzer@br-automation.com> Reviewed-by: Tom Rini <trini@konsulko.com> Reviewed-by: Jean-Jacques Hiblot <jjhiblot@ti.com>
* mmc: replace CONFIG_GENERIC_MMC with CONFIG_MMCMasahiro Yamada2017-05-151-1/+1
| | | | | | | | | | | Now CONFIG_GENERIC_MMC and CONFIG_MMC match for all defconfig. We do not need two options for the same feature. Deprecate the former. This commit was generated with the sed script 's/GENERIC_MMC/MMC/' and manual fixup of drivers/mmc/Kconfig. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
* board/BuR/common: incorrect check of dtbxypron.glpk@gmx.de2017-05-051-3/+3
| | | | | | | | | | | | | The logical expression to check the dtb is incorrect in load_devicetree. The problem was indicated by cppcheck. The inconsistent variable name dtppart is changed to dtbpart. Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by: Hannes Schmelzer <oe5hpm@oevsv.at> Acked-by: Hannes Schmelzer <oe5hpm@oevsv.at>
* ti: boot: Register the MMC controllers in SPL in the same way as in u-bootJean-Jacques Hiblot2017-03-191-1/+1
| | | | | | | | | | | | To keep a consistent MMC device mapping in SPL and in u-boot, let's register the MMC controllers the same way in u-boot and in the SPL. In terms of boot time, it doesn't hurt to register more controllers than needed because the MMC device is initialized only prior being accessed for the first time. Having the same device mapping in SPL and u-boot allows us to use the environment in SPL whatever the MMC boot device. Signed-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com>
* board/BuR: rename kwb board to brxre1Hannes Schmelzer2016-06-246-12/+12
| | | | | | | Rename B&R kwb board to brxre1 Signed-off-by: Hannes Schmelzer <oe5hpm@oevsv.at> Reviewed-by: Tom Rini <trini@konsulko.com>
* board/BuR: rename tseries board to brppt1Hannes Schmelzer2016-06-246-13/+13
| | | | | | | Rename B&R tseries board to brppt1 Signed-off-by: Hannes Schmelzer <oe5hpm@oevsv.at> Reviewed-by: Tom Rini <trini@konsulko.com>
* nand: Embed mtd_info in struct nand_chipScott Wood2016-06-031-1/+1
| | | | | | | | | | | | nand_info[] is now an array of pointers, with the actual mtd_info instance embedded in struct nand_chip. This is in preparation for syncing the NAND code with Linux 4.6, which makes the same change to struct nand_chip. It's in a separate commit due to the large amount of changes required to accommodate the change to nand_info[]. Signed-off-by: Scott Wood <oss@buserror.net>
* board/BuR: drop ETH-support in SPL-StageHannes Schmelzer2016-02-241-7/+2
| | | | | | | | | | | | | During very early prototype-phase we did boot the AM335x boards initially from CPSW-EMAC. Now we don't need this feature anymore. So we drop it to save MLO-space and having therefore a more quickly boot. Signed-off-by: Hannes Schmelzer <oe5hpm@oevsv.at> Reviewed-by: Tom Rini <trini@konsulko.com>
* board/BuR/kwb: use bootvx(...) (with bootline feature) instead go(...)Hannes Petermaier2015-11-121-18/+9
| | | | | | | | | | | | | | | | Since we don't have for sure a valid IP-setup during board_late_init(...) because it maybe allready stored in environment or not, we cannot form a proper vxWorks bootline at this place. So we move to the way, forming the bootline just before executing/launching vxWorks. To do this we use the bootvx command instead go. We only have to form the "othbootargs" environment variable, the rest is done pretty good by the "bootvx" commannd. Signed-off-by: Hannes Schmelzer <oe5hpm@oevsv.at> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
* board/BuR: simplify default IP-setup on B&R boards.Hannes Petermaier2015-09-111-10/+0
| | | | | | | | | | | | | | | | | | | To simplify and having a common default IP-setup on all B&R boards we introduce an environment variable "brdefaultip" which does following. Test if ${ipaddr} is empty, if yes it set's up some defaults: - ipaddr : 192.168.60.1 - netmask : 255.255.255.0 - gatewayip: 192.168.60.254 - serverip : 192.168.60.254 This environment is ran from CONFIG_PREBOOT. All other "tricks" are dropped. Signed-off-by: Hannes Schmelzer <oe5hpm@oevsv.at> Reviewed-by: Tom Rini <trini@konsulko.com> Acked-by: Joe Hershberger <joe.hershberger@ni.com>
* board/BuR/common: support timer5 for pwm-backlightHannes Petermaier2015-06-181-3/+11
| | | | | | | | | | in future we support yet another b&r am335x based board, where Timer 5 is wired to backlight-driver. So we introduce a new driver-type '2' to setup timer5 instead timer6. Signed-off-by: Hannes Schmelzer <oe5hpm@oevsv.at> Reviewed-by: Simon Glass <sjg@chromium.org>
* cosmetic: change Author/MAINTAINER Name from Petermaier to SchmelzerHannes Schmelzer2015-05-2810-10/+10
| | | | | | | | | | | Since i've been married, i also have a new surname. Mr. Petermaier moved to Mr. Schmelzer. In this patch i update all files in which my (old) name is present. Signed-off-by: Hannes Schmelzer <hannes.schmelzer@br-automation.com> Signed-off-by: Hannes Schmelzer <oe5hpm@oevsv.at>
* board/BuR/common: rename "usbupdate" environment to "usbscript"Hannes Petermaier2015-05-081-2/+2
| | | | | | | | | | | usbupdate in real does allways load some script from usb-storage and execute it, on all B&R targets. So we do following 2 things: - rename it to what it really does - move it from boards to common environment Signed-off-by: Hannes Petermaier <oe5hpm@oevsv.at>
* board/BuR/tseries: Add simplefb supportHannes Petermaier2015-05-081-48/+86
| | | | | | | | | | | | | | | | | | | | | | | Since the used AM3352 SoC doesn't have GPU it isn't allways necessary to build in complete drm-stuff into linux kernel. In very small applications only we use the simple-framebuffer. So we have 2 use-cases: - device operating on drm-driver (let simplefb node disabled) - device operating on simplefb-driver (activate simplefb node and reserve mem) The decision is made by means of "simplefb" environment variable. simplefb = 0 we don't enable the (maybe) existing simplefb node and all the rest around display is up to the linux-kernel. We just disable the backlight, beceause we do not want see the flicker during take over of drm-driver. simplefb = 1 we enable the (maybe) existing simplefb node and reserve framebuffers size in memory. Signed-off-by: Hannes Petermaier <oe5hpm@oevsv.at>
* board/BuR/tseries: take usage of CONFIG_LCD_ROTATIONHannes Petermaier2015-05-081-0/+23
| | | | | | | | | | | | | | | | We take use of the new LCD_ROTATION feature. The information about how the display is rotated is taken from B&R specific (/factory-settings/rotation) information in the devicetree. The information there is stored as string (cw, ud, ccw, none) since starting support of this devices and cannot be changed, so we have to convert it into none = 0 cw = 1 ud = 2 ccw = 3 Signed-off-by: Hannes Petermaier <oe5hpm@oevsv.at>
* board/BuR/tseries: change pinmuxHannes Petermaier2015-04-231-3/+9
| | | | | | | some pins on the board have been rerouted to other peripherals, so we change the pinmux to apply with hardware-design. Signed-off-by: Hannes Petermaier <oe5hpm@oevsv.at>
* board/BuR/tseries: reactivate NAND-boardHannes Petermaier2015-04-233-5/+15
| | | | | | | | | | | | | | The NAND-version has been become a bit orphan. Now we need to reactivate it, so bring necessary things: - loading devicetree - switch control signal to correct pins - setup pinmux - default-environment up to date. Signed-off-by: Hannes Petermaier <oe5hpm@oevsv.at>
* board/BuR/common: simplify access to devicetreeHannes Petermaier2015-04-231-59/+55
| | | | | | | | | | instead of polling everytime the environment, we take usage of the global gd->fdt_blob variable and check it only against NULL. Variable "dtbaddr" from environment is needed only one time on loading the devicetree within "load_devicetree()" Signed-off-by: Hannes Petermaier <oe5hpm@oevsv.at>
* net: cosmetic: Name ethaddr variables consistentlyJoe Hershberger2015-04-181-2/+2
| | | | | | | | Use "_ethaddr" at the end of variables and drop CamelCase. Make constant values actually 'const'. Signed-off-by: Joe Hershberger <joe.hershberger@ni.com> Acked-by: Simon Glass <sjg@chromium.org>
* board/BuR/common: remove unused function 'blink'Hannes Petermaier2015-03-282-15/+0
| | | | | | | | | since we have possibility to write out on lcd whats going on, we don't need the gpio blink functionality anymore. Signed-off-by: Hannes Petermaier <hannes.petermaier@br-automation.com> Signed-off-by: Hannes Petermaier <oe5hpm@oevsv.at>
* board/BuR/common: move I2C initialization from common part to board-specificHannes Petermaier2015-03-286-8/+9
| | | | | | | | | | | | | | | | | | At this time I2C and responsible pin-mux is setup during PMIC initialziation within common.c, this is possible because today PMIC is always connected on I2C0. In Future this will be changed, PMIC isn't anymore connected to bus0 in call cases. So we do following: - rename enable_i2c_pin_mux0 to enable_i2c_pin_mux to be generic for enabling pin-mux on different or more busses. - move the call to i2c_pin_mux and i2c_init from common.c to the specific board.c Signed-off-by: Hannes Petermaier <hannes.petermaier@br-automation.com> Signed-off-by: Hannes Petermaier <oe5hpm@oevsv.at>
* board/BuR/common: use SYS_CONSOLE_OVERWRITEHannes Petermaier2015-03-171-0/+4
| | | | | | | We don't want that CONSOLE is redirected to LCD upon init, we rather prefer that console is still on the serial line. Signed-off-by: Hannes Petermaier <oe5hpm@oevsv.at>
* board/BuR/kwb: Support modify bootcmd through reset-controllerHannes Petermaier2015-03-051-2/+28
| | | | | | | | | | | | | For some cases it is necessary to modify temporaly the bootcommand. This can be done by writing into the Scratchregister a specific value: * 0xCC - modify bootcmd "run netboot" * 0xCD - modify bootcmd "run netscript" * 0xCE - modify bootcmd "run mmcboot" the environment in flash is NOT overwritten. Signed-off-by: Hannes Petermaier <oe5hpm@oevsv.at>
* board/BuR/kwb: Form a bootline for vxWorksHannes Petermaier2015-03-051-0/+30
| | | | | | | | vxWorks needs several parameters which are set by the bootloader und his environment. So we form a vxWorks bootline and pass the result to vxWorks on a predefined address. Signed-off-by: Hannes Petermaier <oe5hpm@oevsv.at>
* board/BuR/kwb: switch to board HW-Rev3Hannes Petermaier2015-03-052-61/+82
| | | | | | | | | The board has been redesigned, therefore we need from now other I/O Pins to mux and handle. Older boards aren't supported from now anymore. Signed-off-by: Hannes Petermaier <oe5hpm@oevsv.at>
* board/BuR/tseries: cosmetic changesHannes Petermaier2015-03-051-2/+0
| | | | | | remove unnary '#define ETHLED_ORANGE (96+16) /* GPIO3_16 */' Signed-off-by: Hannes Petermaier <oe5hpm@oevsv.at>
* board/BuR/tseries: Chg Pinmux - enable UART1 pinsHannes Petermaier2015-03-051-0/+8
| | | | Signed-off-by: Hannes Petermaier <oe5hpm@oevsv.at>
* board/BuR/tseries: Chg pinmux - use free NAND Pins in non NAND-config as GPIOHannes Petermaier2015-03-051-1/+8
| | | | | | | On boards were we have no NAND-flash soldered, we want to use those free pins as regular gpio. Signed-off-by: Hannes Petermaier <oe5hpm@oevsv.at>
* board/BuR/tseries: Change pinmux for GPIO2_28 from GPIO to PWM-TimeroutputHannes Petermaier2015-03-051-3/+3
| | | | Signed-off-by: Hannes Petermaier <oe5hpm@oevsv.at>
* board/BuR/tseries: Enable HW-WatchdogHannes Petermaier2015-03-051-0/+4
| | | | Signed-off-by: Hannes Petermaier <oe5hpm@oevsv.at>
generated by cgit (git 2.34.1) at 2024-08-18 23:03:10 +0000