Marek Vasut writes:
>> Isn't there the case of a single NAND controller with 2 identical chips,
>> each a 8 bit NAND chip, and the controller aggregating them to offer the
>> OS a single 16-bit NAND chip ?
>
> Is that using 1 or 2 physical chipselect lines on the CPU (controller) ?
I think it's 2
Charles Keepax writes:
> Yeah that solution looks a lot more like what I was expecting.
Okay, so I'm ready to fire the v4. I'll wait a couple of days for others reviews
and if none I'll send the v4.
Cheers.
--
Robert
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Boris Brezillon writes:
> On Thu, 29 Oct 2015 18:23:47 +0100
> Marek Vasut wrote:
> Except it's now how devices supporting 16 bits data bus are supposed to
> work, which means your NAND controller will probably not be able to
> send the command/address value on the higher 8 bits...
Correct.
>>
Ulf Hansson writes:
> On 6 June 2015 at 23:15, Robert Jarzmik wrote:
>> From: Daniel Mack
>>
>> Switch over pxamci to dmaengine. This prepares the devicetree full
>> support of pxamci.
>>
>> This was successfully tested on a PXA3xx board, as well as P
Ezequiel Garcia writes:
> Here you go:
>
> http://git.infradead.org/users/ezequielg/linux/shortlog/refs/heads/pxa3xx-nand-timing-rework-v2
Okay, I've tested this on cm-x300. The result is not bright :
nand: device found, Manufacturer ID: 0xec, Chip ID: 0xdc
nand: Samsung NAND 512
Vaibhav Hiremath writes:
> On Monday 20 July 2015 12:39 PM, Vaibhav Hiremath wrote:
>>
>>
>> On Monday 20 July 2015 12:36 PM, Vaibhav Hiremath wrote:
>>>
>>>
>>> On Saturday 18 July 2015 01:19 AM, Robert Jarzmik wrote:
>>>> Vaibhav Hi
Dmitry Torokhov writes:
> Hi,
>
> This series tries to move the driver away from legacy platform data towards
> using platform-independent way of retrieving both configuration parameters and
> GPIOs (device_property_read_* and gpiod APIs).
>
> This is based on top of 2 Timo's patches converting t
for pxa25x.
Cheers.
--
Robert
---8<---
>From 8e0da8ff579bd38a7923f15a905133814153ebdb Mon Sep 17 00:00:00 2001
From: Robert Jarzmik
Date: Sun, 1 Nov 2015 20:07:31 +0100
Subject: [PATCH] ARM: pxa: use pinctrl
Select pinctrl for all PXA architectures.
Signed-off-by: Robert Jarzmik
---
Masahiro Yamada writes:
> Building pinctrl-pxa27x.c as a module causes a link error:
>
> ERROR: "pxa2xx_pinctrl_init" [drivers/pinctrl/pxa/pinctrl-pxa27x.ko]
> undefined!
>
> Signed-off-by: Masahiro Yamada
Yeah, I see no other way out to spare namespace polutio
Masahiro Yamada writes:
> 2016-01-24 2:56 GMT+09:00 kbuild test robot :
>> Hi Masahiro,
>>
>> [auto build test ERROR on next-20160122]
>> [cannot apply to v4.4-rc8 v4.4-rc7 v4.4-rc6 v4.4]
>> [if your patch is applied to the wrong git tree, please drop us a note to
>> help improving the system]
>
Roman Volkov writes:
> В Thu, 31 Dec 2015 23:33:45 +0100 (CET)
> Thomas Gleixner пишет:
>
>> Roman,
>>
>> On Thu, 31 Dec 2015, Roman Volkov wrote:
>> > Since vt8500 and PXA timers are identical, use MIN_OSCR_DELTA from
>> > PXA, which is bigger than existing value. It is required to
>> > determ
Arnd Bergmann writes:
> Sorry for the late reply. I think this is great and I'd like to just apply it.
> Can you re-send to a...@kernel.org if you're happy with that?
Yep.
> Looking at your description above, I see that you included pxa168_defconfig
> and pxa910_defconfig as well, but they are m
*c files, look for all
platform devices added, and verify they are all in pxa_defconfig
- do the same to ensure all pxa specific drivers (leds, gpio, ...) are
included
Signed-off-by: Robert Jarzmik
---
arch/arm/configs/pxa_defconfig | 783 +
1 file c
ngine: pxa: add pxa dmaengine driver")
Reported-by: Vasily Khoruzhick
Tested-by: Vasily Khoruzhick
Signed-off-by: Robert Jarzmik
---
drivers/dma/pxa_dma.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/dma/pxa_dma.c b/drivers/dma/pxa_dma.c
index f2a0310ae771..ca6c088ed
,
because of an trivial operator issue.
This was tested on a pxa27x platform.
Fixes: a57e16cf0333 ("dmaengine: pxa: add pxa dmaengine driver")
Reported-by: Vasily Khoruzhick
Tested-by: Vasily Khoruzhick
Signed-off-by: Robert Jarzmik
---
Since v1: add the mask fix suggested by Vasily
---
d
Ulf Hansson writes:
> On 6 February 2016 at 22:14, Robert Jarzmik wrote:
>> When the gpio driver is probed after the mmc one, the read/write gpio
>> and card detection one return -EPROBE_DEFER. Unfortunately, the memory
>> region remains requested, and upon the next probe
.
More broadly, this patch uses devm_*() primitives whenever possible in
the probe function.
Signed-off-by: Robert Jarzmik
---
Since v1: broaden the devm_*() enveloppe
Since v2: further broaden devm_*(): regulator + clock
---
drivers/mmc/host/pxamci.c | 35 +--
1 file
or 32, and in these
only the camera has a driver using dma.
Fixes: e87ffbdf0697 ("dmaengine: pxa_dma: fix the no-requestor case")
Signed-off-by: Robert Jarzmik
---
drivers/dma/pxa_dma.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/drivers/dma/pxa_dma.
Guennadi Liakhovetski writes:
> Hi Robert,
>
> On Tue, 27 Oct 2015, Robert Jarzmik wrote:
>
>> Guennadi Liakhovetski writes:
>>
>> > Hi Robert,
>> >
>> > Didn't you tell me, that your dmaengine patch got rejected and therefore
>>
Vinod Koul writes:
> On Mon, Feb 08, 2016 at 03:18:51PM +0100, Robert Jarzmik wrote:
>> The current number of requestor lines is limited to 31. This was an
>> error of a previous commit, as this number is platform dependent, and is
>> actually :
>> - for pxa25x: 4
Vinod Koul writes:
> On Tue, Feb 09, 2016 at 08:20:05AM +0100, Robert Jarzmik wrote:
>> Vinod Koul writes:
>>
>> > On Mon, Feb 08, 2016 at 03:18:51PM +0100, Robert Jarzmik wrote:
>> >> The current number of requestor lines is limited to 31. This was an
>&
Mark Brown writes:
> On Fri, Feb 26, 2016 at 02:33:49AM +0100, Robert Jarzmik wrote:
>> Mark Brown writes:
>
>> > It will not be called, the generic AC'97 code will be used.
>
>> Ok, if it's not called no code in sound/soc/codecs/wm9713.c will
Robert Jarzmik writes:
> Vinod Koul writes:
>
>> On Mon, Feb 15, 2016 at 09:57:48PM +0100, Robert Jarzmik wrote:
>>> The current number of requestor lines is limited to 31. This was an
>>> error of a previous commit, as this number is platform dependent, and is
&g
Robert Jarzmik writes:
> While testing audio with pxa2xx-ac97, underrun were happening while the
> user application was correctly feeding the music. Debug proved that the
> cyclic transfer is not cyclic, ie. the last descriptor did not loop on
> the first.
>
> Another
Laxman Dewangan writes:
> Use devm_pinctrl_register() for pin control registration and clean
> the error path.
>
> Signed-off-by: Laxman Dewangan
> Cc: Daniel Mack
> Cc: Haojian Zhuang
> Cc: Robert Jarzmik
> Cc: linux-arm-ker...@lists.infradead.org
Acked-by:
Robert Jarzmik writes:
> Since the switch from mmp_pdma to pxa_dma driver for pxa architectures,
> the pxa_dma requires 2 arguments, namely the requestor line and the
> requested priority.
>
> Fix the only left device node which was still passing only one argument,
> maki
Rob Herring writes:
>> +Example:
>> +ac97: sound@4050 {
>> +compatible = "marvell,pxa2xx-ac97";
>> +reg = < 0x4050 0x1000 >;
>> +interrupts = <14>;
>> +reset-gpio = <&gpio 113 GPIO_ACTIVE_HIGH>;
>> +#sound-dai-cells = <1>;
>>
Ezequiel Garcia writes:
> On 12 February 2016 at 19:29, Robert Jarzmik wrote:
>> When the driver is initialized in a pure device-tree platform, the
>> driver's probe fails allocating the dma channel :
>> [ 525.624435] pxa3xx-nand 4310.nand: no resource defined for
ith Mark Brown about AC97 rework, that's the reason I'm
holding it for now. It's here mainly to show application of 1/2.
Any rework ideas would be appreciated.
Cheers.
--
Robert
Robert Jarzmik (2):
ARM: dts: pxa3xx: add pincontrol helpers
ARM: dts: pxa: add zylonite devicetree bo
The various pxa3xx variants have a really weird pin scheme assignement,
when you want the pin number relative to a known gpio pin.
This change adds the various tools to ease up writing the pinmux and
pinconf devicetree parts.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa3xx.dtsi | 90
Add the description of the Zylonite board. This should be the equivalent
of arch/arm/mach-pxa/zylonite.c and part of
arch/arm/mach-pxa/zylonite_pxa300.c
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/zylonite310.dts | 682 ++
1 file changed, 682
Vinod Koul writes:
> On Thu, Feb 11, 2016 at 10:23:18PM +0100, Robert Jarzmik wrote:
>> @@ -1399,13 +1405,17 @@ static int pxad_probe(struct platform_device *op)
>> return PTR_ERR(pdev->base);
>>
>> of_id = of_match_device(pxad_dt_ids, &op-&g
Vinod Koul writes:
> On Mon, Feb 15, 2016 at 06:24:57PM +0100, Robert Jarzmik wrote:
>> Vinod Koul writes:
>>
>> > On Thu, Feb 11, 2016 at 10:23:18PM +0100, Robert Jarzmik wrote:
>> >> @@ -1399,13 +1405,17 @@ static int pxad_probe(struct platform_device *op)
For pxa based platforms, the number of requestor lines should be
specified, so that the driver can check if the flow control should be
activated (when a requestor line is asked for) or not.
Signed-off-by: Robert Jarzmik
---
Since v1: rename of property to #dma-requests
modify default
The DMA chip has a fixed number of requestor lines used for flow
control. This number is platform dependent. The pxa_dma dma driver will
use this value to activate or not the flow control.
There won't be any impact on mmp_pdma driver.
Signed-off-by: Robert Jarzmik
---
include/
For pxa based platforms, the number of requestor lines should be
specified, so that the driver can check if the flow control should be
activated (when a requestor line is asked for) or not.
Signed-off-by: Robert Jarzmik
---
Since v1: rename of property to #dma-requests
modify default
Declare the number of DMA requestor lines per platform :
- for pxa25x: 40 requestor lines
- for pxa27x: 75 requestor lines
- for pxa3xx: 100 requestor lines
This information will be used to activate the DMA flow control or not.
Signed-off-by: Robert Jarzmik
---
Since v1: rename of property
faulty constant as on pxa[23]xx
platforms, only camera, MSL and USB are above requestor 32, and in these
only the camera has a driver using dma.
Fixes: e87ffbdf0697 ("dmaengine: pxa_dma: fix the no-requestor case")
Signed-off-by: Robert Jarzmik
---
Since v1: change to #dma-requests the o
Vinod Koul writes:
> On Mon, Feb 15, 2016 at 09:57:48PM +0100, Robert Jarzmik wrote:
>> The current number of requestor lines is limited to 31. This was an
>> error of a previous commit, as this number is platform dependent, and is
>> actually :
>> - for pxa25x: 4
Robert Jarzmik writes:
> The DMA chip has a fixed number of requestor lines used for flow
> control. This number is platform dependent. The pxa_dma dma driver will
> use this value to activate or not the flow control.
>
> There won't be any impact on mmp_pdma driver.
Haojia
Sergei Ianovich writes:
> Hi Robert,
>
> On Mon, 2016-02-22 at 16:35 +0100, Robert Jarzmik wrote:
>> You're right, I haven't seen the pxa2xx.dtsi statement before.
>>
>> As such, could you amend a bit your patch please to :
>> - add:
>> Fixe
Dan Williams writes:
> On Tue, Feb 23, 2016 at 4:26 AM, Ard Biesheuvel
> wrote:
>> On 23 February 2016 at 13:03, Ard Biesheuvel
>> wrote:
>>> On 23 February 2016 at 12:58, Russell King - ARM Linux
>>> wrote:
On Mon, Feb 22, 2016 at 09:35:24PM +0100, Ard Biesheuvel wrote:
>> OK, I see wha
Mark Brown writes:
>> > It will eumerate the AC'97 bus by itself and does not need the CODEC to
>> > be described.
>
>> I think I still don't get it.
>
>> So let's rephrase it another way : how will the function wm9713_probe() be
>> called, ie. what is the possible function backtrace leading to t
Pavel Machek writes:
> Thanks for the info.
>
> I added
>
> "
> +Mainline has support for Mitac Mio A701, but that having only 64MiB
> +RAM, QTopia is the software to use there.
> "
Thanks Pavel, that looks good.
Cheers.
--
Robert
--
To unsubscribe from this list: send the line "unsubscribe
pxa_gpio_probe() was called before, so that lubbock
handler becomes the true IRQ chained handler of GPIO0, demuxing the
lubbock IO board interrupts.
Signed-off-by: Robert Jarzmik
---
For Thomas: as a side note, I'm not very happy with this patch. What
makes me unhappy is that I don&#
Thomas Gleixner writes:
> So what is the relationship between installing that chained handler
> and that gpio-pxa probe stuff?
The relation is in gpio-pxa probe, look at the extract of pxa_gpio_probe() :
pxa_gpio_probe()
irq = gpio_to_irq(0);
irq_set_chip_and_handl
Remove the useless CPU_PXA27x non existing kconfig option.
The true options is PXA27x, which is already selected.
Reported-by: Paul Bolle
Signed-off-by: Robert Jarzmik
---
arch/arm/mach-pxa/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/mach-pxa/Kconfig b/arch/arm/mach-pxa
Dmitry Eremin-Solenikov writes:
> 2014-11-09 0:01 GMT+03:00 Robert Jarzmik :
>clock enable_cnt prepare_cntrate
> accuracy phase
>
remaining steps are
:
- pxa3xx
- once PXA is fully converted to device tree, if that happens,
clk-pxa2* and clk-pxa3* should only hold the core clocks which cannot
be described in devicetree.
Signed-off-by: Robert Jarzmik
Tested-by: Dmitry Eremin-Solenikov
---
Since v1: fix clocks after Dmitry
Paul Bolle writes:
> Robert,
>
> Your commit 03ec7fe70c5c ("arm: pxa: add pxa27x device-tree support") is
> included in today's linux-next (ie, next-20141121). It adds a select
> statement for CPU_PXA27x. But there's no Kconfig symbol CPU_PXA27x.
Ah yes, you're perfectly right, CPU_PXA27x was not
As IRQ0, the legacy timer interrupt should not be used as an interrupt
number, shift the interrupts by a fixed number.
As we had in a special case a shift of 16 when ISA bus was used on a
PXA, use that value as the first interrupt number, regardless of ISA or
not.
Signed-off-by: Robert Jarzmik
Nicolas Pitre writes:
> Let ktime_divns() use do_div() inline whenever the divisor is constant
> and small enough. This will make things like ktime_to_us() and
> ktime_to_ms() much faster.
Hi Nicolas,
I suppose the "small enough" is linked to the "!(div >> 32)" in your patch. Can
I have the
Haojian Zhuang writes:
>
> I think that it's a kind of irq muxing, just like lots of PMIC (power
> management IC).
> We should move the lubbock board irqs to a mfd driver, and register them as
> threaded irqs.
I will have a look.
I didn't consider mfd for motherboard gates, I'll think of it, tha
Pavel Machek writes:
> On Thu 2014-11-13 20:18:04, Aaro Koskinen wrote:
>> Hi,
>>
>> On Thu, Nov 13, 2014 at 09:45:36AM -0800, Tony Lindgren wrote:
>> > * Pavel Machek [141113 08:23]:
>> > > OTOH ofono seems pretty reasonable. So I played a bit, and result
>> > > is python/pygtk gui which can r
Jiang Liu writes:
> diff --git a/arch/arm/mach-pxa/pcm990-baseboard.c
> b/arch/arm/mach-pxa/pcm990-baseboard.c
> index 2897da2a5df6..0d8331f8536e 100644
> --- a/arch/arm/mach-pxa/pcm990-baseboard.c
> +++ b/arch/arm/mach-pxa/pcm990-baseboard.c
> @@ -287,6 +287,7 @@ static struct irq_chip pcm990_i
Robert Jarzmik writes:
> Robert Jarzmik writes:
>
>> Robert Jarzmik writes:
>>
>> Hi Vinod,
>>
>> ... removed most of the people as this is a non-technical mail ...
>>
>> I hope to land this in the upcoming merge window. We're at -rc3, so
Vinod Koul writes:
>> +#define DCSR_RUNBIT(31) /* Run Bit (read / write) */
>> +#define DCSR_NODESC BIT(30) /* No-Descriptor Fetch (read / write) */
>> +#define DCSR_STOPIRQEN BIT(29) /* Stop Interrupt Enable (read / write)
>> */
>> +#define DCSR_REQPENDBIT(8) /* Request Pendin
Vinod Koul writes:
>> > Also, we should still mention that it's !slave API only.
>> Certainly not, it's fully slave API, that's the purpose of this patch.
> Its is not dependent on slave, it cna be used by slave as well as other
> users
You're right Vinod. I will rephrase that : this applies for
Add the pxa dma driver as maintained by the pxa architecture
maintainers, as it is part of the core IP.
Signed-off-by: Robert Jarzmik
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 9a76a40..35062a7 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
Document the new design of the pxa dma driver.
Signed-off-by: Robert Jarzmik
---
Since v2: Vinod's review
---
Documentation/dmaengine/pxa_dma.txt | 153
1 file changed, 153 insertions(+)
create mode 100644 Documentation/dmaengine/pxa_dma.txt
diff --
tries" (d294948c2ce4e1c85f452154469752cc9b8e876d).
Signed-off-by: Robert Jarzmik
---
Since v2: bissectability
Since v3: PXA_DCSR_ prefix
---
drivers/dma/pxa_dma.c | 244 ++
1 file changed, 244 insertions(+)
diff --git a/drivers/dma/pxa_dma.c b/drivers/dma/pxa_d
a3xx) and mioa701 (pxa27x),
with dmatest, pxa_camera and pxamci.
Signed-off-by: Robert Jarzmik
---
Since v1: 1) fixed muxed interrupt requesting
Since v2: Vinod's review
- dev_* instead of chan_*
- pxad_config() dma direction change
- residue calculation simplifi
ned-off-by: Robert Jarzmik
---
drivers/dma/pxa_dma.c | 28
1 file changed, 28 insertions(+)
diff --git a/drivers/dma/pxa_dma.c b/drivers/dma/pxa_dma.c
index 7da79d0..ddcbbf5 100644
--- a/drivers/dma/pxa_dma.c
+++ b/drivers/dma/pxa_dma.c
@@ -410,6 +410,15 @@ static i
Vinod Koul writes:
> On Mon, May 25, 2015 at 11:29:18PM +0200, Robert Jarzmik wrote:
>> Document the new design of the pxa dma driver.
>>
> Applied all, Thanks
Thanks so much Vinod. This really helps me moving forward.
Cheers.
--
Robert
--
To unsubscribe from this l
Add documentation about acking the transfers, and their
reusability.
Signed-off-by: Robert Jarzmik
Cc: Maxime Ripard
---
Documentation/dmaengine/provider.txt | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/Documentation/dmaengine/provider.txt
b/Documentation
was fixed according to
Maxime's first 2 comments.
Cheers.
--
Robert
[1] https://lkml.org/lkml/2015/3/21/230
Robert Jarzmik (2):
dmaengine: virt-dma: don't always free descriptor upon completion
Documentation: dmaengine: document DMA_CTRL_ACK
Documentation/dmaengi
set in the
transfer.
Signed-off-by: Robert Jarzmik
Cc: Lars-Peter Clausen
Cc: Maxime Ripard
---
drivers/dma/virt-dma.c | 19 +--
drivers/dma/virt-dma.h | 13 -
2 files changed, 25 insertions(+), 7 deletions(-)
diff --git a/drivers/dma/virt-dma.c b/drivers/dma/virt
Document the new design of the pxa dma driver.
Signed-off-by: Robert Jarzmik
---
Since v2: Vinod's review
---
Documentation/dmaengine/pxa_dma.txt | 153
1 file changed, 153 insertions(+)
create mode 100644 Documentation/dmaengine/pxa_dma.txt
diff --
Add the pxa dma driver as maintained by the pxa architecture
maintainers, as it is part of the core IP.
Signed-off-by: Robert Jarzmik
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 9a76a40..35062a7 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
Add documentation about acking the transfers, and their
reusability.
Signed-off-by: Robert Jarzmik
---
Documentation/dmaengine/provider.txt | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/Documentation/dmaengine/provider.txt
b/Documentation/dmaengine
ned-off-by: Robert Jarzmik
---
drivers/dma/pxa_dma.c | 28
1 file changed, 28 insertions(+)
diff --git a/drivers/dma/pxa_dma.c b/drivers/dma/pxa_dma.c
index f0912a2..08abb51 100644
--- a/drivers/dma/pxa_dma.c
+++ b/drivers/dma/pxa_dma.c
@@ -408,6 +408,15 @@ static i
tries" (d294948c2ce4e1c85f452154469752cc9b8e876d).
Signed-off-by: Robert Jarzmik
---
Since v2: bissectability
---
drivers/dma/pxa_dma.c | 242 ++
1 file changed, 242 insertions(+)
diff --git a/drivers/dma/pxa_dma.c b/drivers/dma/pxa_dma.c
index bad1b36..f0912a2 10
a3xx) and mioa701 (pxa27x),
with dmatest, pxa_camera and pxamci.
Signed-off-by: Robert Jarzmik
---
Since v1: 1) fixed muxed interrupt requesting
Since v2: Vinod's review
- dev_* instead of chan_*
- pxad_config() dma direction change
- residue calculation simplifi
Maxime Ripard writes:
> Hi Robert,
>
>>* DMA_CTRL_ACK
>> -- Undocumented feature
>> -- No one really has an idea of what it's about, besides being
>> - related to reusing the DMA transaction descriptors or having
>> - additional transactions added to it in the async-tx API
>
Robert Jarzmik writes:
Hi Vinod,
... removed most of the people as this is a non-technical mail ...
I hope to land this in the upcoming merge window. We're at -rc3, so time is
short. Apart from patch 6/6 where I still have Maxime's review to apply, are you
satisfied with the v3 of
Vinod Koul writes:
Hi Vinod,
First thanks for the review.
>> This is a new driver for pxa SoCs, which is also compatible with the former
>> mmp_pdma.
> The rationale is fine, is there a plan to remove old mmp_pdma then?
I have this in mind, yes. I will need a test from the MMP people to assess
Vinod Koul writes:
> On Sat, Apr 11, 2015 at 09:40:32PM +0200, Robert Jarzmik wrote:
>> Document the new design of the pxa dma driver.
>> + a) Transfers hot queuing
>> + A driver submitting a transfer and issuing it should be granted the
>> transfer
>> +
Robert Jarzmik writes:
> Robert Jarzmik writes:
>
> Hi Vinod,
>
> ... removed most of the people as this is a non-technical mail ...
>
> I hope to land this in the upcoming merge window. We're at -rc3, so time is
> short. Apart from patch 6/6 where I still have
Vinod Koul writes:
> On Fri, May 08, 2015 at 02:52:46PM +0200, Robert Jarzmik wrote:
>> Vinod Koul writes:
>>
>> Euh no, I meant that a transfer which is submitted and issued on a _phy_
>> doesn't wait for a _phy_ to stop and restart, but is submitted on a
Vinod Koul writes:
> On Fri, May 08, 2015 at 02:28:37PM +0200, Robert Jarzmik wrote:
>> Sorry I don't get this comment, would you care to explain me please ?
> Right now you are using very genric names which can conflict with others, so
> makese sense to add PXA_DCMD_LENGTH
>>
>> Fix arch/arm to correctly use "Hz", thereby acknowledging Heinrich Hertz
>> contribution to the modern world.
>>
>> Signed-off-by: Russell King
>
> Acked-by: Tony Lindgren
Acked-by: Robert Jarzmik
Cheers.
--
Robert
--
To unsubscribe from
Robert Jarzmik writes:
> Robert Jarzmik writes:
>
>> Robert Jarzmik writes:
>>
>>> Hi Vinod,
>>>
>>> This is the same serie as in v1, only one fix around irq probing was
>>> included in
>>> patch 3/5. I copy-pasted the previous c
Vinod Koul writes:
>> Would it be possible that I take that through the pxa tree, even it stays in
>> drivers/dmaengine ? I want that to land in the next cycle, and I'll take the
>> fixes and maintainance anyway on my back.
> Sorry about the delay, I should be able to get this done in next few da
Robert Jarzmik writes:
> Arnd Bergmann writes:
>
>> On Monday 15 December 2014 00:10:06 Robert Jarzmik wrote:
>>> +
>>> + platform_set_drvdata(pdev, cot);
>>> + cot->gpio0 = gpiod_get(&pdev->dev, "lubbock_irq", 0);
>&g
Daniel Lezcano writes:
> On 02/23/2015 08:40 PM, Robert Jarzmik wrote:
>
> Yes.
Thanks.
Cheers.
--
Robert
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.k
Robert Jarzmik writes:
> The commit "ARM: pxa: arbitrarily set first interrupt number" changed
> the first pxa interrupt to 16.
>
> As a consequence, device-tree builds got broken, because :
> - pxa_mask_irq() and pxa_unmask_irq() are using IRQ_BIT()
> - IRQ_BIT(x)
Ezequiel Garcia writes:
> Hi Antoine,
>
> On 03/05/2015 08:31 AM, Antoine Tenart wrote:
> [..]
>> +
>> +static struct pxa3xx_nand_flash berlin_builtin_flash_types[] = {
>> +{ "4GiB 8-bit",0xd7ec, 128, 8192, 8, 8, 4096 },
>> +{ },
>
> IMHO, supporting a specific flash shouldn't be part of th
Ezequiel Garcia writes:
>> I think you'll kill the zylonite board, and I'll nack it if that's the case.
>> At
>> least that's what happened when I tried to use onfi default values last time
>> in
>> barebox development.
>>
>> I can test your changes, but if the specific zylonite nand (ie. nand
Ezequiel Garcia writes:
>>> Which flash do you have there?
>> The one with 0xba20 id as I said, which is AFAIK a Numonyx NAND02GR4B2C.
>>
>
> $ grep "0xBA" drivers/mtd/nand/nand_ids.c
> EXTENDED_ID_NAND("NAND 256MiB 1,8V 16-bit", 0xBA, 256, LP_OPTIONS16),
>
> Seems already supported by the NAND
Greg Kroah-Hartman writes:
> On Fri, Feb 20, 2015 at 05:02:57PM +0100, Robert Jarzmik wrote:
>> If there is no solution, I'll fallback through arch/arm/plat-pxa, not very
>> nice,
>> but it has to land somewhere, I don't want lubbock to remain broken.
>
>
Arnd Bergmann writes:
> On Thursday 26 March 2015, Robert Jarzmik wrote:
>>
>> Greg Kroah-Hartman writes:
>>
>> > On Fri, Feb 20, 2015 at 05:02:57PM +0100, Robert Jarzmik wrote:
>> >> If there is no solution, I'll fallback through arch/arm/plat
Arnd Bergmann writes:
... removed people not concerned by pxa story ...
>> As for XIP support, I don't have a clear view if it's a requirement for
>> multiplatform nor if it works in these builds.
>
> It would be nice to not have to support both options: if we put pxa into
> ARCH_MULTIPLATFORM,
d legacy static platform data platforms, modify
>> platform_get_irq() to assign the trigger flags to the
>> irq descriptor when a client looks up an IRQ from static
>> resources.
>>
>> Fixes: d52fdbb735c3 ("smc91x: retrieve IRQ and trigger flags in a modern
>>
Vinod Koul writes:
> On Sun, Feb 15, 2015 at 07:49:16PM +0100, Robert Jarzmik wrote:
>> Fix the dmaengine complaint about missing slave caps :
>> - declare the available bus widths
>> - declare the available transfer types
>> - declare the residue calculation type
&
ces at no point assign the trigger flags to the
>>> corresponding IRQ descriptor.
>>>
>>> To make the behaviour identical on modern device tree
>>> and legacy static platform data platforms, modify
>>> platform_get_irq() to assign the trigger flags to the
&
David Miller writes:
> From: Robert Jarzmik
> Date: Thu, 19 Feb 2015 21:48:49 +0100
>
>> Linus has submitted the patch [1]. I'll be watching carefully until -rc4 that
>> this is applied. If it's not, I'll reping you to apply this revert. Until
>> the
Each pxa has an embedded OS Timers IP. The kernel cannot work without a
valid clocksource, and this adds the OS Timers to the pxa device-tree
description.
Signed-off-by: Robert Jarzmik
---
Since v1: removed clocksource node, pxa-timer being directly under
pxabus (Rob's co
x27;t
disable them automatically (unused clocks shutdown)
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 36
1 file changed, 32 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts/pxa27x.dtsi
index 80
Each pxa variant has 2 I2C busses on the SoC :
- the casual I2C
- the power I2C, normally driving power regulators, and capable of
receiving orders on core frequency modifications
Add the missing pwri2c to pxa description.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa2xx.dtsi | 9
Each pxa27x has an embedded usb udc controller. Add it in the pxa27x
device-tree description.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts/pxa27x.dtsi
index 7cbf36f
501 - 600 of 1327 matches
Mail list logo
