Add full support for USDHC2, USDHC3, USDHC4 on mx6sx sabresd board.
The default boot socket is USDHC4, so the MMC environment is set to
this device.
Signed-off-by: Ye.Li
---
Changes since v1:
- Modify the function return value
board/freescale/mx6sxsabresd/mx6sxsabresd.c | 99 +
The reset value of "uSDHCx_INT_STATUS_EN" register is changed to 0
on iMX6SX. So the fsl_esdhc driver must update to set the register,
otherwise no state can be detected.
Signed-off-by: Ye.Li
---
Changes since v1:
- Remove codes which set INT_STATUS_EN register according PIO or DMA mode.
driver
On Mon, Oct 13, 2014 at 3:56 AM, Alban Bedel
wrote:
>
> On Thu, 9 Oct 2014 17:17:00 +0200
> Marek Vasut wrote:
>
> > On Thursday, October 09, 2014 at 01:42:49 PM, Alban Bedel wrote:
> > > Many ethernet devices use an EEPROM to store various settings, most
> > > commonly the device MAC address. Bu
Configure the pad setting and enable qspi clock to support qspi
flashes access.
Signed-off-by: Peng Fan
---
Changelog v3:
none
Changelog v2:
Take Fabio's suggestion, split soc code and board code into two patches.
board/freescale/mx6sxsabresd/mx6sxsabresd.c | 40
Add QSPI support for mx6solox.
Signed-off-by: Peng Fan
---
Changelog v3:
none
Changelog v2:
Take Fabio's suggestion, split soc code and board code into two patches.
arch/arm/cpu/armv7/mx6/clock.c | 50
arch/arm/include/asm/arch-mx6/clock.h| 1
According cs, use different amba_base to choose the corresponding
flash devices. If not, `sf probe 1:0` and `sf probe 1:1` will
choose the same flash device, but not different flash devices.
Signed-off-by: Peng Fan
---
Changelog v3:
none
Changelog v2:
none
drivers/spi/fsl_qspi.c | 30 +
Use QSPI_CMD_xx instead of flash opcodes
Signed-off-by: Peng Fan
---
Changelog v3:
Use QSPI_CMD_XX instead of flash opcodes. To fsl qspi controller, the LUT
should be pre programmed with QSPI CMD.
Changelog v2:
none
drivers/spi/fsl_qspi.c | 64 ++
Adjust the sandbox SPI driver to support driver model and move sandbox over
to driver model for SPI.
Signed-off-by: Simon Glass
Reviewed-by: Jagannadha Sutradharudu Teki
---
Changes in v4: None
Changes in v3:
- Add implementation/comment for the cs_info() method
- Remove the child_pre_probe() m
This converts the Tegra SPI drivers to use driver model. This is tested
on:
- Tegra20 - trimslice
- Tegra30 - beaver
- Tegra124 - dalmore
(not tested on Tegra124)
Reviewed-by: Jagannadha Sutradharudu Teki
Signed-off-by: Simon Glass
---
Changes in v4:
- Drop the incorrect compulab hunk from th
This README is intended to help maintainers move their SPI drivers over to
driver model. It works through the required steps with an example.
Signed-off-by: Simon Glass
Reviewed-by: Jagannadha Sutradharudu Teki
---
Changes in v4: None
Changes in v3:
- Update for the new cs_info() method
Change
Adjust spi_flash_probe_slave() to return an error value instead of a
pointer so we get the correct error return.
Have the caller allocate memory for spi_flash to simplify error handling,
and also so that driver model can use its existing allocated memory.
Add a spi.h include in the sf_params file
Reserve the 'normal' name for use by driver model, and rename the old
driver so that it is clear that it is for 'legacy' drivers only.
Signed-off-by: Simon Glass
Reviewed-by: Jagannadha Sutradharudu Teki
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
drivers/spi/Makefile
Move the exynos SPI driver over to driver model. This removes quite a bit
of boilerplate from the driver, although it adds some for driver model.
A few device tree additions are needed to make the SPI flash available.
Signed-off-by: Simon Glass
Reviewed-by: Jagannadha Sutradharudu Teki
---
Cha
All boards with a SPI interface have a suitable spi alias except the tegra30
boards. Add these missing aliases.
Signed-off-by: Simon Glass
Reviewed-by: Jagannadha Sutradharudu Teki
---
Changes in v4: None
Changes in v3:
- Add new patch to add aliases for spi on tegra30 boards
Changes in v2: No
We want the SPI flash probing feature to operate as a standard driver.
Add a driver for the basic probing feature used by most boards. This
will be activated by device_probe() as with any other driver.
The 'sf probe' command currently keeps track of the SPI slave that it
last used. This doesn't wo
These tests use SPI flash (and the sandbox emulation) to operate.
Signed-off-by: Simon Glass
Acked-by: Jagannadha Sutradharudu Teki
---
Changes in v4: None
Changes in v3:
- Expand SPI tests to cover compatibility functions
- Minor renames for clarity
Changes in v2:
- Create a 'spi.bin' file fo
Use driver model for exynos5 board SPI flash.
Signed-off-by: Simon Glass
Reviewed-by: Jagannadha Sutradharudu Teki
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
include/configs/exynos-common.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/configs/exynos-common.
Adjust the sandbox cros_ec emulation driver to work with driver model, and
switch over to driver model for sandbox cros_ec.
Signed-off-by: Simon Glass
Acked-by: Jagannadha Sutradharudu Teki
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
drivers/misc/cros_ec_sandbox.c | 90 +++
Adjust this driver to use driver model and move smdk5420 boards over to
use it.
Series-changes 4
- Add review/ack tags for SPI maintainer (Jagan)
Acked-by: Jagannadha Sutradharudu Teki
Signed-off-by: Simon Glass
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
drivers/misc/cro
Add support for driver model if enabled. This involves minimal changes
to the code, mostly just plumbing around the edges.
Signed-off-by: Simon Glass
Acked-by: Jagannadha Sutradharudu Teki
---
Changes in v4:
- Remove a extra tab character (oops)
Changes in v3:
- Add a missing tab character
Ch
U-Boot includes a SPI emulation driver already but it is not explicit, and
is hidden in the SPI flash code.
Conceptually with sandbox's SPI implementation we have a layer which
creates SPI bus transitions and a layer which interprets them, currently
only for SPI flash. The latter is actually an em
Convert sandbox's spi flash emulation driver to use driver model.
Signed-off-by: Simon Glass
Reviewed-by: Jagannadha Sutradharudu Teki
---
Changes in v4: None
Changes in v3:
- Add a few more debug() statements
- Use an explicit chip select value instead of reusing device sequence number
Change
Since spi_flash.h is supposed to be the public API for SPI flash, move
private things to sf_internal.h. Also tidy up a few comment nits.
Signed-off-by: Simon Glass
Reviewed-by: Jagannadha Sutradharudu Teki
---
Changes in v4: None
Changes in v3:
- Add spi.h header to 3 sh boards
- Rebase to mast
Add a simple test for SPI that uses SPI flash. It operates by creating a
SPI flash file and using the 'sf test' command to test that all
operations work correctly.
Signed-off-by: Simon Glass
Acked-by: Jagannadha Sutradharudu Teki
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
Add a driver model uclass for SPI flash which supports the common
operations (read, write, erase). Since we must keep support for the
non-dm interface, some modification of the spi_flash header is required.
CONFIG_DM_SPI_FLASH is used to enable driver model for SPI flash.
Signed-off-by: Simon Gla
This feature provides for init of a single SPI port for the soft SPI
feature. It is not really compatible with driver model since it assumes a
single SPI port. Also, inserting SPI init into the driver by means of
a #define is not very nice.
This feature is not used by any active boards, so let's r
Add a new implementation of soft_spi that uses device tree to specify the
GPIOs. This will replace soft_spi_legacy for boards which use driver model.
Signed-off-by: Simon Glass
Reviewed-by: Jagannadha Sutradharudu Teki
---
Changes in v4: None
Changes in v3:
- Word-wrap the first paragraph of th
The sequence number is unique within the uclass, so state this clearly.
Signed-off-by: Simon Glass
Acked-by: Jagannadha Sutradharudu Teki
---
Changes in v4: None
Changes in v3:
- Add new patch to add a clarifying comment on struct udevice's seq member
Changes in v2: None
doc/driver-model/REA
Adjust this board to use the driver model soft_spi implementation.
Signed-off-by: Simon Glass
Reviewed-by: Jagannadha Sutradharudu Teki
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
arch/arm/dts/exynos4210-universal_c210.dts | 13
board/samsung/universal_c210/univer
Driver model does its own init, so we don't need this.
There is still a call in board_f.c but it is only enabled by CONFIG_HARD_SPI.
It is easy enough to disable that option when converting boards which use
it to driver model.
Signed-off-by: Simon Glass
Reviewed-by: Jagannadha Sutradharudu Teki
Add a uclass which provides access to SPI buses and includes operations
required by SPI.
For a time driver model will need to co-exist with the legacy SPI interface
so some parts of the header file are changed depending on which is in use.
The exports are adjusted also since some functions are not
Buses sometimes want to pass data to their children when they are probed.
For example, a SPI bus may want to tell the slave device about the chip
select it is connected to.
Add a new function to permit the parent data to be supplied to the child.
Signed-off-by: Simon Glass
Acked-by: Jagannadha S
Buses need to iterate through their children in some situations. Add a few
functions to make this easy.
Signed-off-by: Simon Glass
Acked-by: Jagannadha Sutradharudu Teki
---
Changes in v4: None
Changes in v3:
- Add new functions to iterate through device children
Changes in v2: None
doc/driv
Add a SPI device which can be used for testing SPI flash features in
sandbox.
Also add a cros_ec device since with driver model the Chrome OS EC
emulation will not otherwise be available.
Reviewed-by: Jagannadha Sutradharudu Teki
Signed-off-by: Simon Glass
---
Changes in v4: None
Changes in v3
Some files are using SPI functions but not explitly including the SPI
header file. Fix this, since driver model needs it.
Signed-off-by: Simon Glass
Reviewed-by: Jagannadha Sutradharudu Teki
---
Changes in v4: None
Changes in v3: None
Changes in v2:
- Add spi.h header to dfu_sf.c
common/env_s
Up until now driver model has not been used for any type of bus. Buses
have some unique properties and needs, so we cannot claim that driver
model can cover all the common cases unless we have converted a bus over
to driver model.
SPI is a reasonable choice for this next step. It has a fairly simp
Driver model uses a different way to find the SPI bus and slave from the
numbered devices given on the command line. Adjust the code to suit.
We use a generic SPI device, and attach it to the SPI bus before performing
the transaction.
Signed-off-by: Simon Glass
Reviewed-by: Jagannadha Sutradharu
Hi Akshay,
On 13 October 2014 23:05, Akshay Saraswat wrote:
> Hi Simon,
>
>>
>>Hi Akshay,
>>
>>On 10 October 2014 05:50, Akshay Saraswat wrote:
>>>
>>> Hi Simon,
>>>
>>> >
>>> >Hi Akshay,
>>> >
>>> >On 8 October 2014 02:10, Akshay Saraswat wrote:
>>> >> Now we are adding a new Peach-Pi board whic
Hi Minkyu,
On 9 October 2014 00:00, Simon Glass wrote:
> Hi Minkyu,
>
> On 14 September 2014 16:29, Simon Glass wrote:
>> (Note: Tegra patches have been applied, I am resending with exynos only)
>>
>> Now that driver model is part of U-Boot, the task of converting drivers over
>> to it begins. G
Hi,
This question came up at the U-Boot mini-summit yesterday and I was
tasked with starting a thread on the mailing list.
There seemed to be a strong feeling in the room that permitting
platform data in driver model is a mistake. Reasons mentioned were:
- device tree is how things are done in L
Hi Akshay,
On 10 October 2014 05:50, Akshay Saraswat wrote:
>
> Hi Simon,
>
> >
> >Hi Akshay,
> >
> >On 8 October 2014 02:10, Akshay Saraswat wrote:
> >> Now we are adding a new Peach-Pi board which is a variant of Peach-Pit
> >> and is based on Exynos5800. Exynos5800 itself is a variant of Exyn
> -Original Message-
> From: Albert ARIBAUD [mailto:albert.u.b...@aribaud.net]
> Sent: Monday, October 13, 2014 5:46 PM
> To: Tang Yuantian-B29983
> Cc: u-boot@lists.denx.de; Jin Zhengxiong-R64188; Sun York-R58495
> Subject: Re: [PATCH 0/4] Deep sleep patches for Freescale QorIQ platforms
>
On Mon, Oct 13, 2014 at 9:38 AM, Tom Rini wrote:
> On Mon, Oct 13, 2014 at 09:08:09AM -0300, Otavio Salvador wrote:
>> On Mon, Oct 13, 2014 at 5:53 AM, Tom Rini wrote:
>> > On Sun, Oct 12, 2014 at 05:48:37PM -0300, Otavio Salvador wrote:
>> >> The 'tools-only' target seems to be broken.
>> >>
>>
On Mon, Oct 13, 2014 at 4:51 AM, Ye.Li wrote:
> int board_mmc_init(bd_t *bis)
> {
> - imx_iomux_v3_setup_multiple_pads(usdhc2_pads,
> ARRAY_SIZE(usdhc2_pads));
> + int i;
> +
> + /*
> +* According to the board_mmc_init() the following map is done:
> +* (U-boot
On Mon, Oct 13, 2014 at 6:16 AM, Ye.Li wrote:
> The reset value of "uSDHCx_INT_STATUS_EN" register is changed to 0
> on iMX6SX. So the fsl_esdhc driver must update to set the register,
> otherwise no state can be detected.
>
> Signed-off-by: Ye.Li
This patch seems to do more than described on th
On Mon, Oct 13, 2014 at 02:51:40PM +0200, Hans de Goede wrote:
> Currently uboot wrongly uses 25mV / step for dcdc3, this is a copy and paste
> error introduced when adding the axp152_mvolt_to_target during review of the
> axp152.c driver. This results in u-boot setting Vddr to 2.3V instead of 1.5
On Sun, Oct 12, 2014 at 04:23:05PM +0800, Chen-Yu Tsai wrote:
> On Sun, Oct 12, 2014 at 12:05 AM, Ian Campbell wrote:
> > On Tue, 2014-10-07 at 15:11 +0800, Chen-Yu Tsai wrote:
> >> From: Hans de Goede
> >>
> >> The A31, A23 and later SoCs have an extra pin controller, called CPUs_PIO
> >> or R_P
On Mon, Oct 13, 2014 at 9:38 AM, Ye.Li wrote:
> On mx6 sabreauto board, there are two USB ports:
> 0: OTG
> 1: HOST
> The EHCI driver is enabled for this board, but the IOMUX and VBUS power
> control is not implemented, which cause both USB port failed to work.
> This patch fix the problem by addi
Many people are still using old linux-sunxi-3.4 kernels on sunxi devices,
adding the proper MACH_TYPE defines for this allows people to switch to
upstream u-boot, so that we can stop maintaining the linux-sunxi u-boot fork.
These machine-ids are all properly registered at:
http://www.arm.linux.or
Currently uboot wrongly uses 25mV / step for dcdc3, this is a copy and paste
error introduced when adding the axp152_mvolt_to_target during review of the
axp152.c driver. This results in u-boot setting Vddr to 2.3V instead of 1.5V.
This commit fixes this.
Signed-off-by: Hans de Goede
---
driver
Hi Tom,
Here is a last minute fix for v2014.10 to fix the axp152 code setting the
DRAM voltage way too high on some sunxi boards (2.3V instead of 1.5V).
I hope this can still make v2014.10, if not it is not too bad as most boards
use the axp209, not the axp152, and the axp152 boards I've seem to
On mx6 sabreauto board, there are two USB ports:
0: OTG
1: HOST
The EHCI driver is enabled for this board, but the IOMUX and VBUS power
control is not implemented, which cause both USB port failed to work.
This patch fix the problem by adding the board support codes.
Since the power control uses t
With the introduction of CONFIG_LOCALVERSION support we cannot build
tools without having a config file (as we won't know our PLAIN_VERSION
until then).
Reported-by: Otavio Salvador
Signed-off-by: Tom Rini
---
Makefile |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makef
On Mon, Oct 13, 2014 at 09:08:09AM -0300, Otavio Salvador wrote:
> On Mon, Oct 13, 2014 at 5:53 AM, Tom Rini wrote:
> > On Sun, Oct 12, 2014 at 05:48:37PM -0300, Otavio Salvador wrote:
> >> The 'tools-only' target seems to be broken.
> >>
> >> In a clean tree (no previous build) running:
> >>
> >>
On Mon, Oct 13, 2014 at 5:53 AM, Tom Rini wrote:
> On Sun, Oct 12, 2014 at 05:48:37PM -0300, Otavio Salvador wrote:
>> The 'tools-only' target seems to be broken.
>>
>> In a clean tree (no previous build) running:
>>
>> $: make tools-only
>>
>> fails with:
>>
>> CHK include/config/uboot.rele
Signed-off-by: Dileep Katta
---
Changes in v2:
-None
Changes in v3:
-None
Changes in v4:
-None
-Fastboot flash command changes by Steve Rae are in mainline
This enables the code for BeagleBone Black
Hi Ye Li,
On Mon, Oct 13, 2014 at 2:56 AM, Li Ye-B37916 wrote:
> I will update per your comments.
>
> For the copyright, in FSL we are asked to update it when applying any change
> to the file. what's the rule used in community?
Yes, that internal script does not make sense. I would say just l
Hi Yuantian,
On Mon, 13 Oct 2014 09:41:35 +, Yuantian Tang
wrote:
> PING.
This submission is only 4 days old, across a week ending. Can you please
wait a bit longer before pinging?
> Thanks,
> Yuantian
Amicalement,
--
Albert.
___
U-Boot mailing
PING.
Thanks,
Yuantian
> -Original Message-
> From: yuantian.t...@freescale.com [mailto:yuantian.t...@freescale.com]
> Sent: Thursday, October 09, 2014 4:12 PM
> To: albert.u.b...@aribaud.net
> Cc: u-boot@lists.denx.de; Jin Zhengxiong-R64188; Sun York-R58495; Tang
> Yuantian-B29983
> Subj
The reset value of "uSDHCx_INT_STATUS_EN" register is changed to 0
on iMX6SX. So the fsl_esdhc driver must update to set the register,
otherwise no state can be detected.
Signed-off-by: Ye.Li
---
drivers/mmc/fsl_esdhc.c | 13 +
1 files changed, 13 insertions(+), 0 deletions(-)
dif
Add full support for USDHC2, USDHC3, USDHC4 on mx6sx sabresd board.
The default boot socket is USDHC4, so the MMC environment is set to
this device.
Signed-off-by: Ye.Li
---
board/freescale/mx6sxsabresd/mx6sxsabresd.c | 96 +--
include/configs/mx6sxsabresd.h
On Mon, Oct 13, 2014 at 08:48:39AM +0200, Jeroen Hofstee wrote:
> Hello Simon,
>
> On 13-10-14 07:14, Simon Glass wrote:
> >Hi Jeroen,
> >
> >On 12 October 2014 10:13, Jeroen Hofstee wrote:
> >
> >>Hello Hans,
> >>
> >>On 12-10-14 12:25, Hans de Goede wrote:
> >>
> >>>Hi,
> >>>
> >>>This one seem
On Thu, 9 Oct 2014 17:17:00 +0200
Marek Vasut wrote:
> On Thursday, October 09, 2014 at 01:42:49 PM, Alban Bedel wrote:
> > Many ethernet devices use an EEPROM to store various settings, most
> > commonly the device MAC address. But on some devices it can contains
> > a lot more, for example USB
On Sun, Oct 12, 2014 at 05:48:37PM -0300, Otavio Salvador wrote:
> The 'tools-only' target seems to be broken.
>
> In a clean tree (no previous build) running:
>
> $: make tools-only
>
> fails with:
>
> CHK include/config/uboot.release
> /bin/sh: 1: cannot open include/config/auto.conf: N
There are three SD/MMC sockets on mx6slevk boards. Implements the
full support for them.
The default boot socket is USDHC2, so the MMC environment is set
to that device.
Signed-off-by: Ye.Li
---
board/freescale/mx6slevk/mx6slevk.c | 101 --
include/configs/mx6sle
Set the USDHC1-3 IOMUX settings which are used for mx6slevk board.
Signed-off-by: Ye.Li
---
arch/arm/include/asm/arch-mx6/mx6sl_pins.h | 19 +++
1 files changed, 19 insertions(+), 0 deletions(-)
diff --git a/arch/arm/include/asm/arch-mx6/mx6sl_pins.h
b/arch/arm/include/asm/ar
On Mon, 2014-10-13 at 06:48 +0200, Hans de Goede wrote:
> Hi,
>
> On 10/12/2014 11:19 PM, Ian Campbell wrote:
> > On Sun, 2014-10-12 at 20:07 +0200, Hans de Goede wrote:
> >> Hi Ian,
> >>
> >> Here is v3 of my second sdcard slot patch-set.
> >>
> >> Changes since v2:
> >> - Rebased on top of lates
67 matches
Mail list logo
