Hi Bin,
On 22 April 2015 at 12:14, Bin Meng wrote:
> Hi Jagan,
>
> On Tue, Apr 21, 2015 at 8:47 PM, Jagan Teki wrote:
>> Hi Bin,
>>
>> On 20 April 2015 at 15:02, Bin Meng wrote:
>>> Hi Jagan,
>>>
>>> On Fri, Apr 17, 2015 at 4:48 PM, Jagan Teki
>>> wrote:
Hi Bin,
On 17 April 201
Hi Jagan,
On Wed, Apr 22, 2015 at 3:03 PM, Jagan Teki wrote:
> Hi Bin,
>
> On 22 April 2015 at 12:14, Bin Meng wrote:
>> Hi Jagan,
>>
>> On Tue, Apr 21, 2015 at 8:47 PM, Jagan Teki wrote:
>>> Hi Bin,
>>>
>>> On 20 April 2015 at 15:02, Bin Meng wrote:
Hi Jagan,
On Fri, Apr 17, 20
Hi Bin,
On 22 April 2015 at 12:44, Bin Meng wrote:
> Hi Jagan,
>
> On Wed, Apr 22, 2015 at 3:03 PM, Jagan Teki wrote:
>> Hi Bin,
>>
>> On 22 April 2015 at 12:14, Bin Meng wrote:
>>> Hi Jagan,
>>>
>>> On Tue, Apr 21, 2015 at 8:47 PM, Jagan Teki
>>> wrote:
Hi Bin,
On 20 April 201
Hi Jagan,
On Wed, Apr 22, 2015 at 4:06 PM, Jagan Teki wrote:
> Hi Bin,
>
> On 22 April 2015 at 12:44, Bin Meng wrote:
>> Hi Jagan,
>>
>> On Wed, Apr 22, 2015 at 3:03 PM, Jagan Teki wrote:
>>> Hi Bin,
>>>
>>> On 22 April 2015 at 12:14, Bin Meng wrote:
Hi Jagan,
On Tue, Apr 21, 20
Hi Bin,
On 22 April 2015 at 14:13, Bin Meng wrote:
> Hi Jagan,
>
> On Wed, Apr 22, 2015 at 4:06 PM, Jagan Teki wrote:
>> Hi Bin,
>>
>> On 22 April 2015 at 12:44, Bin Meng wrote:
>>> Hi Jagan,
>>>
>>> On Wed, Apr 22, 2015 at 3:03 PM, Jagan Teki
>>> wrote:
Hi Bin,
On 22 April 201
Hi Pavel,
On 20.04.2015 11:43, Stefan Roese wrote:
On 20.04.2015 11:24, Pavel Machek wrote:
Which SPI flash are you talking about -- QSPI one or EPCS/EPCQ one ?
I think Stefan got the QSPI one working. EPCQ is a bit trickier.
Datasheet mentions QSPI_IO*/CLK/SS* pins, so I assume it is QSPI.
Hi Tom,
On 08.04.2015 16:01, Simon Glass wrote:
On 7 April 2015 at 20:50, Simon Glass wrote:
On 30 March 2015 at 21:47, Masahiro Yamada
wrote:
CONFIG_SPI does not exist in Kconfig in the first place, so the
dependency "depends on DM && SPI" is never met, i.e., DM_SPI_FLASH
can never be enab
Hi Jagan,
On Wed, Apr 22, 2015 at 5:15 PM, Jagan Teki wrote:
> Hi Bin,
>
> On 22 April 2015 at 14:13, Bin Meng wrote:
>> Hi Jagan,
>>
>> On Wed, Apr 22, 2015 at 4:06 PM, Jagan Teki wrote:
>>> Hi Bin,
>>>
>>> On 22 April 2015 at 12:44, Bin Meng wrote:
Hi Jagan,
On Wed, Apr 22, 20
Hi Bin,
On 22 April 2015 at 15:02, Bin Meng wrote:
> Hi Jagan,
>
> On Wed, Apr 22, 2015 at 5:15 PM, Jagan Teki wrote:
>> Hi Bin,
>>
>> On 22 April 2015 at 14:13, Bin Meng wrote:
>>> Hi Jagan,
>>>
>>> On Wed, Apr 22, 2015 at 4:06 PM, Jagan Teki
>>> wrote:
Hi Bin,
On 22 April 201
T2080RDB RevC uses new SODIMM 1867MT/s instead of previous 1600MT/s.
So update RCW to support new DDR frequency 1867MT/s by default.
Reserve the old 1600MT/s in comment for users in needed.
Signed-off-by: Shengzhou Liu
---
board/freescale/t208xrdb/t2080_rcw.cfg | 5 -
1 file changed, 4 inser
Upto now flash sector_size is assigned from params which isn't
necessarily a sector size from vendor, so based on the SECT_*
flags from flash_params the erase_size will compute and it will
become the sector_size finally.
Signed-off-by: Jagannadha Sutradharudu Teki
Reported-by: Bin Meng
---
driv
On Wednesday, April 22, 2015 at 11:19:53 AM, Stefan Roese wrote:
> Hi Tom,
>
> On 08.04.2015 16:01, Simon Glass wrote:
> > On 7 April 2015 at 20:50, Simon Glass wrote:
> >> On 30 March 2015 at 21:47, Masahiro Yamada
> >>
> >> wrote:
> >>> CONFIG_SPI does not exist in Kconfig in the first place,
On 20 April 2015 at 11:17, Heiko Schocher wrote:
> From: Daniel Schwierzeck
>
> add MTD layer driver for spi, original patch from:
> http://git.denx.de/?p=u-boot/u-boot-mips.git;a=commitdiff;h=bb246819cdc90493dd7089eaa51b9e639765cced
>
> changes from Heiko Schocher against this patch:
> - remove
On 20 April 2015 at 11:17, Heiko Schocher wrote:
> move common functions from cmd_nand.c (for calculating offset
> and size from cmdline paramter) to common place, so they could
> used from other commands which use mtd partitions.
>
> For onenand the arg_off_size() is left in common/cmd_onenand.c.
On 20 April 2015 at 11:17, Heiko Schocher wrote:
> with this patch, it is possible to get the offset and size information
> from the mtdpartiton setting in "mtdparts", similiar to the
> "nand" commandos.
>
> => sf
> sf - SPI flash sub-system
>
> Usage:
> sf probe [[bus:]cs] [hz] [mode] - init flas
On 23 December 2014 at 13:45, Jagan Teki wrote:
> Hi Heiko,
>
> On 23 December 2014 at 12:04, Heiko Schocher wrote:
>> Hello Jagan,
>>
>> Am 22.12.2014 09:58, schrieb Jagan Teki:
>>>
>>> On 18 December 2014 at 19:21, Jagannadha Sutradharudu Teki
>>> wrote:
This reverts commit 562f8df18
On 13 January 2015 at 11:35, Stefan Roese wrote:
> Hi Wolfgang,
>
> On 12.01.2015 22:10, Wolfgang Denk wrote:
Should we add a memset(buf, 0, sizeof(buf)) before the memcpy() to
prevent information from earlier activities to leak?
>>>
>>>
>>> "buf" points to the new data to be writ
On 15 July 2014 at 02:07, Tom Rini wrote:
> On Sat, Jul 12, 2014 at 06:42:31PM +0530, Jagan Teki wrote:
>> On Sat, Jul 12, 2014 at 2:23 AM, Tom Rini wrote:
>> > From: Vinothkumar Rajendran
>> >
>> > By default QSPI data through-put in memory mapped mode is ~2.4MB/sec @
>> > 48MHz. Added edma mem
On 22.04.2015 13:11, Jagan Teki wrote:
On 12.01.2015 22:10, Wolfgang Denk wrote:
Should we add a memset(buf, 0, sizeof(buf)) before the memcpy() to
prevent information from earlier activities to leak?
"buf" points to the new data to be written into the flash. We're
overwriting the first "l
On 22 April 2015 at 16:45, Stefan Roese wrote:
> On 22.04.2015 13:11, Jagan Teki wrote:
>>>
>>> On 12.01.2015 22:10, Wolfgang Denk wrote:
>>
>>
>> Should we add a memset(buf, 0, sizeof(buf)) before the memcpy() to
>> prevent information from earlier activities to leak?
>
On 20 March 2015 at 10:49, Peng Fan wrote:
> Need to check value of spi_setup_slave and spi_setup_slave_fdt.
> If their return value 'bus' is NULL, there is no need to pass it
> to following spi_flash_probe_tail.
>
> If 'bus' is null, the original function flow is as following:
> spi_flash_probe
>
On 21 April 2015 at 00:07, Simon Glass wrote:
> This comment should refer to SPI, not serial.
>
> Signed-off-by: Simon Glass
> ---
>
> include/spi.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/spi.h b/include/spi.h
> index c58e453..aa0598b 100644
> --- a/incl
On Wednesday, April 22, 2015 at 08:49:42 AM, Ramneek Mehresh wrote:
> Enable USB IP support for both EHCI and XHCI for
> ls1021atwr platform
>
> Signed-off-by: Ramneek Mehresh
> ---
> include/configs/ls1021atwr.h | 29 +
> include/linux/usb/xhci-fsl.h | 5 +
> 2
On Wednesday, April 22, 2015 at 08:49:41 AM, Ramneek Mehresh wrote:
> Add xhci driver support for all FSL socs
>
> Signed-off-by: Ramneek Mehresh
Hi!
[...]
> diff --git a/drivers/usb/host/xhci-fsl.c b/drivers/usb/host/xhci-fsl.c
> new file mode 100644
> index 000..9d89313
> --- /dev/null
>
On Tue, Apr 21, 2015 at 2:59 PM, Masahiro Yamada
wrote:
> Masahiro Yamada (5):
> ARM: ARM720t: remove empty asm/arch/hardware.h
> ARM: integrator: move board select into mach-integrator/Kconfig
> ARM: integrator: split board select into AP/CP select and CM select
> ARM: integrator: abolis
Hi Nikolay,
On 17/04/2015 00:36, Nikolay Dimitrov wrote:
> This is proposal for clamping the MMDC/DDR3 clocks to the maximum supported
> frequencies as per imx6 SOC models, and for dynamically calculating valid
> clock value based on mem_speed.
>
> Currently the code uses impossible values for me
Hi Stefano,
On 04/22/2015 03:12 PM, Stefano Babic wrote:
Hi Nikolay,
On 17/04/2015 00:36, Nikolay Dimitrov wrote:
This is proposal for clamping the MMDC/DDR3 clocks to the maximum supported
frequencies as per imx6 SOC models, and for dynamically calculating valid
clock value based on mem_speed
On 16/04/2015 15:20, Tim Harvey wrote:
> On Thu, Apr 16, 2015 at 12:46 AM, Stefano Babic wrote:
>> Hi Tim,
>>
>> I have no problem with the whole series, I will start to apply. Just a
>> couple of questions:
>>
>> On 08/04/2015 21:54, Tim Harvey wrote:
>>> Certain older kernels in use by some cust
Hi Tim,
On 21/04/2015 06:13, Tim Harvey wrote:
> On Thu, Apr 9, 2015 at 10:56 AM, Simon Glass wrote:
>> Hi Tim,
>>
>> On 8 April 2015 at 12:45, Tim Harvey wrote:
>>>
>>> Add 'fdt_fixup_display' function to fixup device-tree native-mode property
>>> of display-timings node to select timings for a
On 04/21/2015 08:26 PM, Jagannadha Sutradharudu Teki wrote:
> Move the header code into driver for more readable and
> easy to access it.
>
> Signed-off-by: Jagannadha Sutradharudu Teki
> Cc: Michal Simek
> ---
> drivers/spi/xilinx_spi.c | 113 +-
> drivers/s
On 04/21/2015 08:27 PM, Jagannadha Sutradharudu Teki wrote:
> - Zap unneeded macros
> - Re-arrange the code
> - Removed __attribute__((weak))
> - Replace __func__ macro with func names to save macro transition.
> - Re-arranged comment lines.
> - Arrange driver code in more readable format[1]
>
> [
On 04/04/2015 01:56, Tim Harvey wrote:
> The LDO_EN is bit 4, not value 4. This is only used on the Ventana boards so
> we will change it in the header as the other values there are in terms of
> values and not bit numbers.
>
> Signed-off-by: Tim Harvey
> ---
Applied to u-boot-imx, thanks !
Bes
On 04/04/2015 01:52, Tim Harvey wrote:
> DDR3 has a special Precharge power-down mode: fast-exit vs slow-exit.
>
> In slow-exit mode the DLL is off but in some quiescent state that makes it
> easy
> to turn on again in tXPDLL cycles (about 10tCK) vs the full tDLLK (512tCK).
> In fast-exist mode t
On 08/04/2015 21:54, Tim Harvey wrote:
> This collection of patches comprises a set of various updates that has
> been sitting in my queue for a while.
>
> There are a couple of patches pending that this series depends on:
> - fdt: add new fdt_fixup_display function to configure display
> - arm:
On 26/03/2015 23:53, Jörg Krause wrote:
> Reading the boot mode pins after power-up does not necessarily represent the
> boot mode used by the ROM loader. For example the state of a pin may have
> changed because a recovery switch which was pressed to enter USB mode is
> already released after plug
On 22/04/2015 14:22, Nikolay Dimitrov wrote:
> Hi Stefano,
>
> On 04/22/2015 03:12 PM, Stefano Babic wrote:
>> Hi Nikolay,
>>
>> On 17/04/2015 00:36, Nikolay Dimitrov wrote:
>>> This is proposal for clamping the MMDC/DDR3 clocks to the maximum
>>> supported
>>> frequencies as per imx6 SOC models,
On 06/04/2015 09:35, Gaurav Rana wrote:
> Move the compilation of file fsl_validate.c in MACRO CONFIG_CMD_ESBC_VALIDATE.
> This file should be compiled only when the above MACRO is defined
>
> This caused a break in compilation of iMX platforms when compiling for
> SECURE_BOOT
>
> Signed-off-by:
Hi Eric,
On 16/04/2015 20:31, Eric Nelson wrote:
> Signed-off-by: Eric Nelson
> ---
> include/configs/nitrogen6x.h | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/include/configs/nitrogen6x.h b/include/configs/nitrogen6x.h
> index 8ef4b73..0ca02e9 100644
> --- a/include/configs/nitr
On 20/04/2015 19:48, Fabio Estevam wrote:
> From: Fabio Estevam
>
> Add the initial SPL support for HummingBoard-i2eX, which is based on a
> MX6 Dual.
>
> For more information about HummingBoard, please check:
> http://www.solid-run.com/products/hummingboard/
>
> Based on the work from Jon Net
On 12/03/2015 16:34, Stefan Roese wrote:
> This patch extracts all baseboard specific defines into a separate config
> file.
> This makes it easier to add other baseboards that use the TQMa6 SoM.
>
> This patch will be used by the upcoming WRU-IV board support which also
> uses the TQMa6 SoM.
>
On 17/04/2015 03:11, Fabio Estevam wrote:
> From: Fabio Estevam
>
> mx6sabresd has four MT41K128M16JT-125 chips. Each memory has 16-bit bus
> and 2GiB, so fix the width and density fields accordingly.
>
> Signed-off-by: Fabio Estevam
> ---
Applied to u-boot-imx, thanks !
Best regards,
Stefan
On 17/04/2015 03:11, Fabio Estevam wrote:
> From: Fabio Estevam
>
> RTT_NOM_120OHM is not defined, so remove its ifdef.
>
> Signed-off-by: Fabio Estevam
> ---
Applied to u-boot-imx, thanks !
Best regards,
Stefano Babic
--
On Tue, Apr 21, 2015 at 11:17 PM, Igor Grinberg wrote:
> Hi Tim,
>
> Sorry for that late reply. I guess better late then never...
>
>
> Yes, I did this for several of our boards.
> I really wanted to clean it up and push upstream, but I barely had time
> to implement it in some way to make it wor
Hi,
On 04/16/2015 02:57 PM, thomas.lan...@lantiq.com wrote:
> Hello Michal,
>
> Michal Simek wrote on 2015-04-16:
>> From: Siva Durga Prasad Paladugu
>>
>> Fix wrong timer calculation in get_timer_masked incase of overflow. This
>> fixes the issue of getting wrong time from get_timer() calls.
>>
Some catches on this!
On 22 April 2015 at 15:29, Jagannadha Sutradharudu Teki
wrote:
> Upto now flash sector_size is assigned from params which isn't
> necessarily a sector size from vendor, so based on the SECT_*
> flags from flash_params the erase_size will compute and it will
> become the sect
Hi,
I've been trying to use fastboot (and especially the boot command) on
sunxi recently, and got it to work pretty fine (apart from PSCI, but
that's another story).
The only thing that worries me a bit is that by default, both the
fastboot tool and mkbootimg will generate an image with the kerne
On Wed, Apr 22, 2015 at 12:35 AM, Simon Glass wrote:
> On 21 April 2015 at 07:36, Linus Walleij wrote:
>> This switches the Integrator boards over to using the device model
>> for its serial ports.
>>
>> Cc: Masahiro Yamada
>> Signed-off-by: Linus Walleij
(...)
>> +#define CONFIG_SYS_MALLOC_F_L
On Thu, Apr 16, 2015 at 09:30:14AM +0200, Albert ARIBAUD wrote:
> Hello Tom,
>
> On Tue, 3 Feb 2015 15:21:53 -0500, Tom Rini wrote:
> > - Move the obj- lines for memset.S/memcpy.S to outside of an SPL check
> > so that SPL can use them as well.
> > - Make sure memset() / memcpy() end up in a t
Commit 1565d54a7671a1 ("imx:mx6sxsabresd board spl support") introduced the
SPL support, but described the memory layout incorrectly.
mx6sxsabresd board has two MT41K256M16HA-125 DDR3 chips.
Each MT41K256M16HA-125 has 16-bit width, giving a total bus width of 32 bits and
1GiB of RAM space, so fi
Hi Nikolay,
On 22/04/2015 14:22, Nikolay Dimitrov wrote:
> Hi Stefano,
>
> On 04/22/2015 03:12 PM, Stefano Babic wrote:
>> Hi Nikolay,
>>
>> On 17/04/2015 00:36, Nikolay Dimitrov wrote:
>>> This is proposal for clamping the MMDC/DDR3 clocks to the maximum
>>> supported
>>> frequencies as per imx6
On Tue, Apr 21, 2015 at 07:51:04AM -0500, Franklin S Cooper Jr wrote:
> Across several devices network environment variables are duplicated.
> Move these variables to a common include file which insures the environment
> variables are reused and insures devices across product lines share the same
On Wed, Apr 22, 2015 at 04:45:05PM +0530, Jagan Teki wrote:
> On 15 July 2014 at 02:07, Tom Rini wrote:
> > On Sat, Jul 12, 2014 at 06:42:31PM +0530, Jagan Teki wrote:
> >> On Sat, Jul 12, 2014 at 2:23 AM, Tom Rini wrote:
> >> > From: Vinothkumar Rajendran
> >> >
> >> > By default QSPI data thro
On Tue, 21 Apr 2015 07:18:24 +0200
Jan Kiszka wrote:
Hi Jan,
> CONFIG_ARMV7_VIRT depends on CONFIG_ARMV7_NONSEC,
Is this Kconfig rule always enforced these days? Or can one get away
without it by using stuff from include/configs/*.h?
> thus doesn't need to
> be taken into account additionally.
On 2015-04-22 16:03, Andre Przywara wrote:
> On Tue, 21 Apr 2015 07:18:24 +0200
> Jan Kiszka wrote:
>
> Hi Jan,
>
>> CONFIG_ARMV7_VIRT depends on CONFIG_ARMV7_NONSEC,
>
> Is this Kconfig rule always enforced these days? Or can one get away
> without it by using stuff from include/configs/*.h?
On Tue, Apr 21, 2015 at 12:37:18PM +0900, Masahiro Yamada wrote:
> Currently, CONFIG_SPL_LIBGENERIC_SUPPORT must be defined
> to build under lib/ directory for SPL.
>
> This directory contains very basic functions such as memcpy, memset
> in lib/string.c, so it should be very useful for all the bo
Hi,
On 22 April 2015 at 04:07, Marek Vasut wrote:
> On Wednesday, April 22, 2015 at 11:19:53 AM, Stefan Roese wrote:
>> Hi Tom,
>>
>> On 08.04.2015 16:01, Simon Glass wrote:
>> > On 7 April 2015 at 20:50, Simon Glass wrote:
>> >> On 30 March 2015 at 21:47, Masahiro Yamada
>> >>
>> >> wrote:
>>
Hi Simon,
On 22.04.2015 16:39, Simon Glass wrote:
Applied to u-boot-dm/next, thanks!
Do you plan to release a v2015.04.1 stable release at some time? Then
please add this patch to this version. As it fixes SPI NOR flash on
SoCFPGA.
Maybe we should consider u-boot-stable ...
In this case,
On Wed, Apr 22, 2015 at 03:17:03PM +0200, Linus Walleij wrote:
> On Wed, Apr 22, 2015 at 12:35 AM, Simon Glass wrote:
> > On 21 April 2015 at 07:36, Linus Walleij wrote:
> >> This switches the Integrator boards over to using the device model
> >> for its serial ports.
> >>
> >> Cc: Masahiro Yamad
Hi Stefan,
On 22 April 2015 at 08:42, Stefan Roese wrote:
> Hi Simon,
>
> On 22.04.2015 16:39, Simon Glass wrote:
>
> Applied to u-boot-dm/next, thanks!
Do you plan to release a v2015.04.1 stable release at some time? Then
please add this patch to this version. As it fixes
This is proposal for clamping the MMDC/DDR3 clocks to the maximum supported
frequencies as per imx6 SOC models, and for dynamically calculating valid
clock value based on mem_speed.
Currently the code uses impossible values for mem_speed (1333, 1600 MT/s) for
calculating the DDR timings, and uses
On Mon, Apr 20, 2015 at 02:05:58PM -0700, York Sun wrote:
> Tom,
>
> The following changes since commit b8d7652c81689a69bc6eaa206cf875bbe632831c:
>
> Merge branch 'buildman' of git://git.denx.de/u-boot-x86 (2015-04-18 19:24:13
> -0400)
>
> are available in the git repository at:
>
>
> git
On Wednesday, April 22, 2015 at 03:04:47 PM, Maxime Ripard wrote:
> Hi,
Hi!
> I've been trying to use fastboot (and especially the boot command) on
> sunxi recently, and got it to work pretty fine (apart from PSCI, but
> that's another story).
>
> The only thing that worries me a bit is that by
On Sat, Apr 18, 2015 at 08:07:02AM +0200, Jörg Krause wrote:
> This patch fixes cross-compiling U-Boot tools with the musl C library:
> * including is needed for ulong
> * defining _GNU_SOURCE is needed for loff_t
>
> Signed-off-by: Jörg Krause
> ---
> include/image.h| 1 +
> tools/env
Hi,
On 22 April 2015 at 06:38, Stefano Babic wrote:
>
> Hi Tim,
>
> On 21/04/2015 06:13, Tim Harvey wrote:
> > On Thu, Apr 9, 2015 at 10:56 AM, Simon Glass wrote:
> >> Hi Tim,
> >>
> >> On 8 April 2015 at 12:45, Tim Harvey wrote:
> >>>
> >>> Add 'fdt_fixup_display' function to fixup device-tree
Hi Przemyslaw,
On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
> Hello,
> Again the next version. The changes are described below each commit message.
> This is rebased on last u-boot-dm/master after apply this patchset:
> https://patchwork.ozlabs.org/patch/462775/
> https://patchwork.ozlabs
On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
> This config name was never used, because the present pmic command
> was precompiled for the CONFIG_POWER.
>
> Signed-off-by: Przemyslaw Marczak
> ---
> include/configs/exynos4-common.h | 1 -
> 1 file changed, 1 deletion(-)
Acked-by: Simon
On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
>
> Move the configs listed below from exynos5-dt-common.h to exynos5-common.h:
> - CONFIG_POWER
> - CONFIG_POWER_I2C
> fixes build break for Arndale and Smdk5250 boards.
>
> Signed-off-by: Przemyslaw Marczak
> ---
> include/configs/exynos5-co
On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
> Signed-off-by: Przemyslaw Marczak
> ---
> lib/Kconfig | 8
> 1 file changed, 8 insertions(+)
(please make sure to always add a commit message)
Acked-by: Simon Glass
___
U-Boot mailing l
On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
> This is new command for the PMIC devices based on driver model PMIC API.
> Command features are unchanged:
> - list UCLASS pmic devices
> - show or [set] operating pmic device (NEW)
> - dump registers
> - read byte of register at address
> - w
Hi Przemyslaw,
On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
> This command is based on driver model regulator's API.
> The user interface provides:
> - list UCLASS regulator devices
> - show or [set] operating regulator device
> - print constraints info
> - print operating status
> - prin
Hi Przemyslaw,
On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
> This commit introduces the implementation of dm regulator API.
> Device tree support allows for auto binding. And by the basic
> uclass operations, it allows to driving the devices in a common
> way. For detailed informations,
On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
> This is the implementation of driver model PMIC driver.
> The max77686 PMIC driver implements read/write operations and driver
> bind method - to bind its childs.
>
> This driver will try to bind the regulator devices by using it's child
> inf
On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
> This driver implements regulator operations for fixed Voltage/Current
> value regulators. beside the standard regulator constraints, which are
> put into the uclass platform data, a typical fixed regulator node provides
> few additional proper
Hi Przemyslaw,
On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
> This commit change the old pmic framework calls to the new ones.
>
> Signed-off-by: Przemyslaw Marczak
> ---
> Changes v2:
> - remove board_init_i2c() call
> - update regulator calls
> - update headers
> - samsung/misc.c: incl
Hi Przemyslaw,
On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
> Since this framework is still under the construction, the main
> documentation is kept in the header files.
>
> Signed-off-by: Przemyslaw Marczak
> ---
> Changes v2, V3:
> - update documentation with the framework api changes
On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
> This commit also updates the proper dts files.
>
> Signed-off-by: Przemyslaw Marczak
> ---
> arch/arm/dts/exynos4412-odroid.dts | 2 +-
> arch/arm/dts/exynos4412-trats2.dts | 2 +-
> arch/arm/dts/exynos5250-smdk5250.dts | 2 +-
> arch/ar
On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
> Adding regulators subnode to fdt max77686 node, allows properly init
> regulators by the max77686 regulator driver. This enables the complete
> functionality of the regulator command.
>
> Signed-off-by: Przemyslaw Marczak
> ---
> Changes V2:
On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
> This change enables the configs required to init and setup max77686
> regulator driver, using the new driver model pmic and regulator API.
>
> This commits enables:
> - CONFIG_ERRNO_STR
> - CONFIG_DM_PMIC
> - CONFIG_DM_PMIC_CMD
> - CONFIG_DM_P
On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
> In the power_init_board function call, regulator driver init is called,
> so before compile, make sure that any power framework is defined.
>
> Signed-off-by: Przemyslaw Marczak
> ---
> board/samsung/common/board.c | 4 ++--
> 1 file changed
The QEMU u-boot located itself at a 4k aligned offset which the rest
of the code didn't really expect. Align it with 64k to allow the memory
code to deal with 64k granularity.
This fixes broken interrupt delivery with the ppce500 machine for me.
Signed-off-by: Alexander Graf
---
include/configs
Hi Przemyslaw,
On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
> This commit introduces the PMIC uclass implementation.
> It allows providing the basic I/O interface for PMIC devices.
> For the multi-function PMIC devices, this can be used as I/O
> parent device, for each IC's interface. The
The macro to select the I2C address for ECC bus-width detection
was defined incorrectly for the Marvell DB-MV784MP-GP board. This
patch changes the macro to the correct value to fix this issue.
Signed-off-by: Stefan Roese
---
drivers/ddr/mvebu/ddr3_axp.h | 2 +-
1 file changed, 1 insertion(+), 1
On Tue, Apr 21, 2015 at 4:56 PM, Arun Bharadwaj wrote:
> - printf("Board revision: %d\n", get_board_revision());
It is still very useful to report the board revision on boot. Could
you restore this? The printf in get_board_revision doesn't appear
(too early in the boot perhaps?).
--Ash
__
Hi Arun,
I gave this patch a whirl and it works for me. As such:
Tested-by: Ash Charles
--Ash
On Tue, Apr 21, 2015 at 4:56 PM, Arun Bharadwaj wrote:
> u-boot breaks for the Overo boards since the following
> commit: a6b541b09022acb6f7c2754100ae26bd44eed1d9
>
> This is because the gd pointer i
On 20 April 2015 at 15:24, Simon Glass wrote:
> On 20 April 2015 at 05:32, Przemyslaw Marczak wrote:
>>
>> Uclass API provides a few functions for get/find the device.
>> To provide a complete function set of uclass-internal functions,
>> for use by the drivers, the function uclass_get_device_tai
On 20 April 2015 at 15:24, Simon Glass wrote:
> On 20 April 2015 at 05:32, Przemyslaw Marczak wrote:
>> This commit introduces simple tests for functions:
>> - uclass_find_device_by_name()
>> - uclass_get_device_by_name()
>>
>> Tests added by this commit:
>> - Test: dm_test_uclass_devices_find_by
On 20 April 2015 at 15:24, Simon Glass wrote:
> On 20 April 2015 at 05:32, Przemyslaw Marczak wrote:
>> The functions:
>> - uclass_find_device_by_name()
>> - uclass_get_device_by_name()
>> searches the required device for the exactly given name.
>> This patch, presice this fact for both function'
On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
> This commit adds support to MAX77686 regulator driver,
> based on a driver model regulator's API. It implements
> almost all regulator operations, beside those for setting
> and geting the Current value.
> For proper bind and operation it requ
On 22 April 2015 at 10:30, Simon Glass wrote:
> Hi Przemyslaw,
>
> On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
>> This commit introduces the implementation of dm regulator API.
>> Device tree support allows for auto binding. And by the basic
>> uclass operations, it allows to driving the
Yes, I can move get_board_revision into common.c. Then we can retain the
earlier printf.
On Wed, Apr 22, 2015 at 9:45 AM, Ash Charles wrote:
> On Tue, Apr 21, 2015 at 4:56 PM, Arun Bharadwaj wrote:
> > - printf("Board revision: %d\n", get_board_revision());
> It is still very useful to r
On 22 April 2015 at 10:29, Simon Glass wrote:
> On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
>> This config name was never used, because the present pmic command
>> was precompiled for the CONFIG_POWER.
>>
>> Signed-off-by: Przemyslaw Marczak
>> ---
>> include/configs/exynos4-common.h |
On 22 April 2015 at 10:29, Simon Glass wrote:
> On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
>>
>> Move the configs listed below from exynos5-dt-common.h to exynos5-common.h:
>> - CONFIG_POWER
>> - CONFIG_POWER_I2C
>> fixes build break for Arndale and Smdk5250 boards.
>>
>> Signed-off-by:
On 22 April 2015 at 10:54, Simon Glass wrote:
> On 22 April 2015 at 10:30, Simon Glass wrote:
>> Hi Przemyslaw,
>>
>> On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
>>> This commit introduces the implementation of dm regulator API.
>>> Device tree support allows for auto binding. And by th
On 22 April 2015 at 10:30, Simon Glass wrote:
> Hi Przemyslaw,
>
> On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
>> This commit introduces the PMIC uclass implementation.
>> It allows providing the basic I/O interface for PMIC devices.
>> For the multi-function PMIC devices, this can be us
On 22 April 2015 at 10:29, Simon Glass wrote:
> On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
>> Signed-off-by: Przemyslaw Marczak
>> ---
>> lib/Kconfig | 8
>> 1 file changed, 8 insertions(+)
>
> (please make sure to always add a commit message)
>
> Acked-by: Simon Glass
Appl
On 22 April 2015 at 10:30, Simon Glass wrote:
> On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
>> This is the implementation of driver model PMIC driver.
>> The max77686 PMIC driver implements read/write operations and driver
>> bind method - to bind its childs.
>>
>> This driver will try t
On 22 April 2015 at 10:30, Simon Glass wrote:
> On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
>> This is new command for the PMIC devices based on driver model PMIC API.
>> Command features are unchanged:
>> - list UCLASS pmic devices
>> - show or [set] operating pmic device (NEW)
>> - dum
On 22 April 2015 at 10:30, Simon Glass wrote:
> Hi Przemyslaw,
>
> On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
>> This command is based on driver model regulator's API.
>> The user interface provides:
>> - list UCLASS regulator devices
>> - show or [set] operating regulator device
>> - p
On 22 April 2015 at 10:31, Simon Glass wrote:
> On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
>> This commit adds support to MAX77686 regulator driver,
>> based on a driver model regulator's API. It implements
>> almost all regulator operations, beside those for setting
>> and geting the C
On 22 April 2015 at 10:31, Simon Glass wrote:
> Hi Przemyslaw,
>
> On 20 April 2015 at 12:07, Przemyslaw Marczak wrote:
>> Since this framework is still under the construction, the main
>> documentation is kept in the header files.
>>
>> Signed-off-by: Przemyslaw Marczak
>> ---
>> Changes v2, V3
1 - 100 of 141 matches
Mail list logo
