Hi Tony,
On Wed, Apr 13, 2011 at 05:00:30PM +0300, Tony Lindgren wrote:
> * Shawn Guo [110328 12:10]:
> > On Thu, Mar 24, 2011 at 04:18:41PM -0700, John Bonesio wrote:
> > > This patch provides the ability to boot using a device tree that is
> > > appended
> > > to the raw binary zImage (e.g. ca
PCIe device in legacy mode can trigger interrupts using the wires #INTA, #INTB
,#INTC and #INTD. PCI devices are obligated to use #INTx for interrupts under
legacy mode. Each PCI slot or device is typically wired to different inputs on
the interrupt controller.
So, Define interrupt-map and inter
On Wed, Apr 20, 2011 at 2:47 AM, Wolfram Sang wrote:
>
>> BTW, Are there reason to omit the sdhci-s3c.c? Maybe Mr. Jung will handle it.
>
> The difference is that sdhci-s3c.c was more like a fork of sdhci-pltfm while
> the others were users of it. With the new interface, s3c can be converted
> us
> There hasn't been any plans to do so, but if you need it then we can
> probably do so.
>
> Jon, how do you feel about cutting a release?
Happy to do so. I'll try to pull one together in the
next couple days or so.
jdl
___
devicetree-discuss mailing
On Tue, Apr 19, 2011 at 6:47 PM, Jeremy Kerr wrote:
> Hi Shawn,
>
>> It fixes the return value of funciont early_init_dt_scan_memory on
>> the success return path.
>
> [In general, the changelog should explain why you're making this change,
> not just re-iterate what the patch does. Does this fix
There hasn't been any plans to do so, but if you need it then we can
probably do so.
Jon, how do you feel about cutting a release?
On Tue, Apr 19, 2011 at 7:26 PM, David VomLehn wrote:
> I'd like to deploy dtc outside our kernel but have an IT department that
> wants a formally versioned release
I'd like to deploy dtc outside our kernel but have an IT department that
wants a formally versioned release. The last such release was 1.2.0 back in
July 2008 and it was missing a whole bunch of features that are required
for work we're doing. Anything we can do to make a 1.2.1 or 1.3.0 tag
get as
Hi Shawn,
> It fixes the return value of funciont early_init_dt_scan_memory on
> the success return path.
[In general, the changelog should explain why you're making this change,
not just re-iterate what the patch does. Does this fix a problem you
were seeing?]
With regards to this specific patc
On Wed, 20 Apr 2011 00:00:18 +0200
"Hans J. Koch" wrote:
> On Tue, Apr 19, 2011 at 12:08:16AM -0600, Grant Likely wrote:
> > PowerPC and x86 will return 0 for an unassigned IRQ, as will most platforms.
>
> That might be right for these architectures. On ARM SoCs, IRQ0 is often a
> normal irq lik
On Tue, Apr 19, 2011 at 12:08:16AM -0600, Grant Likely wrote:
> On Mon, Apr 18, 2011 at 10:50:54AM +0200, Michal Simek wrote:
> > Adding OF binding to genirq.
> > Version string is setup to the "devicetree".
> >
> > Compatible string is not setup for now but you can add your
> > custom compatible
On Tue, 19 Apr 2011 13:26:26 -0500
Meador Inge wrote:
> On 04/19/2011 12:52 PM, Scott Wood wrote:
> > On Tue, 19 Apr 2011 11:59:34 -0500
> > Meador Inge wrote:
> >
> >> Aliases are of the form 'msgr-block',
> >> +where is an integer specifying the block's number. Numbers shall
> >> star
On 04/19/2011 12:52 PM, Scott Wood wrote:
> On Tue, 19 Apr 2011 11:59:34 -0500
> Meador Inge wrote:
>
>> +- interrupt-parent: Specifies the interrupt parent of the message
>> register
>> + block. The type shall be a and the value of that
>> + shall point to the interrupt parent.
On Tue, 19 Apr 2011 11:59:34 -0500
Meador Inge wrote:
> +- interrupt-parent: Specifies the interrupt parent of the message
> register
> + block. The type shall be a and the value of that
> + shall point to the interrupt parent.
interrupt-parent is not required; it can be inheri
> BTW, Are there reason to omit the sdhci-s3c.c? Maybe Mr. Jung will handle it.
The difference is that sdhci-s3c.c was more like a fork of sdhci-pltfm while
the others were users of it. With the new interface, s3c can be converted using
pltfm more easily. If somebody is willing to do that, this i
Some MPIC implementations contain one or more blocks of message registers
that are used to send messages between cores via IPIs. A simple API has
been added to access (get/put, read, write, etc ...) these message registers.
The available message registers are initially discovered via nodes in the
This binding documents how the message register blocks found in some FSL
MPIC implementations shall be represented in a device tree.
Signed-off-by: Meador Inge
Cc: Hollis Blanchard
Cc: Grant Likely
Cc: Benjamin Herrenschmidt
---
.../devicetree/bindings/powerpc/fsl/mpic-msgr.txt | 71 ++
This patch set defines a binding for FSL MPIC message registers and implements
an API for accessing those message registers. Testing was done on a MPC8572DS
in an Linux-Linux AMP setup using OpenMCAPI (www.openmcapi.org) to communicate
between OS instances. The message register API is used by the
On Tue, Apr 19, 2011 at 06:14:12PM +0200, Wolfgang Grandegger wrote:
> On 04/18/2011 09:22 PM, Grant Likely wrote:
> > On Mon, Apr 18, 2011 at 1:22 PM, Wolfgang Grandegger
> > wrote:
> >> Hallo,
> >>
> >> I'm looking for a solution for the following problem:
> >>
> >> A device may be served by mo
On 04/18/2011 09:22 PM, Grant Likely wrote:
> On Mon, Apr 18, 2011 at 1:22 PM, Wolfgang Grandegger
> wrote:
>> Hallo,
>>
>> I'm looking for a solution for the following problem:
>>
>> A device may be served by more than one driver depending on the
>> application. Therefore the driver to use shoul
Hi Mounir,
Took me a while, but here are the instructions for testing DT support on IGEP:
The current nightly u-boot builds should work out-of-the-box with
device tree support. You can use the prebuilt binaries
>From what I can tell, the kernel build doesn't yet have DT enabled for
any of the p
On Tue, 19 Apr 2011 00:12:59 -0700
wrote:
> I am running Linux 2.6.32 on a P2020 and am trying to use the kernel’s DMA
> code. So far, I have had no success. Is there a mistake in
> linux/arch/powerc/boot/dts/p2020rdb.dts?
>
> According to linux/Documentation/powerpc/dts-bindings/fsl/dma.txt
On Tue, Apr 19, 2011 at 9:07 AM, Arnd Bergmann wrote:
> On Tuesday 19 April 2011, Grant Likely wrote:
>> > or whatever, as this would bind all instances matching vendor,device.
>> >
>> > So, the question I have is, how to handle bind per-instance?
>>
>> By manipulating a property on the device ins
On Tuesday 19 April 2011, Grant Likely wrote:
> > or whatever, as this would bind all instances matching vendor,device.
> >
> > So, the question I have is, how to handle bind per-instance?
>
> By manipulating a property on the device instance of course! :-)
>
> Something like: echo "generic-uio
It fixes the return value of funciont early_init_dt_scan_memory on
the success return path.
Signed-off-by: Shawn Guo
---
drivers/of/fdt.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c
index c9db49c..387336d 100644
--- a/drivers/of/f
Hi,
BTW, Are there reason to omit the sdhci-s3c.c? Maybe Mr. Jung will handle it.
Thank you,
Kyungmin Park
On Tue, Apr 19, 2011 at 7:20 PM, Wolfram Sang wrote:
> Hi Shawn,
>
> On Fri, Mar 25, 2011 at 04:48:46PM +0800, Shawn Guo wrote:
>> Here are what the patch set does.
>>
>> * Remove .probe a
This patch adds support for the PTP clock found on the DP83640.
The basic clock operations and one external time stamp have
been implemented.
Signed-off-by: Richard Cochran
---
drivers/net/phy/Makefile |1 +
drivers/net/phy/dp83640.c | 1100 +
This patch adds an infrastructure for hardware clocks that implement
IEEE 1588, the Precision Time Protocol (PTP). A class driver offers a
registration method to particular hardware clock drivers. Each clock is
presented as a standard POSIX clock.
The ancillary clock features are exposed in two di
On Monday, April 11, 2011 11:33:04 AM Domenico Andreoli wrote:
> From: Domenico Andreoli
>
> Assign proper OF node (= with matching physical base address) to each
> s3c24xx GPIO chip.
>
> Signed-off-by: Domenico Andreoli
>
> ---
>
> With this new patch there is no need to add the dt_compat fi
On Wednesday 13 April 2011 20:25:47 Domenico Andreoli wrote:
> From: Domenico Andreoli
>
> This patch adds DeviceTree support to the S3C SDI driver.
>
> It implements all the configurations of the platform driver except the
> set_power() callback and the ocr_avail mask.
>
> Signed-off-by: Domen
There is a TOCTOU bug in briq_panel_write() code:
if (vfd_cursor > 39) <<<
scroll_vfd();
vfd[vfd_cursor++] = c; <<<
It's possible to write to arbitrary memory location in case of more than
one process tries to call write() simultaneously.
Signed-off-by: Vasiliy Kulikov
---
Creates P2020si.dtsi, containing information for P2020 SoC. Modifies dts files
for P2020 based systems to use dtsi file.
Signed-off-by: Prabhakar Kushwaha
---
Based upon
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git(branch
master)
Please see mpc5200b.dtsi for reference
On Mon, 2011-04-18 at 08:29 +0200, Richard Cochran wrote:
> This patch adds a driver for the hardware time stamping unit found on the
> IXP465. The basic clock operations and an external trigger are implemented.
[...]
> --- a/drivers/net/arm/ixp4xx_eth.c
> +++ b/drivers/net/arm/ixp4xx_eth.c
[...]
>
On Mon, 2011-04-18 at 08:30 +0200, Richard Cochran wrote:
> This patch adds support for the PTP clock found on the DP83640.
> The basic clock operations and one external time stamp have
> been implemented.
[...]
> --- /dev/null
> +++ b/drivers/net/phy/dp83640.c
[...]
> +static int match(struct sk_b
On Tue, Apr 19, 2011 at 6:37 AM, John Williams
wrote:
> On Tue, Apr 19, 2011 at 4:11 PM, Grant Likely
> wrote:
>> On Tue, Apr 19, 2011 at 11:58:25AM +1000, John Williams wrote:
>>> On Tue, Apr 19, 2011 at 2:06 AM, Wolfram Sang wrote:
>>> > Hi,
>>> >
>>> >> For example with "uio" compatible stri
From: Bhaskar Upadhaya
Signed-off-by: Bhaskar Upadhaya
Acked-By: Scott Wood
---
Based upon git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
(branch -> master)
.../devicetree/bindings/net/can/fsl-flexcan.txt| 61
1 files changed, 61 insertions(+)
On Tuesday 19 April 2011, John Williams wrote:
> OK, so let's talk about this interface. As I see it, it must be able
> to handle bind per-instance, not per compatibility.
Yes.
> For example, we make systems with multiple, identical timers. One
> will be used as the system timer, the others nee
On Tue, Apr 19, 2011 at 4:11 PM, Grant Likely wrote:
> On Tue, Apr 19, 2011 at 11:58:25AM +1000, John Williams wrote:
>> On Tue, Apr 19, 2011 at 2:06 AM, Wolfram Sang wrote:
>> > Hi,
>> >
>> >> For example with "uio" compatible string:
>> >> static const struct of_device_id __devinitconst uio_of_
On Fri, Mar 25, 2011 at 04:48:51PM +0800, Shawn Guo wrote:
> The structure sdhci_pltfm_data is not necessarily to be in a public
> header like include/linux/mmc/sdhci-pltfm.h, so the patch moves it
> into drivers/mmc/host/sdhci-pltfm.h and eliminates the former one.
>
> Signed-off-by: Shawn Guo
> config MMC_SDHCI_ESDHC_IMX
> - bool "SDHCI platform support for the Freescale eSDHC i.MX controller"
> + bool "SDHCI support for the Freescale eSDHC i.MX controller"
> depends on ARCH_MX25 || ARCH_MX35 || ARCH_MX5
> depends on MMC_SDHCI
> - select MMC_SDHCI_PLTFM
> +
> +static int __devinit sdhci_esdhc_probe(struct platform_device *pdev)
> +{
> + struct sdhci_host *host;
> + int ret;
> +
> + host = sdhci_pltfm_init(pdev, &sdhci_esdhc_pdata);
> + if (!host)
> + return -ENOMEM;
Just noticed: Since pltfm_init may fail due to various r
On Fri, Mar 25, 2011 at 04:48:48PM +0800, Shawn Guo wrote:
> The patch is to migrate the use of sdhci_of_host and sdhci_of_data
> to sdhci_pltfm_host and sdhci_pltfm_data, so that the former pair can
> be eliminated.
>
> Signed-off-by: Shawn Guo
> ---
[...]
> diff --git a/drivers/mmc/host/sdhci
On Fri, Mar 25, 2011 at 04:48:47PM +0800, Shawn Guo wrote:
> The patch turns the common stuff in sdhci-pltfm.c into functions, and
> add device drivers their own .probe and .remove which in turn call
> into the common functions, so that those sdhci-pltfm device drivers
> register itself and keep a
Hi Shawn,
On Fri, Mar 25, 2011 at 04:48:46PM +0800, Shawn Guo wrote:
> Here are what the patch set does.
>
> * Remove .probe and .remove hooks from sdhci-pltfm.c and make it be
> a pure common helper function providers.
> * Add .probe and .remove hooks for sdhci pltfm drivers sdhci-cns3xxx,
>
Arnd Bergmann wrote:
On Tuesday 19 April 2011, Grant Likely wrote:
On Tue, Apr 19, 2011 at 11:58:25AM +1000, John Williams wrote:
I know the arguments against the 'generic-uio' tag, but come on, let's
look at the lesser of two evils here! I call BS on this DTS purity.
Both a specific device
Wolfram Sang wrote:
Hi,
For example with "uio" compatible string:
static const struct of_device_id __devinitconst uio_of_genirq_match[] = {
{ .compatible = "uio", },
{ /* empty for now */ },
};
Please use a proper example with "vendor,device".
(And after that it won't be empty
Grant Likely wrote:
On Mon, Apr 18, 2011 at 10:50:54AM +0200, Michal Simek wrote:
Adding OF binding to genirq.
Version string is setup to the "devicetree".
Compatible string is not setup for now but you can add your
custom compatible string to uio_of_genirq_match structure.
For example with "u
On Tuesday 19 April 2011, Grant Likely wrote:
> On Tue, Apr 19, 2011 at 11:58:25AM +1000, John Williams wrote:
> >
> > I know the arguments against the 'generic-uio' tag, but come on, let's
> > look at the lesser of two evils here! I call BS on this DTS purity.
Both a specific device ID and somet
I am running Linux 2.6.32 on a P2020 and am trying to use the kernel’s DMA
code. So far, I have had no success. Is there a mistake in
linux/arch/powerc/boot/dts/p2020rdb.dts?
According to linux/Documentation/powerpc/dts-bindings/fsl/dma.txt, the
compatible lists for DMA controllers and the DM
48 matches
Mail list logo
