On Sun, Nov 29, 2015 at 2:31 PM, Arnd Bergmann wrote:
> On Sunday 29 November 2015 14:18:24 Peter Crosthwaite wrote:
>>
>> I started a small project to test as many QEMU emulated ARM boards
>> using the multi_v7 defconfig:
>>
>> https://lists.gnu.org/archive/html
Hi,
I started a small project to test as many QEMU emulated ARM boards
using the multi_v7 defconfig:
https://lists.gnu.org/archive/html/qemu-devel/2015-10/msg00755.html
One thing that came up was we cannot use the virt board as it relies
on virtio hotplug and drivers to get block and network sup
Ping!
Anything I need to do or send to to get a merge on this?
Regards,
Peter
On Tue, Mar 3, 2015 at 12:49 AM, Peter Crosthwaite
wrote:
> ARM64 has the yield nop hint which has the intended semantics of
> cpu_relax. Implement.
>
> The immediate application is ARM CPU emulators. An
,
and sees a significant boot time performance increase with this change.
Signed-off-by: Peter Crosthwaite
Acked-by: Will Deacon
---
arch/arm64/include/asm/processor.h | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/arch/arm64/include/asm/processor.h
b/arch/arm64/include
On Wed, Feb 25, 2015 at 5:24 AM, Will Deacon wrote:
> On Tue, Feb 24, 2015 at 11:07:37PM +0000, Peter Crosthwaite wrote:
>> ARM64 has the yield nop hint which has the intended semantics of
>> cpu_relax. Implement.
>>
>> The immediate application is ARM CPU emul
All instances of "ttyPS" use this macro except for this one. Convert
it.
Signed-off-by: Peter Crosthwaite
Acked-by: Michal Simek
---
drivers/tty/serial/xilinx_uartps.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/tty/serial/xilinx_uartps.c
b/drivers/
,
and sees a significant boot time performance increase with this change.
Signed-off-by: Peter Crosthwaite
---
arch/arm64/include/asm/processor.h | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/arch/arm64/include/asm/processor.h
b/arch/arm64/include/asm/processor.h
index
On Sat, Nov 29, 2014 at 1:34 PM, Sören Brinkmann
wrote:
> Hi Peter,
>
> The patches look all good to me. But you may want to check your CC
> lists. I think at least the DT list should be included.
>
Resent
> For the whole series:
> Acked-by: Soren Brinkmann
>
Thanks,
Regards,
Peter
>
Add a DTS describing the Digilent ZYBO board. Similar to ZED but with
a 50MHz crystal instead of 33MHz.
Acked-by: Soren Brinkmann
Signed-off-by: Peter Crosthwaite
---
Changed since v1:
Change compat vendor prefix from xlnx to digilent (Soren review)
Alphabetise nodes
---
arch/arm/boot/dts
. the Digilent ZYBO).
Acked-by: Soren Brinkmann
Signed-off-by: Peter Crosthwaite
---
Changed since v1:
Alphabetize node ordering (Soren review)
Im guessing long term this should be converted to a fixed clock. But
I think this at least steps in that direction.
---
arch/arm/boot/dts/zynq-7000
Digilent is a board designer, making various Linux capabable FPGA and
processor boards. Add to the vendor list.
Acked-by: Soren Brinkmann
Signed-off-by: Peter Crosthwaite
---
http://www.digilentinc.com
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion
ia EEPROM contents or should the dts just
describe the EEPROM?
Regards,
Peter
> Regards,
> Steve
>
> -Peter Crosthwaite wrote: -
> To: Sören Brinkmann , Steve Wang
>
> From: Peter Crosthwaite
> Date: 11/10/2014 02:56PM
> Cc: linux-kernel@vger.kernel.org, mich...
Add a DTS describing the Digilent ZYBO board. Similar to ZED but with
a 50MHz crystal instead of 33MHz.
Signed-off-by: Peter Crosthwaite
---
Changed since v1:
Change compat vendor prefix from xlnx to digilent (Soren review)
Alphabetise nodes
---
arch/arm/boot/dts/Makefile | 3 ++-
arch
Digilent is a board designer, making various Linux capabable FPGA and
processor boards. Add to the vendor list.
Signed-off-by: Peter Crosthwaite
---
http://www.digilentinc.com
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a
. the Digilent ZYBO).
Signed-off-by: Peter Crosthwaite
---
Changed since v1:
Alphabetize node ordering (Soren review)
Im guessing long term this should be converted to a fixed clock. But
I think this at least steps in that direction.
---
arch/arm/boot/dts/zynq-7000.dtsi | 1 -
arch/arm
On Mon, Nov 17, 2014 at 5:32 AM, Sören Brinkmann
wrote:
> On Sun, 2014-11-16 at 11:51AM +0100, Andreas Färber wrote:
>> Hi Michal,
>>
>> Am 14.11.2014 um 11:52 schrieb Michal Simek:
>> > diff --git a/arch/arm/boot/dts/zynq-7000.dtsi
>> > b/arch/arm/boot/dts/zynq-7000.dtsi
>> > index ce2ef5bec4f2.
On Tue, Nov 11, 2014 at 8:42 AM, Sören Brinkmann
wrote:
> On Tue, 2014-11-11 at 08:39AM +1000, Peter Crosthwaite wrote:
>> On Mon, Nov 10, 2014 at 7:47 AM, Sören Brinkmann
>> wrote:
>> > Hi Peter,
>> >
>> > On Sun, 2014-11-09 at 01:38PM +1000, Peter Cro
On Mon, Nov 10, 2014 at 7:47 AM, Sören Brinkmann
wrote:
> Hi Peter,
>
> On Sun, 2014-11-09 at 01:38PM +1000, Peter Crosthwaite wrote:
>> Add a DTS describing the Digilent ZYBO board. Similar to ZED but with
>
> "Digilent ZYBO" here...
>
> [...]
>> +
On Mon, Nov 10, 2014 at 7:34 AM, Sören Brinkmann
wrote:
> On Sun, 2014-11-09 at 01:38PM +1000, Peter Crosthwaite wrote:
>> The fact that all supported boards use the same 33MHz crystal is a
>> co-incidence. The Zynq PS support a range of crystal freqs so the
>> hardcoded sett
. the Digilent ZYBO).
Signed-off-by: Peter Crosthwaite
---
Im guessing long term this should be converted to a fixed clock. But
I think this at least steps in that direction.
---
arch/arm/boot/dts/zynq-7000.dtsi | 1 -
arch/arm/boot/dts/zynq-parallella.dts | 4
arch/arm/boot/dts/zynq
Add a DTS describing the Digilent ZYBO board. Similar to ZED but with
a 50MHz crystal instead of 33MHz.
Signed-off-by: Peter Crosthwaite
---
arch/arm/boot/dts/Makefile | 3 ++-
arch/arm/boot/dts/zynq-zybo.dts | 52 +
2 files changed, 54 insertions
On Sat, Apr 5, 2014 at 4:05 PM, Harini Katakam
wrote:
> Hi Peter,
>
> On Sat, Apr 5, 2014 at 4:44 AM, Peter Crosthwaite
> wrote:
>> On Sat, Apr 5, 2014 at 12:30 AM, Harini Katakam
>> wrote:
>>> Hi,
>>>
>>> On Fri, Apr 4, 2014 at 7:38 PM, Harini
On Sat, Apr 5, 2014 at 12:30 AM, Harini Katakam
wrote:
> Hi,
>
> On Fri, Apr 4, 2014 at 7:38 PM, Harini Katakam
> wrote:
>> Hi Mark,
>>
>> On Fri, Apr 4, 2014 at 6:16 PM, Mark Brown wrote:
>>> On Fri, Apr 04, 2014 at 05:44:23PM +0530, Harini Katakam wrote:
On Fri, Apr 4, 2014 at 3:39 PM, Ma
On Thu, Apr 3, 2014 at 9:10 PM, Harini Katakam wrote:
> Add driver for Cadence SPI controller. This is used in Xilinx Zynq.
>
> Signed-off-by: Harini Katakam
> ---
>
> v2 changes:
> - Use xilinx compatible string too.
> - Changes read register and write register functions to static inline.
> - Re
On Fri, Apr 4, 2014 at 10:14 PM, Harini Katakam
wrote:
> Hi Mark,
>
> On Fri, Apr 4, 2014 at 3:39 PM, Mark Brown wrote:
>> On Fri, Apr 04, 2014 at 08:30:38AM +0530, Harini Katakam wrote:
>>> On Fri, Apr 4, 2014 at 3:04 AM, Mark Brown wrote:
>>> > On Thu, Apr 03, 2014 at 04:40:31PM +0530, Harini
On Thu, Dec 19, 2013 at 8:47 PM, Jonas Jensen wrote:
> Add a generic (dtsi) include file for MOXA ART SoCs.
>
> Also add a file for UC-7112-LX.
>
> Signed-off-by: Jonas Jensen
Reviewed-by: Peter Crosthwaite
P.S. you could have added this already, small changes don't r
= "MOXART";
> + interrupt-parent = <&intc>;
> +
> + cpus {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + cpu@0 {
> + device_type = "cpu";
&g
;&dma 5>,
> + <&dma 5>;
> + dma-names = "tx", "rx";
> + status = "disabled";
> + };
> +
> + mdio0: mdio@90900090 {
> + compatible =
On Tue, Dec 17, 2013 at 6:05 AM, Jonas Jensen wrote:
> On 15 December 2013 05:27, Peter Crosthwaite
> wrote:
>>> + sdhci: sdhci@98e0 {
>>> + compatible = "moxa,moxart-sdhci";
>>> + reg = <0x98e
On Sat, Dec 14, 2013 at 12:33 AM, Jonas Jensen wrote:
> Add a generic (dtsi) include file for MOXA ART SoCs.
>
> Also add a file for UC-7112-LX.
>
> Signed-off-by: Jonas Jensen
> ---
> Documentation/devicetree/bindings/arm/moxart.txt | 12 +++
> arch/arm/boot/dts/Makefile
Ping!
On Thu, Nov 28, 2013 at 5:26 PM, Peter Crosthwaite
wrote:
> When searching the interrupt map, if a matched parent is disabled, just
> ignore it and move on with the search.
>
> This allows for specifying connection of a single device IRQ to
> multiple interrupt cont
On Thu, Nov 28, 2013 at 12:17 AM, Grant Likely wrote:
> On Wed, 27 Nov 2013 19:06:35 +1000, Peter Crosthwaite
> wrote:
>> On Mon, Nov 25, 2013 at 7:32 AM, Grant Likely
>> wrote:
>> > On Sun, 24 Nov 2013 17:04:52 +1000, Peter Crosthwaite
>> > wrote:
&
controller via the already
existing status = "disabled" mechanism.
Signed-off-by: Peter Crosthwaite
Acked-by: Michal Simek
---
drivers/of/irq.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/of/irq.c b/drivers/of/irq.c
index 786b0b4..22e414b 100644
--- a/drivers/of/i
When searching the system for interrupt controllers, skip over any
that are explicitly disabled.
This makes interrupt controllers consistent with regular devices,
which can be marked as do-not-probe via the status = "disabled" dts
property.
Signed-off-by: Peter Crosthwaite
Acked-
Hi All,
These two patches support the case where an interrupt controller is
marked as disabled. Patch 1 fixed the dts interrupt-map search logic to
ignore disabled interrupt controllers. Patch 2 stops disabled interrupt
controllers getting probed.
Peter Crosthwaite (2):
of: irq: Ignore
On Mon, Nov 25, 2013 at 7:32 AM, Grant Likely wrote:
> On Sun, 24 Nov 2013 17:04:52 +1000, Peter Crosthwaite
> wrote:
>> On Wed, Nov 13, 2013 at 4:14 PM, Grant Likely
>> wrote:
>> > On Wed, 13 Nov 2013 09:17:01 +1000, Peter Crosthwaite
>> > wrote:
>
On Wed, Nov 13, 2013 at 4:14 PM, Grant Likely wrote:
> On Wed, 13 Nov 2013 09:17:01 +1000, Peter Crosthwaite
> wrote:
>> On Tue, Nov 12, 2013 at 6:50 PM, Grant Likely
>> wrote:
>> > On Tue, 12 Nov 2013 17:49:37 +1000, Peter Crosthwaite
>> > wrote:
>&g
On Tue, Nov 12, 2013 at 6:50 PM, Grant Likely wrote:
> On Tue, 12 Nov 2013 17:49:37 +1000, Peter Crosthwaite
> wrote:
>> Hi Grant,
>>
>> On Tue, Nov 12, 2013 at 4:54 PM, Grant Likely
>> wrote:
>> > On Tue, 12 Nov 2013 08:58:15 +1000, Peter C
Hi Grant,
On Tue, Nov 12, 2013 at 4:54 PM, Grant Likely wrote:
> On Tue, 12 Nov 2013 08:58:15 +1000, Peter Crosthwaite
> wrote:
>> Hi Grant,
>>
>> On Wed, Oct 16, 2013 at 6:39 AM, Grant Likely
>> wrote:
>> > The standard interrupts property in devi
Hi Grant,
On Wed, Oct 16, 2013 at 6:39 AM, Grant Likely wrote:
> The standard interrupts property in device tree can only handle
> interrupts coming from a single interrupt parent. If a device is wired
> to multiple interrupt controllers, then it needs to be attached to a
> node with an interrupt
Hi All,
For micron M25P80 parts there is a mix of naming conventions in the
device table:
/* Micron */
{ "n25q064", INFO(0x20ba17, 0, 64 * 1024, 128, 0) },
{ "n25q128a11", INFO(0x20bb18, 0, 64 * 1024, 256, 0) },
{ "n25q128a13", INFO(0x20ba18, 0, 64 * 1024, 256,
r27=, r28=
> [ 96.660622] r29=, r30=, r31=C24A97E0, rPC=C011E1A0
> [ 96.666849] msr=42A2, ear=004C, esr=0872, fsr=362E3639
>
> Signed-off-by: Stephan Linz
Tested-by: Peter Crosthwaite
> ---
> v2 Remove additional printk mess
t; [1.014924] uartlite 8fff.debug: failed to get alias id, errno -19
> [1.022543] uartlite 8fff.debug: failed to get port-number
>
> Signed-off-by: Stephan Linz
Reviewed-by: Peter Crosthwaite
Tested-by: Peter Crosthwaite
> ---
> drivers/tty/serial/uartlite.c |5 ++
43 matches
Mail list logo
