| 2018-01-30 |
rsa: Add missing newline to pr_err messages
...
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 30 Jan 2018
|
ARM: configs: am335x_defconfig: Reorder configs
...
These configs were added directly in the config file and not with
menuconfig. Reorder these like menuconfig would place them.
Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Daniel Schultz
authored
on 29 Jan 2018
Sascha Hauer
committed
on 30 Jan 2018
|
commands: ubi: ubiupdatevol: Reduce error code to 0 or 1
...
do_ubiupdatevol can either return 0 or the ioctl return value. This is
not in conformity with the other ubi comannds return values.
Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Daniel Schultz
authored
on 29 Jan 2018
Sascha Hauer
committed
on 30 Jan 2018
|
bbremote: rename command subparser variables
...
Don't reuse unrelated subparser variables for new command subparsers,
make each subparser have its own variable.
Just for consistency really, not a bugfix.
Signed-off-by: Aleksander Morgado <aleksander@aleksander.es>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Aleksander Morgado
authored
on 28 Jan 2018
Sascha Hauer
committed
on 30 Jan 2018
|
| 2018-01-26 |
bootargs: Fix memory leak in linux_bootargs_get()
...
globalvar_get_match() returns an allocated string which may be
empty. We have to free() the empty string aswell.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 26 Jan 2018
|
fs: Fix memory leak in mount()
...
"path" is allocated by normalise_path() and thus must be
freed. This was done in the error path, but not in the success
path.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 26 Jan 2018
|
| 2018-01-25 |
net: phy: scan PHYs referenced by phandle
...
If we point to a PHY node by phandle, that PHY might well be on a MDIO
bus that hasn't been scanned when we look for the PHY. Fortunately we
know exactly where to look for the PHY, so make sure to scan the bus
at the right address.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Lucas Stach
authored
on 23 Jan 2018
Sascha Hauer
committed
on 25 Jan 2018
|
i2c: read/write_reg: don't assume client->dev to be valid
...
When using the barebox commands i2c_read or i2c_write the client pointer
passed to the respective function isn't completely initialized. This
makes
dev_dbg(&client->dev, ...);
choke as it dereferences client->dev.driver->name with
client->dev.driver being a random value.
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Uwe Kleine-König
authored
on 22 Jan 2018
Sascha Hauer
committed
on 25 Jan 2018
|
sandbox: use 'poweroff' command for exit
...
The 'poweroff' command is more appropriate for exit
barebox than 'reset'.
Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Antony Pavlov
authored
on 22 Jan 2018
Sascha Hauer
committed
on 25 Jan 2018
|
| 2018-01-22 |
Merge branch 'for-next/socfpga'
Sascha Hauer
committed
on 22 Jan 2018
|
Merge branch 'for-next/net-designware'
Sascha Hauer
committed
on 22 Jan 2018
|
Merge branch 'for-next/misc'
Sascha Hauer
committed
on 22 Jan 2018
|
Merge branch 'for-next/imx'
Sascha Hauer
committed
on 22 Jan 2018
|
Merge branch 'for-next/fastboot-sparse'
Sascha Hauer
committed
on 22 Jan 2018
|
Merge branch 'for-next/dts'
Sascha Hauer
committed
on 22 Jan 2018
|
Merge branch 'for-next/build'
Sascha Hauer
committed
on 22 Jan 2018
|
Merge branch 'for-next/at91'
Sascha Hauer
committed
on 22 Jan 2018
|
mci: drop unused parameter from mci_switch()
...
The SWITCH command has two purposes:
a) switch the command set
b) Write to the EXT_CSD register
If the access field (bits [25:24]) in the argument are b00, we're in
case a), otherwise in b). As mci_switch() always passes
MMC_SWITCH_MODE_WRITE_BYTE (0b3) in the access field, only case b) is
relevant here. According to the eMMC specification[1] the command set
field is ignored in case b) and so the respective parameter (that is
unused already now) can be dropped.
[1] Embedded Multi-Media Card (e•MMC) Electrical Standard (5.1),
February 2015; paragraph 6.6.1
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Uwe Kleine-König
authored
on 19 Jan 2018
Sascha Hauer
committed
on 22 Jan 2018
|
Release v2018.01.0
...
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 22 Jan 2018
|
commands/Kconfig: Fix tpyo
...
s/Pring/Print/
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Uwe Kleine-König
authored
on 19 Jan 2018
Sascha Hauer
committed
on 22 Jan 2018
|
state: Documentation: Fix typo
...
underlaying -> underlying
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 22 Jan 2018
|
state: Documentation: fix typo
...
Signed-off-by: Ulrich Ölmann <u.oelmann@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Ulrich Ölmann
authored
on 19 Jan 2018
Sascha Hauer
committed
on 22 Jan 2018
|
Documentation: Bootchooser: fix typo
...
Signed-off-by: Bastian Stender <bst@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Bastian Stender
authored
on 19 Jan 2018
Sascha Hauer
committed
on 22 Jan 2018
|
blspec: fix crash when trying to boot from loop mounts
...
When trying to boot from a loop mount path, the blspec code passes a
NULL pointer to dev_name, because cdev->dev is not set for loop mounts:
unable to handle NULL pointer dereference at address 0x00000020
pc : [<4fe09e28>] lr : [<4fe02305>]
sp : 4ffef7c0 ip : 31b75c78 fp : 31b6a388
r10: 31b6a368 r9 : 315a4cac r8 : 00000001
r7 : 00000001 r6 : 311b8540 r5 : ffffffea r4 : 31b6a3f8
r3 : 00000000 r2 : 10000000 r1 : 00000001 r0 : 00000000
Flags: nzcv IRQs off FIQs off Mode SVC_32
[<4fe09e28>] (dev_id+0xc/0x38) from [<4fe02305>] (blspec_scan_directory+0x3e1/0x484)
[<4fe02305>] (blspec_scan_directory+0x3e1/0x484) from [<4fe02551>] (blspec_bootentry_provider+0x1d/0x3c)
[<4fe02551>] (blspec_bootentry_provider+0x1d/0x3c) from [<4fe0984b>] (bootentry_create_from_name+0x23/0xdc)
[<4fe0984b>] (bootentry_create_from_name+0x23/0xdc) from [<4fe246f9>] (do_boot+0x95/0x160)
[<4fe246f9>] (do_boot+0x95/0x160) from [<4fe032e9>] (execute_command+0x21/0x48)
[<4fe032e9>] (execute_command+0x21/0x48) from [<4fe088e3>] (run_list_real+0x56b/0x634)
[<4fe088e3>] (run_list_real+0x56b/0x634) from [<4fe08249>] (parse_stream_outer+0xd9/0x164)
[<4fe08249>] (parse_stream_outer+0xd9/0x164) from [<4fe08b6d>] (run_shell+0x31/0x60)
[<4fe08b6d>] (run_shell+0x31/0x60) from [<4fe032e9>] (execute_command+0x21/0x48)
[<4fe032e9>] (execute_command+0x21/0x48) from [<4fe088e3>] (run_list_real+0x56b/0x634)
[<4fe088e3>] (run_list_real+0x56b/0x634) from [<4fe085fd>] (run_list_real+0x285/0x634)
[<4fe444b9>] (unwind_backtrace+0x1/0x58) from [<4fe00b7d>] (panic+0x1d/0x34)
[<4fe00b7d>] (panic+0x1d/0x34) from [<4fe42a75>] (do_exception+0xd/0x10)
[<4fe42a75>] (do_exception+0xd/0x10) from [<4fe42ad5>] (do_data_abort+0x21/0x2c)
[<4fe42ad5>] (do_data_abort+0x21/0x2c) from [<4fe42394>] (do_abort_6+0x48/0x54)
Fix this by checking cdev->dev as well as cdev before calling dev_name.
Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Philipp Zabel
authored
on 18 Jan 2018
Sascha Hauer
committed
on 22 Jan 2018
|
partitions: dos: Treat all extended partition types equally
...
Creating logical DOS partitions with fdisk (Fedora 27, fdisk from
util-linux 2.30.2) results in extended partition of type 0x05 being
created on the device. Partitioned like this, device is succesfully
recognized by Linux, but, due to algorithm in dos_partition(), not
Barebox.
Looking closer at the actual contents of MBR shows that while marked
as "Extended partition with CHS addressing" that partition still have
all of the LBA adressed fields filled correctly.
Given the above and the fact that similar code in Linux
kernel (block/partitions/msdos.c) does not make a distinction between
types 0x0f and 0x05, port Linux's is_extended_partition() and convert
the code to treat types 0x05, 0x0f and 0x85 the same way.
Signed-off-by: Andrey Smirnov <andrew.smirnov@gmail.com>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Andrey Smirnov
authored
on 17 Jan 2018
Sascha Hauer
committed
on 22 Jan 2018
|
| 2018-01-18 |
FIT: export fit_open_configuration() and fit_open_image()
...
Currently only fit_open() is exported which only opens the predefined
images "kernel", "dtb" and "ramdisk". To make the FIT code more usable
for other code which may want to open other images export
fit_open_configuration() and fit_open_image().
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 18 Jan 2018
|
usb: gadget: fastboot: Add sparse image support
...
Sparse images are needed for fastboot to flash images that do not
fit into memory.
Android fastboot is kind of a dumb protocol. It first sends you a
big image and afterwards it tells you where to put this image. This
of course limits fastboot to files smaller than the available memory.
To bypass this issue fastboot has so called Sparse image support. This
is a new image format that can contain holes in the data so a big image
can be written in multiple steps with holes in other areas each step.
Implementing this for UBI images is kind of tricky since ubiformat
normally expects to get a single image. Preparations to ubiformat
a device in multiple parts have been done in previous patches.
It is however, only for the first part possible to detect if it is
a UBI image. The other parts are just binary data and we cannot
know if we have to pass this data raw to the flash or use ubiformat.
For this reason this patch makes the 'u' flag in the partition
description mandatory for proper UBI image flashing on MTD devices.
fastboot passes a max_download_size variable to the host. This
variable contains the image size fastboot can take in one go.
We have to choose a good compromise here. On one hand we do not
want to risk that we actually do not have enough memory to hold the
transferred image, on the other hand we want images like bootloaders
not as sparse images, but in one go instead to make atomic exchange
of the bootloader possible. Right now we have chosen 8MiB which
should be big enough for all bootloaders. The value is configurable
via global.usbgadget.fastboot_max_download_size.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 18 Jan 2018
|
| 2018-01-17 |
FIT: Fix error path
...
In case of error of_unflatten_dtb() returns an ERR_PTR. Make sure
that handle->root contains NULL in this case so that we do not call
of_delete_node on the error pointer in the exit path.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 17 Jan 2018
|
at91sam9263ek: enable DT support
...
Add at91sam9263ek.dts to build.
Include mmc1 in at91sam9263ek.dts, as mmc1 is what the evaluation
kit uses for the SD card.
Add DT specific of_init
Adjust build to drop non-DT files from mach-at91
RomBOOT
>AT91Bootstrap 3.0.1
patch-0.8 64MB Ram
Load from SD-Card
Loading from SD-Card
Open: u-boot.bin
Loading from SD-Card - Success
barebox 2017.12.0-00036-gda46de29e #23 Sun Dec 31 09:15:39 CET 2017
Board: Atmel at91sam9263ek
gpio-at91 fffff200.gpio: AT91 gpio driver registered
gpio-at91 fffff400.gpio: AT91 gpio driver registered
gpio-at91 fffff600.gpio: AT91 gpio driver registered
gpio-at91 fffff800.gpio: AT91 gpio driver registered
gpio-at91 fffffa00.gpio: AT91 gpio driver registered
pinctrl-at91 pinctrl.2: AT91 pinctrl registered
AT91: Detected soc type: at91sam9263
AT91: Detected soc subtype: Unknown
mdio_bus: miibus0: probed
macb fffbc000.ethernet: Cadence MACB at 0xfffbc000
at91_udc fff78000.gadget: at91_udc version 3 May 2006
atmel_mci fff80000.mmc: version: 0x210
atmel_mci fff80000.mmc: registered as fff80000.mmc
atmel_mci fff84000.mmc: version: 0x210
atmel_mci fff84000.mmc: registered as fff84000.mmc
malloc space: 0x239fab00 -> 0x23dfaaff (size 4 MiB)
barebox-environment environment.6: probe failed: No such device
environment load /dev/env0: No such file or directory
Maybe you have to create the partition.
running /env/bin/init...
\e[?25h
Hit any key to stop autoboot: 3
barebox@Atmel at91sam9263ek:/ iomem
0x00000000 - 0xffffffff (size 0x00000000) iomem
0x00300000 - 0x00313fff (size 0x00014000) 300000.sram
0x00500000 - 0x00503fff (size 0x00004000) 500000.sram
0x00700000 - 0x00700fff (size 0x00001000) 700000.fb
0x20000000 - 0x23ffffff (size 0x04000000) ram0
0x239fab00 - 0x23dfaaff (size 0x00400000) malloc space
0x23dfab00 - 0x23dfffe2 (size 0x000054e3) board data
0x23e00000 - 0x23e53cc8 (size 0x00053cc9) barebox
0x23e53cc9 - 0x23e6404f (size 0x00010387) barebox data
0x23e64050 - 0x23e6754b (size 0x000034fc) bss
0x23fe4000 - 0x23fe7fff (size 0x00004000) ttb
0x23fe8000 - 0x23feffff (size 0x00008000) stack
0xfff78000 - 0xfff7bfff (size 0x00004000) fff78000.gadget
0xfff80000 - 0xfff805ff (size 0x00000600) fff80000.mmc
0xfff84000 - 0xfff845ff (size 0x00000600) fff84000.mmc
0xfff8c000 - 0xfff8c1ff (size 0x00000200) fff8c000.serial
0xfffbc000 - 0xfffbc0ff (size 0x00000100) fffbc000.ethernet
0xffffee00 - 0xffffefff (size 0x00000200) ffffee00.serial
0xfffff200 - 0xfffff3ff (size 0x00000200) fffff200.gpio
0xfffff400 - 0xfffff5ff (size 0x00000200) fffff400.gpio
0xfffff600 - 0xfffff7ff (size 0x00000200) fffff600.gpio
0xfffff800 - 0xfffff9ff (size 0x00000200) fffff800.gpio
0xfffffa00 - 0xfffffbff (size 0x00000200) fffffa00.gpio
0xfffffd30 - 0xfffffd3e (size 0x0000000f) fffffd30.timer
barebox@Atmel at91sam9263ek:/ devinfo
`-- global
`-- nv
`-- platform
`-- mem0
`-- 0x00000000-0x03ffffff ( 64 MiB): /dev/ram0
`-- 300000.sram
`-- 0x00000000-0x00013fff ( 80 KiB): /dev/sram0
`-- 500000.sram
`-- 0x00000000-0x00003fff ( 16 KiB): /dev/sram1
`-- ahb.0
`-- apb.1
`-- fffff000.interrupt-controller
`-- fffffc00.pmc
`-- ffffe200.ramc
`-- ffffe400.smc
`-- ffffe800.ramc
`-- ffffea00.smc
`-- ffffec00.matrix
`-- fffffd30.timer
`-- fff7c000.timer
`-- fffffd00.rstc
`-- fffffd10.shdwc
`-- pinctrl.2
`-- fffff200.gpio
`-- fffff400.gpio
`-- fffff600.gpio
`-- fffff800.gpio
`-- fffffa00.gpio
`-- ffffee00.serial
`-- cs0
`-- 0x00000000-0xffffffffffffffff ( 0 Bytes): /dev/cs0
`-- fff8c000.serial
`-- cs1
`-- 0x00000000-0xffffffffffffffff ( 0 Bytes): /dev/cs1
`-- fffbc000.ethernet
`-- miibus0
`-- eth0
`-- fff78000.gadget
`-- usbgadget
`-- fff80000.mmc
`-- mci0
`-- fff84000.mmc
`-- mci1
`-- fffffd40.watchdog
`-- fffa4000.spi
`-- fffac000.can
`-- 700000.fb
`-- a00000.ohci
`-- 10000000.ebi
`-- i2c-gpio-0.3
`-- leds.4
`-- gpio_keys.5
`-- cs2
`-- 0x00000000-0xffffffffffffffff ( 0 Bytes): /dev/cs2
`-- soc
`-- mem1
`-- 0x00000000-0xfffffffe ( 4 GiB): /dev/mem
`-- environment.6
`-- mdio_bus
`-- fs
`-- ramfs0
`-- devfs0
`-- net
`-- udc0
`-- fb0
`-- 0x00000000-0x000257ff ( 150 KiB): /dev/fb0
barebox@Atmel at91sam9263ek:/ drvinfo
Driver Device(s)
--------------------
syscon
at91-pit
fffffd30.timer
gpio-at91
fffff200.gpio
fffff400.gpio
fffff600.gpio
fffff800.gpio
fffffa00.gpio
pinctrl-at91
pinctrl.2
atmel_usart
ffffee00.serial
fff8c000.serial
ramfs
ramfs0
devfs
devfs0
fat
tftp
at91sam9-smc
Generic PHY
macb
fffbc000.ethernet
atmel_nand
cfi_flash
at91_udc
fff78000.gadget
atmel_mci
fff80000.mmc
fff84000.mmc
atmel_lcdfb
700000.fb
gpio-leds
leds.4
gpio_keys
gpio_keys.5
mmio-sram
300000.sram
500000.sram
mem
mem0
mem1
barebox-environment
Use 'devinfo DEVICE' for more information
barebox@Atmel at91sam9263ek:/ gpioinfo
GPIOs 0-31, chip fffff200.gpio:
dir val requested label
GPIO 0: unk hi false
GPIO 1: unk hi false
GPIO 2: in hi false
GPIO 3: unk hi false
GPIO 4: unk hi false
GPIO 5: unk hi false
GPIO 6: unk lo false
GPIO 7: unk hi false
GPIO 8: unk hi false
GPIO 9: unk hi false
GPIO 10: unk hi false
GPIO 11: unk hi false
GPIO 12: unk hi false
GPIO 13: in hi false
GPIO 14: in hi false
GPIO 15: in hi false
GPIO 16: in hi false
GPIO 17: in hi false
GPIO 18: in hi false
GPIO 19: in lo false
GPIO 20: in hi false
GPIO 21: in hi false
GPIO 22: in hi false
GPIO 23: in hi false
GPIO 24: in hi false
GPIO 25: in lo true udc_vbus
GPIO 26: unk hi false
GPIO 27: unk hi false
GPIO 28: unk hi false
GPIO 29: unk hi false
GPIO 30: in lo false
GPIO 31: in hi false
GPIOs 32-63, chip fffff400.gpio:
dir val requested label
GPIO 32: in hi false
GPIO 33: in hi false
GPIO 34: in hi false
GPIO 35: in hi false
GPIO 36: in hi false
GPIO 37: in hi false
GPIO 38: in hi false
GPIO 39: out hi true d3
GPIO 40: in hi false
GPIO 41: unk hi false
GPIO 42: in hi false
GPIO 43: in hi false
GPIO 44: in hi false
GPIO 45: in hi false
GPIO 46: in hi false
GPIO 47: in hi false
GPIO 48: in hi false
GPIO 49: in hi false
GPIO 50: in hi false
GPIO 51: in hi false
GPIO 52: in hi false
GPIO 53: in hi false
GPIO 54: in hi false
GPIO 55: in hi false
GPIO 56: in hi false
GPIO 57: in hi false
GPIO 58: in hi false
GPIO 59: out lo active low PHY 50 MHz oscillator
GPIO 60: in hi false
GPIO 61: in hi false
GPIO 62: in hi false
GPIO 63: in hi false
GPIOs 64-95, chip fffff600.gpio:
dir val requested label
GPIO 64: in hi false
GPIO 65: unk hi false
GPIO 66: unk hi false
GPIO 67: unk hi false
GPIO 68: in hi true gpio_keys
GPIO 69: in hi true gpio_keys
GPIO 70: unk lo false
GPIO 71: unk lo false
GPIO 72: unk lo false
GPIO 73: unk lo false
GPIO 74: unk lo false
GPIO 75: unk lo false
GPIO 76: unk lo false
GPIO 77: in hi false
GPIO 78: unk lo false
GPIO 79: unk lo false
GPIO 80: unk lo false
GPIO 81: unk lo false
GPIO 82: unk lo false
GPIO 83: unk lo false
GPIO 84: in hi false
GPIO 85: in hi false
GPIO 86: unk lo false
GPIO 87: unk lo false
GPIO 88: unk lo false
GPIO 89: unk lo false
GPIO 90: unk lo false
GPIO 91: unk lo false
GPIO 92: in hi false
GPIO 93: in hi true d2
GPIO 94: unk hi false
GPIO 95: unk hi false
GPIOs 96-127, chip fffff800.gpio:
dir val requested label
GPIO 96: in hi false
GPIO 97: in hi false
GPIO 98: in hi false
GPIO 99: in hi false
GPIO 100: in hi false
GPIO 101: in hi false
GPIO 102: in hi false
GPIO 103: in hi false
GPIO 104: in hi false
GPIO 105: in hi false
GPIO 106: in hi false
GPIO 107: in hi false
GPIO 108: unk lo false
GPIO 109: unk lo false
GPIO 110: unk lo false
GPIO 111: in hi false
GPIO 112: unk lo false
GPIO 113: unk hi false
GPIO 114: unk hi false
GPIO 115: unk lo false
GPIO 116: unk hi false
GPIO 117: unk hi false
GPIO 118: unk hi false
GPIO 119: unk hi false
GPIO 120: unk lo false
GPIO 121: unk hi false
GPIO 122: unk hi false
GPIO 123: unk lo false
GPIO 124: unk hi false
GPIO 125: unk hi false
GPIO 126: unk hi false
GPIO 127: unk hi false
GPIOs 128-159, chip fffffa00.gpio:
dir val requested label
GPIO 128: in hi false
GPIO 129: in hi false
GPIO 130: in hi false
GPIO 131: in hi false
GPIO 132: in hi false
GPIO 133: in hi false
GPIO 134: in hi false
GPIO 135: in hi false
GPIO 136: in hi false
GPIO 137: in hi false
GPIO 138: in hi false
GPIO 139: in hi false
GPIO 140: in hi false
GPIO 141: in hi false
GPIO 142: in hi false
GPIO 143: in hi false
GPIO 144: in hi false
GPIO 145: in hi false
GPIO 146: in lo true mci_cd
GPIO 147: in hi false
GPIO 148: in hi false
GPIO 149: unk lo false
GPIO 150: in hi false
GPIO 151: unk lo false
GPIO 152: unk lo false
GPIO 153: unk lo false
GPIO 154: unk lo false
GPIO 155: unk lo false
GPIO 156: unk lo false
GPIO 157: unk lo false
GPIO 158: unk hi false
GPIO 159: in hi false
barebox@Atmel at91sam9263ek:/ clk_dump
slow_xtal (rate 32768, enabled)
prog0 (rate 32768, enabled)
pck0 (rate 32768, disabled)
prog1 (rate 32768, enabled)
pck1 (rate 32768, disabled)
prog2 (rate 32768, enabled)
pck2 (rate 32768, disabled)
prog3 (rate 32768, enabled)
pck3 (rate 32768, disabled)
main_xtal (rate 16367660, enabled)
main_osc (rate 16367660, enabled)
mainck (rate 16367660, enabled)
pllbck (rate 98205960, enabled)
usbck (rate 49102980, enabled)
uhpck (rate 49102980, disabled)
udpck (rate 49102980, disabled)
pllack (rate 204595750, enabled)
masterck (rate 102297875, enabled)
pioA_clk (rate 102297875, enabled)
pioB_clk (rate 102297875, enabled)
pioCDE_clk (rate 102297875, enabled)
usart0_clk (rate 102297875, enabled)
usart1_clk (rate 102297875, disabled)
usart2_clk (rate 102297875, disabled)
mci0_clk (rate 102297875, disabled)
mci1_clk (rate 102297875, disabled)
can_clk (rate 102297875, disabled)
twi0_clk (rate 102297875, disabled)
spi0_clk (rate 102297875, disabled)
spi1_clk (rate 102297875, disabled)
ssc0_clk (rate 102297875, disabled)
ssc1_clk (rate 102297875, disabled)
ac97_clk (rate 102297875, disabled)
tcb_clk (rate 102297875, disabled)
pwm_clk (rate 102297875, disabled)
macb0_clk (rate 102297875, enabled)
g2de_clk (rate 102297875, disabled)
udc_clk (rate 102297875, disabled)
isi_clk (rate 102297875, disabled)
lcd_clk (rate 102297875, enabled)
dma_clk (rate 102297875, disabled)
ohci_clk (rate 102297875, disabled)
barebox@Atmel at91sam9263ek:/ led
registered LEDs:
0 : name: d3 max_value: 1
1 : name: d2 max_value: 1
barebox@Atmel at91sam9263ek:/ led 1 1
barebox@Atmel at91sam9263ek:/ led 0 1
Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
Reviewed-by: Andrey Smirnov <andrew.smirnov@gmail.com>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sam Ravnborg
authored
on 15 Jan 2018
Sascha Hauer
committed
on 17 Jan 2018
|
arm: at91: simplify soc setup
...
The at91 soc support inherited a complex scheme
from the kernel.
This schme did not really give any benefits, and when
starting to migrate at91sam9263ek to use DT it started
to get in the way for a proper way to do things.
Replace the former setup with a simple function
pointer that can be called from setup.c.
Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
Reviewed-by: Andrey Smirnov <andrew.smirnov@gmail.com>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sam Ravnborg
authored
on 15 Jan 2018
Sascha Hauer
committed
on 17 Jan 2018
|
