| 2014-09-30 |
Introduce message logging support
...
This adds a buffer for log messages and a 'dmesg' command to
print the messages. The log buffer is implemented as log objects
rather than a string buffer. This makes it easy to implement
limiting the messages, cleaning the buffer and timestamping
the messages.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 30 Sep 2014
|
| 2014-09-16 |
resource: Let dev_request_mem_region return an error pointer
...
For all users fix or add the error check.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 16 Sep 2014
|
resource: Let dev_request_mem_region_by_name return an error pointer
...
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 16 Sep 2014
|
resource: Let dev_get_mem_region return an error pointer
...
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Acked-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Sascha Hauer
committed
on 16 Sep 2014
|
resource: Let dev_get_resource return an error pointer
...
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 16 Sep 2014
|
resource: Let request_iomem_region return an error pointer
...
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 16 Sep 2014
|
resource: Let dev_get_mem_region_by_name return an error pointer
...
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 16 Sep 2014
|
resource: Let dev_get_resource_by_name return an error pointer
...
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 16 Sep 2014
|
| 2014-04-08 |
common: Allow for I/O mapped I/O
...
Rework the current framework so that I/O mapped I/O resources are
also possible.
Signed-off-by: Michel Stam <michel@reverze.net>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Michel Stam
authored
on 7 Apr 2014
Sascha Hauer
committed
on 8 Apr 2014
|
| 2014-02-13 |
device: remove parameters when unregistering a device
...
Otherwise we loose memory on each device_unregister. The ethernet
code used to do this before calling unregister_device. This can
now be removed.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 13 Feb 2014
|
device: init bus list
...
bus_list is only initialized when the device has a bus, but it
needs to be initialized in unregister_device, so initialize the
list unconditionally.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 13 Feb 2014
|
| 2013-11-08 |
treewide: Add missing includes
...
A lot of files rely on include/driver.h including include/of.h (and
this including include/errno.h. include the files explicitly so we can
eventually get rid of including of.h from driver.h
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 8 Nov 2013
|
| 2013-10-07 |
Merge branch 'for-next/misc'
...
Conflicts:
commands/Makefile
Sascha Hauer
committed
on 7 Oct 2013
|
| 2013-09-29 |
introduce runtime loglevel
...
With this the verbosity of barebox can be controlled during runtime
using the 'loglevel' globalvar.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 29 Sep 2013
|
| 2013-09-27 |
move devinfo command to its own file
...
Just like nearly all other commands are in individual files.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 27 Sep 2013
|
| 2013-06-26 |
driver: implement device_detect_by_name function
...
It becomes a common pattern for boards to find a device and
call device_detect on it. Add a convenience wrapper for it.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 26 Jun 2013
|
| 2013-05-31 |
devices: add detect mechanism
...
We often encounter the situation where slow devices should not be
probed during startup since probing is slow and maybe unnecessary
for unused devices. With MMC we have the 'probe' device parameter,
for ata we have the same, for USB we have the 'usb' command. Overall
this is not very consistent.
With MMC there is the additional problem that the probe parameter
is attached to the logical device when we often have the information
which physical device we want to probe.
This patch adds a 'detect' callback for devices and adds a command
to detect devices and to list the devices which are actually detecable.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 31 May 2013
|
| 2013-05-30 |
driver: Attach info callback to device, not to driver
...
Since the info is device specific and not driver specific, attach
the callback to the device. This makes it possible to have a info
callback for a device which does not have a driver attached.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 30 May 2013
|
| 2013-05-23 |
param: Add info function
...
Some parameters may wish to provide some information about their
meaning or possible values. Provide an info callback for parameters.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 23 May 2013
|
| 2013-04-23 |
Add initial pinctrl support
...
This is a massively stripped down pinctrl support. The upper API
consists of only of:
int pinctrl_select_state(struct device_d *dev, const char *state);
This is used to setup the pinmux for a device to a certain state.
This function normally does not need to be called manually. The
device core will setup the default state before probing a device.
The pinctrl core has the job of handling the devicetree. It parses
the pinctrl phandles for a device from devicetree, finds the correct
pinctrl device and calls its set_state callback with the pinctrl
setup device node.
The simplicity of this pinctrl framework comes from the fact that
we:
- Limit usage to devicetree only for now. For non devicetree use the
old legacy SoC specific APIs still can be used.
- Do not parse the devicetree into internal data structures which
are used by the drivers later. This adds the overhead that we
may parse the devicetree multiple times for more dynamic setups,
but on the other hand we do not need to parse devices from the
devicetree we don't use in barebox
- Do not detect resource conflicts. Since the framework mainly is
a devicetree parser this would be hard to implement. It should
be easy for board maintainers to avoid resource conflicts though.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 23 Apr 2013
|
| 2013-03-14 |
bus: Make struct device a pointer
...
struct bus_type contains an embedded struct device_d which is quite
a big structure. Dynamically allocate this instead to save the space
in the binary.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 14 Mar 2013
|
| 2013-02-18 |
Make "dev_get_resource" publicly available
...
Signed-off-by: Alexander Shiyan <shc_work@mail.ru>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Alexander Shiyan
authored
on 16 Feb 2013
Sascha Hauer
committed
on 18 Feb 2013
|
| 2012-12-12 |
drivers/base: fix corrupt device tree
...
dev_add_child is a very unsafe function. If called multiple times
it allows setting the same device to different parents thus corrupting
the siblings list. This happens regularly since:
| commit c2e568d
| Author: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
| Date: Sat Nov 3 16:11:05 2012 +0100
|
| bus: add bus device
|
| automatically add it as parent of any bus device if none already specified
|
| we have now a nice output per bus
If for example a FATfs is mounted this nice output per bus often ends with:
> `---- fat0
> `---- 0
> `---- 0x86f0000087020031-0x86f000410df27124: /dev/<NULL>
> `---- sram00
> `---- 0x00000000-0xffffffffffffffff: /dev/<NULL>
> `---- 0x00000000-0xffffffffffffffff: /dev/<NULL>
> unable to handle NULL pointer dereference at address 0x0000000c
> pc : [<87f08a20>] lr : [<87f08a04>]
> sp : 86eff8c0 ip : 87f3fbde fp : ffffffff
> r10: ffffffff r9 : 00000000 r8 : 00000003
> r7 : 86f075b8 r6 : 00000002 r5 : ffffffec r4 : 86f07544
> r3 : 00000000 r2 : 43f900b4 r1 : 00000020 r0 : 00000005
> Flags: Nzcv IRQs off FIQs off Mode SVC_32
> [<87f08a20>] (do_devinfo_subtree+0x90/0x130) from [<87f08a90>] (do_devinfo_subtree+0x100/0x130)
>
> [<87f3e070>] (unwind_backtrace+0x0/0x90) from [<87f28514>] (panic+0x28/0x3c)
> [<87f28514>] (panic+0x28/0x3c) from [<87f3e4b8>] (do_exception+0x10/0x14)
> [<87f3e4b8>] (do_exception+0x10/0x14) from [<87f3e544>] (do_data_abort+0x2c/0x38)
> [<87f3e544>] (do_data_abort+0x2c/0x38) from [<87f3e268>] (data_abort+0x48/0x60)
This patch fixes this by adding a device to its parents children list in
register_device so that dev_add_child is no longer needed. This function
is removed from the tree. Now callers of register_device have to clearly
set the parent *before* registering a device.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Reported-by: Jan Lübbe <jlu@pengutronix.de>
Sascha Hauer
committed
on 12 Dec 2012
|
| 2012-12-07 |
Merge branch 'for-next/phylib'
...
Conflicts:
drivers/net/phy/phy.c
Sascha Hauer
committed
on 7 Dec 2012
|
| 2012-11-20 |
driver: introduce device_probe to manully probe a device
...
This will expect a driver to be specified
This is needed by the phylib the probe the generic phy if not driver found
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Jean-Christophe PLAGNIOL-VILLARD
authored
on 18 Nov 2012
Sascha Hauer
committed
on 20 Nov 2012
|
| 2012-11-19 |
bus: add bus device
...
automatically add it as parent of any bus device if none already specified
we have now a nice output per bus
barebox@Atmel at91sam9x5-ek:/
devices:
`---- platform
`---- atmel_usart0
`---- cs0
`---- atmel_usart1
`---- cs1
`---- mem0
`---- 0x00000000-0x07ffffff: /dev/ram0
`---- mem1
`---- 0x00000000-0x00007fff: /dev/sram0
`---- mem2
`---- 0x00000000-0x000037bf: /dev/defaultenv
`---- mem3
`---- 0x00000000-0xfffffffe: /dev/mem
`---- cs2
`---- w1-gpio
`---- w1_bus0
`---- w1-2d-0
`---- 0x00000000-0x0000007f: /dev/ds24310
`---- w1-2d-1
`---- 0x00000000-0x0000007f: /dev/ds24311
`---- w1-23-0
`---- 0x00000000-0x000001ff: /dev/ds24330
`---- at91sam9x5cm
`---- at91sam9x5ek
`---- at91sam9x5dm
`---- atmel_nand0
`---- nand0
`---- 0x00000000-0x1fffffff: /dev/nand0
`---- 0x00000000-0x0003ffff: /dev/at91bootstrap_raw
`---- 0x00040000-0x0009ffff: /dev/self_raw
`---- 0x000a0000-0x000bffff: /dev/env_raw
`---- 0x000c0000-0x000dffff: /dev/env_raw1
`---- 0x00000000-0x0003ffff: /dev/nand0.at91bootstrap
`---- 0x00040000-0x0009ffff: /dev/nand0.barebox
`---- 0x000a0000-0x000bffff: /dev/nand0.bareboxenv
`---- 0x000c0000-0x000dffff: /dev/nand0.bareboxenv2
`---- 0x000e0000-0x000fffff: /dev/nand0.oftree
`---- 0x00100000-0x001fffff: /dev/nand0.free
`---- 0x00200000-0x007fffff: /dev/nand0.kernel
`---- 0x00800000-0x07ffffff: /dev/nand0.rootfs
`---- 0x08000000-0x1fffffff: /dev/nand0.data
`---- macb0
`---- miibus0
`---- eth0
`---- atmel_spi0
`---- mtd_dataflash0
`---- dataflash0
`---- 0x00000000-0x0041ffff: /dev/dataflash0
`---- atmel_mci0
`---- mci0
`---- 0x00000000-0x1d9bfffff: /dev/disk0
`---- 0x00100000-0x064fffff: /dev/disk0.0
`---- 0x06500000-0x1d9bfffff: /dev/disk0.1
`---- i2c-gpio0
`---- i2c0
`---- qt10700
`---- cs3
`---- mdio_bus
`---- spi
`---- i2c
`---- w1_bus
`---- fs
`---- ramfs0
`---- devfs0
`---- net
`---- global
drivers:
atmel_usart
ramfs
devfs
fat
macb
Generic PHY
atmel_nand
mtd_dataflash
m25p80
atmel_spi
i2c-gpio
mci
atmel_mci
qt1070
w1-gpio
ds2431
ds2433
mem
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Jean-Christophe PLAGNIOL-VILLARD
authored
on 3 Nov 2012
Sascha Hauer
committed
on 19 Nov 2012
|
| 2012-11-16 |
Merge branch 'for-next/misc'
...
Conflicts:
commands/Makefile
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha Hauer
committed
on 16 Nov 2012
|
| 2012-10-30 |
driver: add support for requesting resource by name
...
this will allow to avoid issue with resource order
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Jean-Christophe PLAGNIOL-VILLARD
authored
on 17 Oct 2012
Sascha Hauer
committed
on 30 Oct 2012
|
| 2012-10-17 |
cosmetic: remove right alignment on driver list
...
In order to avoid misalignment, just remove the right alignment while
printing the drivers list.
Signed-off-by: Franck Jullien <franck.jullien@gmail.com>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Franck Jullien
authored
on 16 Oct 2012
Sascha Hauer
committed
on 17 Oct 2012
|
| 2012-10-07 |
Merge branch 'pu/misc-fixes'
Sascha Hauer
committed
on 7 Oct 2012
|
