2015-01-26 17:46 GMT+02:00 Jon Cormier :
> 26.1.8.6
Thanks Jon!
My interpretation from codes was pretty much what you described that USB
boot really was "modified network boot". I'm not too sure that this was HW
restriction (=CPU) but merely u-boot boot strategy decision as am335x does
have boo
Hi Peter,
On 26 January 2015 at 10:42, Peter Tyser wrote:
> When run with the --dry-run argument patman prints out information
> showing what it would do. This information currently doesn't line up
> with what patman/git send-email really do. Some basic examples:
> - If an email address is addr
These functions are useful in case the board calls them. Also fix a missing
parameter caused by applying the wrong patch (actually I failed to send v2
and applied v1 by mistake).
Signed-off-by: Simon Glass
---
Changes in v4:
- Bring in the correct patch version
drivers/i2c/i2c-uclass-compat.c
The EC has no concept of offset, so use a value of 0.
Signed-off-by: Simon Glass
---
Changes in v4: None
arch/arm/dts/exynos5250-snow.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/dts/exynos5250-snow.dts b/arch/arm/dts/exynos5250-snow.dts
index 649e4bd..7d8be69 100644
--- a/
Since U-Boot can support different offset lengths (0-4 bytes), add a device
tree property to specify this. This avoids hard-coding it in the driver.
Signed-off-by: Simon Glass
---
Changes in v4: None
doc/device-tree-bindings/i2c/i2c.txt | 28
drivers/i2c/i2c-uclass
Move this driver to use driver model and update the snow configuration to
match.
Signed-off-by: Simon Glass
---
Changes in v4:
- Add patches to support offset length in device tree
- Rebase on top of exynos I2C series
drivers/misc/cros_ec_i2c.c | 82
This series sits on top of Przemyslaw's recent driver model conversion for
Exynos. It changes the cros_ec_i2c driver to use driver model.
Also a new device tree property is added to support offset length, a U-Boot
I2C concept but a feature of the hardware.
Changes in v4:
- Bring in the correct pa
Minghuan,
On 01/26/2015 09:12 PM, Lian Minghuan-B31939 wrote:
> Hi York,
>
> We can not use phys_addr_t and phys_size_t here.
>
> If CONFIG_PHYS_64BIT is defined and uboot is compiled as 32bit like
> PowerPC64 arch,
> phys_addr_t and phys_size_t will be defined as 64bit, but the pointer is
>
On 26 January 2015 at 08:21, Przemyslaw Marczak wrote:
> This patch enables CONFIG_DM_I2C and also CONFIG_DM_I2C_COMPAT.
> The last one should be removed when all the i2c peripheral
> drivers will use dm i2c framework.
>
> Signed-off-by: Przemyslaw Marczak
> Cc: Akshay Saraswat
> Cc: Minkyu Kang
Hi Przemyslaw,
On 26 January 2015 at 08:21, Przemyslaw Marczak wrote:
> This commit adjusts the s3c24x0 driver to new i2c api
> based on driver-model. The driver supports standard
> and high-speed i2c as previous.
>
> Tested on Trats2, Odroid U3, Arndale, Odroid XU3
>
> Signed-off-by: Przemyslaw
On 8 January 2015 at 04:33, Przemyslaw Marczak wrote:
> This commit enable support for the above driver,
> which was disabled in common config.
>
> Signed-off-by: Przemyslaw Marczak
> Cc: Simon Glass
> Cc: Minkyu Kang
> ---
> include/configs/smdk5250.h | 2 ++
> 1 file changed, 2 insertions(+)
Hi Przemyslaw,
On 8 January 2015 at 04:33, Przemyslaw Marczak wrote:
> Some versions of Exynos5 supports High-Speed I2C,
> on few interfaces, this change allows support this.
>
> Signed-off-by: Przemyslaw Marczak
> Cc: Simon Glass
> Cc: Akshay Saraswat
> Cc: Minkyu Kang
> ---
> arch/arm/cpu/
On 26 January 2015 at 08:21, Przemyslaw Marczak wrote:
> This change fixes i2c bus numbering for Odroid U3.
>
> Signed-off-by: Przemyslaw Marczak
> Cc: Minkyu Kang
>
> ---
> Changes v2:
> - new patch
> ---
> arch/arm/dts/exynos4412-odroid.dts | 7 +++
> 1 file changed, 7 insertions(+)
Acke
On 26 January 2015 at 08:21, Przemyslaw Marczak wrote:
> This patch enables CONFIG_DM_I2C and also CONFIG_DM_I2C_COMPAT.
> The last one should be removed when the dm pmic framework will
> be finished.
>
> Signed-off-by: Przemyslaw Marczak
> Cc: Minkyu Kang
>
> ---
> Changes v2:
> - new patch
> -
On 8 January 2015 at 04:33, Przemyslaw Marczak wrote:
> Without this alias setting, the seq numbers
> of the i2c devices are wrong.
>
> Signed-off-by: Przemyslaw Marczak
> Cc: Simon Glass
> Cc: Minkyu Kang
> ---
> arch/arm/dts/exynos5250-arndale.dts | 8
> 1 file changed, 8 insertions
On 8 January 2015 at 04:33, Przemyslaw Marczak wrote:
> This patch modify i2c nodes in exynos4.dtsi with:
> - adding proper interrupts arrays for each i2c node,
> which allows to decode periph id
> - add reg address for each i2c node for i2c driver internal use
>
> Signed-off-by: Przemyslaw Marc
On 8 January 2015 at 04:33, Przemyslaw Marczak wrote:
> This PMIC is not common for all Exynos5250
> based boards, so should be romoved from
> common config.
>
> Signed-off-by: Przemyslaw Marczak
> Cc: Simon Glass
> Cc: Minkyu Kang
> ---
> include/configs/exynos5250-common.h | 3 ---
> 1 file
On 8 January 2015 at 04:33, Przemyslaw Marczak wrote:
> There is no MAX77686 pmic on this board,
> so the driver support should be removed.
>
> Signed-off-by: Przemyslaw Marczak
> Cc: Minkyu Kang
> ---
> include/configs/arndale.h | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/include
Hi York,
We can not use phys_addr_t and phys_size_t here.
If CONFIG_PHYS_64BIT is defined and uboot is compiled as 32bit like
PowerPC64 arch,
phys_addr_t and phys_size_t will be defined as 64bit, but the pointer is
still 32bit size.
we could not convert directly between phys_addr_t and a poi
From: Sonic Zhang
Board can define its own AXI burst length to improve DWMAC DMA performance.
Signed-off-by: Sonic Zhang
---
drivers/net/designware.c |2 ++
drivers/net/designware.h |5 +
2 files changed, 7 insertions(+)
diff --git a/drivers/net/designware.c b/drivers/net/designw
This patch is to implement pmic_mode_init function, and add prototype
in header file.
This function is to set switching mode for pmic buck regulators to
improve system efficiency.
Mode:
OFF: The regulator is switched off and the output voltage is discharged.
PFM: In this mode, the regulator is al
To normal mode, use APS switching mode.
To standy mode, use PFM switching mode.
Signed-off-by: Peng Fan
Acked-by: Przemyslaw Marczak
---
Changes v5:
Add Acked-by: Przemyslaw Marczak
Changes v4:
none
Changes v3:
Following Fabio's comments, correct return value
Changes v2:
none
board/fr
This patch set is to support buck regulator can
working in different switching modes. To improve
system efficiency the buck regulators can operate
in different switching modes.
patch 1/3 is to add related bit definitions and registers.
patch 2/3 is to implement the switching mode init function.
pa
Add more pfuze register offset.
And switch mode definition.
Add a macro SWITCH_SIZE
Signed-off-by: Peng Fan
Acked-by: Przemyslaw Marczak
Reviewed-by: Stefano Babic
---
Changes v5:
add "Acked-by: Przemyslaw Marczak " and
"Reviewed-by: Stefano Babic "
define a SWITCH_SIZE macro to replace
On Mon, 2015-01-26 at 17:17 -0600, Peter Tyser wrote:
> On Mon, 2015-01-26 at 16:33 -0600, Scott Wood wrote:
> > On Mon, 2015-01-26 at 16:24 -0600, Peter Tyser wrote:
> > > The driver-specific verify_buf() function can be replaced with the
> > > standard read_page_raw() function to verify writes.
Since we must run a PCI BIOS ROM, and this can take a calamitous amount of
time, measure it using bootstage.
Signed-off-by: Simon Glass
---
drivers/video/vesa_fb.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/video/vesa_fb.c b/drivers/video/vesa_fb.c
index 9164f8d..47f824a 1006
Signed-off-by: Simon Glass
---
arch/x86/cpu/queensbay/Makefile| 2 +-
arch/x86/cpu/queensbay/fsp_configs.c | 2 +-
arch/x86/cpu/queensbay/tnc.c | 2 +-
arch/x86/cpu/queensbay/tnc_dram.c
For now this code seems to be the same for all FSP platforms. Make it
common until we see what differences are required.
Signed-off-by: Simon Glass
---
arch/x86/cpu/queensbay/Makefile | 2 +-
arch/x86/lib/fsp/Makefile | 2 ++
arch/x86/{c
For the debug UART we need to be able to provide any parameters before
driver model is set up. Add parameters to the low-level access functions
to make this possible.
Signed-off-by: Simon Glass
---
Changes in v2: None
drivers/serial/ns16550.c | 48 ++
This series adds debug UART infrastructure which can in principle be used on
any architecture. It works best with those that don't need a stack to call
functions (e.g. ARM, PowerPC).
This came up in a discussion on the mailing list here:
https://patchwork.ozlabs.org/patch/384613/
My concerns
This came up in a discussion on the mailing list here:
https://patchwork.ozlabs.org/patch/384613/
My concerns at the time were:
- it doesn't need to be written in assembler
- it doesn't need to be ARM-specific
This patch provides a possible alternative. It works by allowing any serial
driver to
Add debug UART functions to permit ns16550 to provide an early debug UART.
Try to avoid using the stack so that this can be called from assembler before
a stack is set up (at least on ARM and PowerPC).
Signed-off-by: Simon Glass
---
Changes in v2:
- Split series out on its own
- Add x86 support
Some information has been gleaned on tools and procedures for porting
U-Boot to different x86 platforms. Add a few notes to start things off.
Signed-off-by: Simon Glass
---
doc/README.x86 | 63 ++
1 file changed, 63 insertions(+)
diff --g
If the BIOS emulator is not available, allow use of native execution if
available, and vice versa. This can be controlled by the caller.
Signed-off-by: Simon Glass
---
arch/x86/cpu/ivybridge/gma.c | 3 ++-
drivers/pci/pci_rom.c| 32 +---
drivers/video/vesa_f
Since the FSP is a black box it helps to have some sort of debugging
available to check its inputs. If the debug UART is in use, set it up
after CAR is available.
Signed-off-by: Simon Glass
---
arch/x86/include/asm/u-boot-x86.h | 3 +++
arch/x86/lib/fsp/fsp_support.c| 4
2 files change
The base address is found in a different way and the protection bit is also
in a different place. Otherwise it is very similar.
Signed-off-by: Simon Glass
---
drivers/spi/ich.c | 56 ---
drivers/spi/ich.h | 11 ++-
2 files changed, 47
Rather than requiring the Makefile to be modified, provide a build option to
enable the ROM to be built.
We cannot do this by default since it requires binary blobs. Without these
the build will fail.
Signed-off-by: Simon Glass
---
Makefile | 5 +++--
doc/README.x86 | 10 ++
2 f
Since these board functions seem to be the same for all boards which use
FSP, move them into a common file. We can adjust this later if future FSPs
need more flexibility.
Signed-off-by: Simon Glass
---
arch/x86/cpu/queensbay/tnc.c | 27
arch/x86/cpu/queensbay/tnc_pci.c | 15 -
To avoid casts, find_fsp_header() should return a pointer. Add asmlinkage
to two API functions which use that convention. UPD_TERMINATOR is common
so move it into a common file.
Signed-off-by: Simon Glass
---
arch/x86/include/asm/arch-queensbay/fsp/fsp_vpd.h | 2 --
arch/x86/include/asm/fsp/fsp
This setting will be used by more than just ivybridge so make it common.
Signed-off-by: Simon Glass
---
arch/x86/Kconfig | 12
board/google/chromebook_link/Kconfig | 1 -
2 files changed, 12 insertions(+), 1 deletion(-)
diff --git a/arch/x86/Kconfig b/arch/x86
Allow measuring of boot time using bootstage.
Signed-off-by: Simon Glass
---
include/configs/x86-common.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/configs/x86-common.h b/include/configs/x86-common.h
index ecedfc3..66d4894 100644
--- a/include/configs/x86-common.h
+++ b/inc
On some hardware this time can be significant. Add bootstage support for
measuring this. The result can be obtained using 'bootstage report' or
passed on to the Linux via the device tree.
Signed-off-by: Simon Glass
---
common/cmd_scsi.c | 2 ++
include/bootstage.h | 1 +
2 files changed, 3 in
This avoids a warning in the Realtek Ethernet driver. The value may not
matter on x86.
Signed-off-by: Simon Glass
---
arch/x86/include/asm/cache.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/x86/include/asm/cache.h b/arch/x86/include/asm/cache.h
index 508b63f..fff1edd 100644
---
There is an existing function prototype in the header file but it is not
implemented. Implement something similar.
Signed-off-by: Simon Glass
---
drivers/pci/pci.c | 38 ++
include/pci.h | 3 +--
2 files changed, 39 insertions(+), 2 deletions(-)
diff --
This board includes a few IDs we have not seen before.
Signed-off-by: Simon Glass
---
include/pci_ids.h | 5 +
1 file changed, 5 insertions(+)
diff --git a/include/pci_ids.h b/include/pci_ids.h
index 26f4748..1012abe 100644
--- a/include/pci_ids.h
+++ b/include/pci_ids.h
@@ -1346,6 +1346,7
Add a driver which locates the available XHCI controllers on the PCI bus
and makes them available.
Signed-off-by: Simon Glass
---
drivers/usb/host/Makefile | 1 +
drivers/usb/host/xhci-pci.c | 60 +
2 files changed, 61 insertions(+)
create mode 10
While queensbay is the first chip with these settings, others will want to
use them too. Make them common.
Signed-off-by: Simon Glass
---
arch/x86/Kconfig | 38 ++
arch/x86/cpu/queensbay/Kconfig | 38 --
2 fil
Use the new utility function instead of local code.
Signed-off-by: Simon Glass
---
drivers/usb/host/ehci-pci.c | 53 +
1 file changed, 1 insertion(+), 52 deletions(-)
diff --git a/drivers/usb/host/ehci-pci.c b/drivers/usb/host/ehci-pci.c
index 991b19
This board uses a new PCI ID.
Signed-off-by: Simon Glass
---
drivers/video/vesa_fb.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/video/vesa_fb.c b/drivers/video/vesa_fb.c
index 3dacafd..3a0fea2 100644
--- a/drivers/video/vesa_fb.c
+++ b/drivers/video/vesa_fb.c
@@ -23,6 +23,7 @@
Sometimes microcode is delivered as a header file. Allow the tool to
support this as well as collecting multiple microcode blocks into a
single update.
Signed-off-by: Simon Glass
---
tools/microcode-tool.py | 90 ++---
1 file changed, 70 insertions(+)
Tidy up the FSP support code a little.
Signed-off-by: Simon Glass
---
arch/x86/lib/fsp/fsp_support.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/arch/x86/lib/fsp/fsp_support.c b/arch/x86/lib/fsp/fsp_support.c
index bf37807..8b639f7 100644
--- a/arch/x86/lib/fs
This series adds support for the Intel Minnowboard Max (called Minnowmax
for short). Along the way a few refactors and additions are made:
- The Intel Firmware Support Package support is moved from queensbay to a
common location
- PCI support for XHCI is added
- A few tweaks are made to the PCI su
On 26 January 2015 at 13:14, Simon Glass wrote:
> On 25 January 2015 at 08:27, Simon Glass wrote:
>> Update the driver model support, and remove the old code. Change snow to
>> use this new support.
>>
>> Signed-off-by: Simon Glass
>> ---
>>
>> Changes in v3: None
>> Changes in v2:
>> - Add patc
On Mon, 2015-01-26 at 16:33 -0600, Scott Wood wrote:
> On Mon, 2015-01-26 at 16:24 -0600, Peter Tyser wrote:
> > The driver-specific verify_buf() function can be replaced with the
> > standard read_page_raw() function to verify writes. This will
> > allow
> > verify_buf() to be removed from indi
On Mon, 2015-01-26 at 16:24 -0600, Peter Tyser wrote:
> The driver-specific verify_buf() function can be replaced with the
> standard read_page_raw() function to verify writes. This will allow
> verify_buf() to be removed from individual drivers. verify_buf() is no
> longer supported in mainline
Hi Christophe,
On Mon, Jan 26, 2015 at 07:15:20AM -0800, christophe.le.rou...@gmail.com wrote:
> > +CONFIG_SYS_EXTRA_OPTIONS="AXP209_POWER,SUNXI_GMAC,AHCI,SATAPWR=SUNXI_GPH(2),USB_EHCI"
>
> What do you think about adding "RGMII" in the CONFIG_SYS_EXTRA_OPTIONS
> like other gigabit A20 board ?
Go
From: Martin Dorwig
this is an atempt to make the export of functions typesafe.
I replaced the jumptable void ** by a struct (jt_funcs) with function pointers.
The EXPORT_FUNC macro now has 3 fixed parameters and one
variadic parameter
The first is the name of the exported function,
the rest of t
This is a low-cost Allwinner A20 board with Arduino-style GPIO headers;
it features 1G RAM, 4G NAND flash, 1 micro-SD, 2 USB sockets, 1 micro
USB socket for OTG and another for power in, HDMI, SATA, 5V power for
SATA devices, gigabit Ethernet, an IR receiver, 3.5mm audio out and a
MIPI camera conne
The nand_verify_buf() function is no longer used, so remove it. This
function has been removed in mainline Linux for a long time, so it
brings U-Boot's NAND implementation a bit closer to its source.
Signed-off-by: Peter Tyser
---
board/prodrive/alpr/nand.c | 16 -
board/socr
The driver-specific verify_buf() function can be replaced with the
standard read_page_raw() function to verify writes. This will allow
verify_buf() to be removed. verify_buf() is no longer supported in
mainline Linux, so it is a pain to continue supporting.
Signed-off-by: Peter Tyser
---
I don'
From: Joe Schaack
Modify the nand_write_page() function to use ECC when appropriate to verify
writes. Previously if a single bit error occured and software ECC was
used the write verification would report a failure. However, the write
really did succeed, since ECC can handle the error.
The iss
From: Joe Schaack
Modify the nand_davinci_write_page() function to use ECC when appropriate
to verify writes. Previously if a single bit error occured and software
ECC was used the write verification would report a failure. However,
the write really did succeed, since ECC can handle the error.
The driver-specific verify_buf() function can be replaced with the
standard read_page_raw() function to verify writes. This will allow
verify_buf() to be removed from individual drivers. verify_buf() is no
longer supported in mainline Linux, so it is a pain to continue
supporting.
Signed-off-by:
Add "oem format" command to write partition table. This relies on the
env variable partitions to contain the list of partitions as required by
the gpt command.
Note that this does not erase any data other than the partition table.
Signed-off-by: Rob Herring
---
drivers/usb/gadget/f_fastboot.c |
This series adds fastboot oem sub-command infrastructure and support for
"oem format" command which partitions and formats the storage device.
The partition layout is set within the u-boot env and is implemented
using the "gpt write" command.
Rob
Michael Scott (1):
fastboot: add "fastboot oe
From: Michael Scott
Add code stub to handle "fastboot oem __" command. As unlock is a common
fastboot command, distinguish that it is not implemented.
Signed-off-by: Michael Scott
Signed-off-by: Rob Herring
---
drivers/usb/gadget/f_fastboot.c | 15 +++
1 file changed, 15 insertion
Add a check for USB cable attached and only enter fastboot when a cable
is attached.
Signed-off-by: Rob Herring
---
common/cmd_fastboot.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/common/cmd_fastboot.c b/common/cmd_fastboot.c
index b72f4f3..346ab80 100644
--- a/common/cmd_fastboo
From: Martin Dorwig
this is an atempt to make the export of functions typesafe.
I replaced the jumptable void ** by a struct (jt_funcs) with function pointers.
The EXPORT_FUNC macro now has 3 fixed parameters and one
variadic parameter
The first is the name of the exported function,
the rest of t
Dear Masahiro,
On 15/12/2014 17:46, Masahiro YAMADA wrote:
Hi Angelo,
2014-12-02 18:22 GMT+09:00 Angelo Dureghello :
And thanks to your post i have also seen now how to build all the m68k
boards in the correct way.
So the tool chain you posted gives no warnings and so it is the
recommended
Hi Wolfgang,
On 26 January 2015 at 11:55, Wolfgang Denk wrote:
> Dear Simon,
>
> In message
> you
> wrote:
>>
>> > Is this a 100% binary compatible change? If not, should we not also
>> > increment XF_VERSION ?
>>
>> If a board has move to driver model and doesn't use
>> CONFIG_DM_I2C_COMPAT
On 25 January 2015 at 08:27, Simon Glass wrote:
> This is no-longer needed since all platforms use SPI for cros_ec.
>
> Signed-off-by: Simon Glass
> ---
>
> Changes in v3: None
> Changes in v2:
> - Add patches to tidy up cros_ec using new I2C/SPI features
>
> drivers/misc/cros_ec_spi.c | 51
> +
On 25 January 2015 at 08:27, Simon Glass wrote:
> Now that we have new bus features, update README.txt and the SPI docs to
> explain these.
> Signed-off-by: Simon Glass
> ---
>
> Changes in v3: None
> Changes in v2:
> - Drop RFC prefix since this series has been properly tested now
> - Update com
On 25 January 2015 at 08:27, Simon Glass wrote:
> Update the driver model support, and remove the old code. Change snow to
> use this new support.
>
> Signed-off-by: Simon Glass
> ---
>
> Changes in v3: None
> Changes in v2:
> - Add patches to tidy up cros_ec using new I2C/SPI features
>
> drive
On 25 January 2015 at 08:27, Simon Glass wrote:
> I2C is now deprecated on ARM platforms and there are no devices that use it
> with the v3 protocol. We can't require v3 support if we want to support I2C.
> Adjust the error handling to suit.
>
> Signed-off-by: Simon Glass
> ---
>
> Changes in v3:
On 25 January 2015 at 08:27, Simon Glass wrote:
> We don't want to bind devices which should never be used.
>
> Signed-off-by: Simon Glass
> Reviewed-by: Masahiro Yamada
> ---
>
> Changes in v3: None
> Changes in v2:
> - Add patches to tidy up cros_ec using new I2C/SPI features
>
> drivers/core
On 25 January 2015 at 23:53, Minkyu Kang wrote:
> On 26/01/15 00:27, Simon Glass wrote:
>> This has moved to driver model so we don't need the fdtdec support.
>>
>> Signed-off-by: Simon Glass
>> ---
>>
>> Changes in v3: None
>> Changes in v2: None
>>
>> include/fdtdec.h | 1 -
>> lib/fdtdec.c
On 25 January 2015 at 08:27, Simon Glass wrote:
> At present we go through various contortions to store the SPI slave's chip
> select in its private data. This only exists when the slave is active so
> must be set up when it is probed. Until the device is probed we don't
> actually know what chip
On 25 January 2015 at 08:27, Simon Glass wrote:
> These have moved to driver model so we don't need the fdtdec support.
>
> Signed-off-by: Simon Glass
Applied to -u-boot-dm
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listi
On 25 January 2015 at 19:05, Masahiro Yamada wrote:
>
> On Sun, 25 Jan 2015 08:27:13 -0700
> Simon Glass wrote:
>
>> At present we go through various contortions to store the I2C's chip
>> address in its private data. This only exists when the chip is active so
>> must be set up when it is probed
On 25 January 2015 at 08:27, Simon Glass wrote:
> Use a single exit point when we have an error and add debugging there.
>
> Signed-off-by: Simon Glass
> ---
>
> Changes in v3: None
> Changes in v2: None
>
> drivers/mtd/spi/sandbox.c | 7 +--
> 1 file changed, 5 insertions(+), 2 deletions(-)
On 25 January 2015 at 08:27, Simon Glass wrote:
> Some buses need to set up their devices before they can be used. This setup
> may well be common to all buses in a particular uclass. Support a common
> pre-probe method for the uclass, called before any bus devices are probed.
>
> Signed-off-by: S
On 25 January 2015 at 08:27, Simon Glass wrote:
> At present we use struct spi_slave as our device pointer in a lot of places
> to avoid changing the old SPI API. At some point this will go away.
>
> But for now, it is better if the SPI uclass sets up this pointer, rather
> than relying on passing
On 25 January 2015 at 08:27, Simon Glass wrote:
> For buses, after a child is bound, allow the uclass to perform some
> processing. This can be used to figure out the address of the child (e.g.
> the chip select for SPI slaves) so that it is ready to be probed.
>
> This avoids bus drivers having t
On 25 January 2015 at 08:27, Simon Glass wrote:
> This is common to all SPI drivers and specifies a structure used by the
> uclass. It makes more sense to define it in the uclass.
>
> Reviewed-by: Masahiro Yamada
> Signed-off-by: Simon Glass
> ---
>
> Changes in v3: None
> Changes in v2: None
>
On 25 January 2015 at 19:00, Masahiro Yamada wrote:
>
> On Sun, 25 Jan 2015 08:27:06 -0700
> Simon Glass wrote:
>
>> In many cases the per-child private data for a device's children is defined
>> by the uclass rather than the individual driver. For example, a SPI bus
>> needs to store information
On 25 January 2015 at 08:27, Simon Glass wrote:
> In many cases the child platform data for a device's children is defined by
> the uclass rather than the individual devices. For example, a SPI bus needs
> to know the chip select and speed for each of its children. It makes sense
> to allow this i
On 25 January 2015 at 08:27, Simon Glass wrote:
> Allow parent drivers to be called when a new child is bound to them. This
> allows a bus to set up information it needs for that child.
>
> Signed-off-by: Simon Glass
> Reviewed-by: Masahiro Yamada
> ---
>
> Changes in v3: None
> Changes in v2: N
On 25 January 2015 at 18:58, Masahiro Yamada wrote:
>
> On Sun, 25 Jan 2015 08:27:04 -0700
> Simon Glass wrote:
>
>> This is useful to check which uclass a device is in.
>>
>> Signed-off-by: Simon Glass
>
>
> Reviewed-by: Masahiro Yamada
>
Applied to -u-boot-dm
On 25 January 2015 at 08:27, Simon Glass wrote:
> At present we try to use the 'reg' property and device tree aliases to give
> devices a sequence number. The 'reg' property is often actually a memory
> address, so the sequence numbers thus-obtained are not useful. It would be
> better if the devi
On 25 January 2015 at 18:56, Masahiro Yamada wrote:
>
> On Sun, 25 Jan 2015 08:27:01 -0700
> Simon Glass wrote:
>
>> For buses it is common for parents to need to know the address of the child
>> on the bus, the bus speed to use for that child, and other information. This
>> can be provided in pl
On 25 January 2015 at 18:57, Masahiro Yamada wrote:
>
> On Sun, 25 Jan 2015 08:27:00 -0700
> Simon Glass wrote:
>
>> When using allocated platform data, allocate it when we bind the device.
>> This makes it possible to fill in this information before the device is
>> probed.
>>
>> This fits with
On 25 January 2015 at 08:26, Simon Glass wrote:
> Make the error handling more standard to make it easier to build on top of
> it. Also correct a bug in the error path where there is no parent.
>
> Signed-off-by: Simon Glass
> Reviewed-by: Masahiro Yamada
> ---
>
> Changes in v3: None
> Changes
On 25 January 2015 at 08:26, Simon Glass wrote:
> Mention that the devices are probed ready for use.
>
> Signed-off-by: Simon Glass
> ---
>
> Changes in v3: None
> Changes in v2: None
>
> include/dm/uclass.h | 4
> 1 file changed, 4 insertions(+)
Applied to -u-boot-dm
_
On 25 January 2015 at 08:26, Simon Glass wrote:
> The root device corresponds to the root device tree node, so set this up.
> Also add a few notes to the documentation.
>
> Signed-off-by: Simon Glass
> ---
>
> Changes in v3: None
> Changes in v2: None
>
> doc/driver-model/README.txt | 4
>
On 25 January 2015 at 08:26, Simon Glass wrote:
> There is no point in running the tests if U-Boot cannot be built. Abort in
> this case.
>
> Signed-off-by: Simon Glass
> ---
>
> Changes in v3: None
> Changes in v2: None
>
> test/dm/test-dm.sh | 9 +++--
> 1 file changed, 7 insertions(+), 2
On 25 January 2015 at 08:26, Simon Glass wrote:
> Rather than assuming that the chip offset length is 1, allow it to be
> provided. This allows chips that don't use the default offset length to
> be used (at present they are only supported by the command line 'i2c'
> command which sets the offset
Hi Tom,
The following changes since commit 37b608a52dcb13312a4f7ccea199cd6bac76d298:
powerpc: remove icecube_5200, Lite5200, cpci5200, mecp5200, pf5200
(2015-01-23 16:56:09 -0500)
are available in the git repository at:
http://git.denx.de/u-boot-x86.git
for you to fetch changes up to e43ad
Hi,
On 26-01-15 16:18, Tom Rini wrote:
On Fri, Jan 23, 2015 at 09:54:12AM +0100, Hans de Goede wrote:
Hi,
On 22-01-15 22:03, Tom Rini wrote:
On Thu, Jan 22, 2015 at 08:10:06PM +0100, Hans de Goede wrote:
Hi,
On 22-01-15 17:20, Tom Rini wrote:
On Wed, Jan 21, 2015 at 09:03:25PM +0100, Hans
Dear Simon,
In message
you wrote:
>
> > Is this a 100% binary compatible change? If not, should we not also
> > increment XF_VERSION ?
>
> If a board has move to driver model and doesn't use
> CONFIG_DM_I2C_COMPAT (and this should ideally not be used) then the
> I2C functions are not present.
Hello everyone,
I have a Gumstix Overo (OMAP3) COM here that I am evaluating BCH8 ECC
scheme on boot-loader (2014.10) and the kernel (3.17.7).
Traditionally the board has been configured with 1 bit HAM, as are other
OMAP3 boards.
I have these changes in my board config:
+#define CONFIG_BCH
+#def
1 - 100 of 193 matches
Mail list logo
