Hello Masahiro,
On Mon, 13 Jul 2015 13:17:03 +0900, Masahiro Yamada
wrote:
>
> Please refer to the commit message of 06/14
> for what this series wants to do.
Remark: you could use "Series-notes:" in 6/14 to have patman directly
include said notes here instead of referring the reader to the pat
Hello Bin Liu,
Am 10.07.2015 um 17:31 schrieb Bin Liu:
Hi,
On 07/10/2015 10:12 AM, Heiko Schocher wrote:
Hello Samuel,
Am 10.07.2015 um 16:50 schrieb Egli, Samuel:
Hi Hans,
-Original Message- From: Hans de Goede
[mailto:hdego...@redhat.com] Sent: Freitag, 10. Juli 2015 16:37
To: Eg
Hello David,
Am 11.07.2015 um 20:54 schrieb David Cemin:
Hi,
I am trying to do pretty much the same thing as described here:
http://lists.denx.de/pipermail/u-boot/2014-April/178252.html
Is the described procedure (copied below) only valid after applying the
patch ?
The patch [1] reffered in
Currently, kzalloc() returns zero-filled memory, while kmalloc()
simply ignores the second argument and never fills the memory
area with zeros.
I want kmalloc(size, __GFP_ZERO) to behave as kzalloc() does,
which will make it easier to add more memory allocator variants.
With the introduction of _
It does not seem efficient to always return cache-aligned memory.
Return aligned memory only when GFP_DMA flag is given.
My main motivation for this commit is to refactor device_probe()
and device_free() in the next commit. DM_FLAG_ALLOC_PRIV_DMA
should be handled more easily.
Signed-off-by: Mas
Please refer to the commit message of 06/14
for what this series wants to do.
Masahiro Yamada (14):
x86: delete unneeded declarations of disable_irq() and enable_irq()
linux_compat: remove cpu_relax() define
linux_compat: move vzalloc() to header file as an inline function
linux_compat:
The memory is automatically released on driver removal, so we do not
need to do so explicitly in device_free().
The helper function alloc_priv() is no longer needed because
devm_kzalloc() now understands the GFP_DMA flag.
Signed-off-by: Masahiro Yamada
Reviewed-by: Heiko Schocher
---
Changes i
As you see in driver/Makefile, Kbuild descends into the driver/core/
directory only when CONFIG_DM is enabled.
Signed-off-by: Masahiro Yamada
---
Changes in v2:
- Newly added
drivers/core/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/core/Makefile b/dri
The macro cpu_relax() is defined by several headers in different
ways.
arch/{arm,avr32,mips}/include/asm/processor.h defines it as follows:
#define cpu_relax() barrier()
On the other hand, include/linux/compat.h defines it as follows:
#define cpu_relax() do {} while (0)
If both headers are
This new command can dump all device resources associated to
each device. The fields in every line shows:
- The address of the resource
- The size of the resource
- The name of the release function
- The stage in which the resource has been acquired (BIND/PROBE)
The output looks like this
Currently, Devres requires additional 16 byte for each allocation,
which is not so insignificant for SPL in some cases.
If CONFIG_DM_DEVICE_REMOVE is disabled, we never remove devices,
so we do not have to manage resources in the first place.
In this case, devres_alloc() can fall back to the simpl
The vzalloc(size) is equivalent to kzalloc(size, 0). Move it to
include/linux/compat.h as an inline function in order to avoid the
function call overhead.
Signed-off-by: Masahiro Yamada
Reviewed-by: Heiko Schocher
Acked-by: Simon Glass
---
Changes in v2: None
include/linux/compat.h | 6
In U-Boot's driver model, memory is basically allocated and freed
in the core framework. So, low level drivers generally only have
to specify the size of needed memory with .priv_auto_alloc_size,
.platdata_auto_alloc_size, etc. Nevertheless, some drivers still
need to allocate memory on their own
With devm_kzalloc(), device_unbind() and the failure path in
device_bind() can be much cleaner.
We no longer need such flags as DM_FLAG_ALLOC_PDATA etc. because
we do not have to remember if the memory has been really allocated.
The memory is freed when the device is unbind.
Signed-off-by: Masah
These two declarations in arch/x86/include/asm/interrupt.h conflict
with ones in include/linux/compat.h, so x86 boards cannot include
.
The comment /* arch/x86/lib/interrupts.c */ is bogus now, and we do
not see any definitions of disable_irq() and enable_irq() in there.
Signed-off-by: Masahiro Y
A little more clean up made possible by devm_kzalloc().
Signed-off-by: Masahiro Yamada
---
Changes in v2: None
drivers/core/device.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/drivers/core/device.c b/drivers/core/device.c
index 65b8a14..bcae3ba 100644
--- a/
devm_kmalloc() is identical to kmalloc() except that the memory
allocated with it is managed and will be automatically released
when the device is removed/unbound.
Likewise for the other variants.
Signed-off-by: Masahiro Yamada
Acked-by: Simon Glass
---
Changes in v2:
- Rip off "extern" from
Currently, we only have DM_FLAG_ACTIVATED to indicate the device
status, but we still cannot know in which stage is in progress,
binding or probing.
This commit introduces a new flag, DM_FLAG_BOUND, which is set when
the device is really bound, and cleared when it is unbound.
Signed-off-by: Masah
For the record, describe exactly which device of which vendor
is used on this board.
I2C EEPROM is bound by the generic compatible string, "i2c-eeprom",
so this commit has no impact on the functionality.
Signed-off-by: Masahiro Yamada
---
arch/arm/dts/uniphier-ref-daughter.dtsi | 2 +-
1 file
On Friday, June 26, 2015 at 10:01:47 PM, Marek Vasut wrote:
> On Friday, June 26, 2015 at 06:43:13 PM, Marek Vasut wrote:
> > On Wednesday, June 03, 2015 at 05:52:47 AM,
> > dingu...@opensource.altera.com
> >
> > wrote:
> > > From: Dinh Nguyen
> > >
> > > Hi,
> > >
> > > This is v4 of the patch
> Support is also provided for the Haier Chromebook, which is based on the
> same SoC. In this case it boots from SPI rather than an SD card.
That's great work, but it looks like the matching between codenames and
actual devices names at
http://www.chromium.org/chromium-os/developer-information-fo
This code allows using DFU defined mediums for storing data received via
TFTP protocol.
It reuses legacy code at common/update.c.
To run update_tftp() during boot one needs to define
"update_tftp_exec_at_boot=true".
Signed-off-by: Lukasz Majewski
---
common/update.c | 37 ++
Up till now it was impossible to use code from update.c when system
was not equipped with raw FLASH memory.
Such behavior prevented DFU from reusing this code.
Signed-off-by: Lukasz Majewski
---
common/update.c | 15 +++
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git a/c
This change gives the ability to reuse the header file by other
subsystems (like e.g. dfu).
Without this change compilation error emerges for the legacy update.c file.
Signed-off-by: Lukasz Majewski
---
common/update.c | 2 +-
include/tftp.h | 30 ++
net/bootp.c
Documentation file for DFU extension. With this functionality it is now
possible to transfer FIT images with firmware updates via TFTP and use
DFU backend for storing them.
Signed-off-by: Lukasz Majewski
---
doc/README.dfutftp | 153 +
1 file c
This commit series enables DFU subsystem to use ETH and TFTP protocol as
a medium for downloading data, which should bring substantial speedup
for writing large files (like rootfs).
Please read provided ./doc/README.dfutftp documentation entry for more
information.
Lukasz Majewski (8):
doc: df
The new 'dfutftp' command has syntax similar to 'dfu' command.
This new command however, requires some extra env variables to allow
update_tftp() code to work properly. For more explanation, please consult
./doc/README.dfutftp
Signed-off-by: Lukasz Majewski
---
common/Makefile | 1 +
commo
This commit adds initial support for using tftp for downloading and
upgrading firmware on the device.
Signed-off-by: Lukasz Majewski
---
drivers/dfu/Makefile | 1 +
drivers/dfu/dfu_tftp.c | 76 ++
include/dfu.h | 11
3 files ch
Stephen Warren writes:
> On 06/30/2015 05:56 AM, Jonas Jensen wrote:
>> Hello,
>>
>> I have found the following issue with RPi 2:
>>
>> Only 1 CPU is brought up when the kernel is started from script (see [1]).
>>
>> All 4 CPUs are brought up if started "manually" typing in environment
>> vari
Signed-off-by: Lukasz Majewski
---
include/configs/am335x_evm.h | 10 ++
1 file changed, 10 insertions(+)
diff --git a/include/configs/am335x_evm.h b/include/configs/am335x_evm.h
index 035c156..09f6543 100644
--- a/include/configs/am335x_evm.h
+++ b/include/configs/am335x_evm.h
@@ -46,6
This function allows writing via DFU data stored from fixed buffer address
(like e.g. loadaddr env variable).
Such predefined buffers are used in the update_tftp() code. In fact this
function is a wrapper on the dfu_write() and dfu_flush().
Signed-off-by: Lukasz Majewski
---
drivers/dfu/dfu.c |
Fix LS102xa timer configuration to ensure timer compare value is set to
all-ones as a 64-bit number rather than a 32-bit number.
When the 32-bit all-ones was used, this could result in a timer compare value
of 2^32-1, which at 12.5 MHz will fire in ~344 seconds. If the operating
system's timer su
Hi Stephen,
On 10 July 2015 at 23:34, Stephen Warren wrote:
> On 07/07/2015 08:53 PM, Simon Glass wrote:
>> Raspberry Pi uses a DWC2 USB controller and a SMSC USB Ethernet adaptor.
>> Neither of these currently support driver model.
>>
>> This series does the following:
>> - Move Raspberry Pi to
Hi,
I am trying to do pretty much the same thing as described here:
http://lists.denx.de/pipermail/u-boot/2014-April/178252.html
Is the described procedure (copied below) only valid after applying the
patch ?
Thank you
regards,
--
David Cemin
+1 343-777-1735
_
On 07/07/2015 08:53 PM, Simon Glass wrote:
> Raspberry Pi uses a DWC2 USB controller and a SMSC USB Ethernet adaptor.
> Neither of these currently support driver model.
>
> This series does the following:
> - Move Raspberry Pi to use device tree control (u-boot-dtb.bin instead of
> u-boot.bin
On Sunday, July 12, 2015 at 01:53:05 PM, Peng Fan wrote:
> Hi Marek,
Hi!
> On Sun, Jul 12, 2015 at 01:39:58PM +0200, Marek Vasut wrote:
> >On Sunday, July 12, 2015 at 12:27:42 PM, Peng Fan wrote:
> >> Hi Marek,
> >>
> >> On Sun, Jul 12, 2015 at 12:10:29AM +0200, Marek Vasut wrote:
> >> >On Satur
On Sunday, July 12, 2015 at 01:55:58 PM, Peng Fan wrote:
> Hi Marek,
Hi!
> On Sun, Jul 12, 2015 at 01:50:55PM +0200, Marek Vasut wrote:
> >On Sunday, July 12, 2015 at 12:32:28 PM, Peng Fan wrote:
> >> Hi Marek,
> >>
> >> On Sun, Jul 12, 2015 at 12:11:42AM +0200, Marek Vasut wrote:
> >> >On Satur
Hi Marek,
On Sun, Jul 12, 2015 at 01:50:55PM +0200, Marek Vasut wrote:
>On Sunday, July 12, 2015 at 12:32:28 PM, Peng Fan wrote:
>> Hi Marek,
>>
>> On Sun, Jul 12, 2015 at 12:11:42AM +0200, Marek Vasut wrote:
>> >On Saturday, July 11, 2015 at 10:07:11 AM, Peng Fan wrote:
>> >> 1. Update imx regis
Hi Marek,
On Sun, Jul 12, 2015 at 01:39:58PM +0200, Marek Vasut wrote:
>On Sunday, July 12, 2015 at 12:27:42 PM, Peng Fan wrote:
>> Hi Marek,
>>
>> On Sun, Jul 12, 2015 at 12:10:29AM +0200, Marek Vasut wrote:
>> >On Saturday, July 11, 2015 at 10:07:10 AM, Peng Fan wrote:
>> >> Add i.MX6UL pins IO
From: Chris Smith
When the original HBUS divider value is retrieved in mxs_ocotp_scale_hclk()
for the purpose or restoring it back later, the value is not shifted by the
HBUS divider offset in that register. This is not a problem, since the shift
is zero on all MXS hardware. Add the shift anyway,
On Sunday, July 12, 2015 at 12:32:28 PM, Peng Fan wrote:
> Hi Marek,
>
> On Sun, Jul 12, 2015 at 12:11:42AM +0200, Marek Vasut wrote:
> >On Saturday, July 11, 2015 at 10:07:11 AM, Peng Fan wrote:
> >> 1. Update imx register base address for i.MX6UL.
> >> 2. Remove duplicated MXS_APBH/GPMI/BCH_BASE
On Sunday, July 12, 2015 at 12:27:42 PM, Peng Fan wrote:
> Hi Marek,
>
> On Sun, Jul 12, 2015 at 12:10:29AM +0200, Marek Vasut wrote:
> >On Saturday, July 11, 2015 at 10:07:10 AM, Peng Fan wrote:
> >> Add i.MX6UL pins IOMUX file which defines the IOMUX settings for choose.
> >>
> >> Signed-off-by
Hi Marek,
On Sun, Jul 12, 2015 at 12:11:42AM +0200, Marek Vasut wrote:
>On Saturday, July 11, 2015 at 10:07:11 AM, Peng Fan wrote:
>> 1. Update imx register base address for i.MX6UL.
>> 2. Remove duplicated MXS_APBH/GPMI/BCH_BASE.
>> 3. Remove #ifdef for register addresses that equal to
>>"AIP
Hi Marek,
On Sun, Jul 12, 2015 at 12:10:29AM +0200, Marek Vasut wrote:
>On Saturday, July 11, 2015 at 10:07:10 AM, Peng Fan wrote:
>> Add i.MX6UL pins IOMUX file which defines the IOMUX settings for choose.
>>
>> Signed-off-by: Peng Fan
>> Signed-off-by: Ye.Li
>> ---
>>
>> Changes v2:
>> none
On Friday 10 July 2015, 23:17:58 wrote Stephen Warren:
> On 07/04/2015 03:48 AM, Alexander Stein wrote:
> > This patchset enables dcache support for Raspberry Pi 1.
> > First the cache support code was made similar to existing arm1136 code.
> > The invalidate and flush functions were inprovoed to a
On Friday 10 July 2015, 23:24:58 wrote Stephen Warren:
> On 07/04/2015 03:48 AM, Alexander Stein wrote:
> > Now that mailbox driver supports cache flush and invalidation, we can
> > enable dcache.
>
> Did you also test that HDMI output doesn't show any issues after this
> change? I think there's a
On Friday 10 July 2015, 23:21:32 wrote Stephen Warren:
> On 07/04/2015 03:48 AM, Alexander Stein wrote:
> > The code is copied 1:1 from arm1136 which uses the same cp15 registers.
>
> Same comment here. Perhaps create a cache-armv6.c (or whatever name is
> appropriate; I'm not sure if ARMv6 mandat
On Friday 10 July 2015, 23:20:07 wrote Stephen Warren:
> On 07/04/2015 03:48 AM, Alexander Stein wrote:
> > This is effectively the same code but it also does a clean cache before
> > invalidating and doing a memory barrier.
>
> Is it possible to share this function with arm1136 rather than
> cut/
48 matches
Mail list logo
