On Wednesday 13 March 2013 10:16 PM, Benoit Cousson wrote:
> Hi Sourav,
>
> I've just applied your branch after a minor subject cleanup for consistency.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git
> for_3.10/dts
>
Thanks for the tree Benoit. I shall update my v2
On Wed, Mar 13, 2013 at 10:49:45AM +, Mark Brown wrote:
> On Wed, Mar 13, 2013 at 10:18:29AM +0800, Shawn Guo wrote:
>
> > I did not see any objection from you on that patch, so I'm waiting for
> > you to publish a branch for it, so that my mxs-dma generic binding
> > series can move forward.
None of mxsfb users uses mxsfb_platform_data now. Let's remove it
from mxsfb driver.
As the result, include/linux/mxsfb.h gets deleted with a few macros
moved into mxsfb.c. Along with the change, the typo "FAILING" in macro
name is fixed to be "FALLING".
Signed-off-by: Shawn Guo
---
drivers/v
Move display timing configurations into device tree, so that the
auxdata for mxsfb driver can be killed.
Signed-off-by: Shawn Guo
---
arch/arm/boot/dts/imx23-evk.dts| 25 ++
arch/arm/boot/dts/imx28-apf28dev.dts | 25 ++
arch/arm/boot/dts/imx28-apx4devkit.dts | 25 ++
Use videomode helpers to get display timings and configurations from
device tree when platform_data is absent.
Signed-off-by: Shawn Guo
---
Documentation/devicetree/bindings/fb/mxsfb.txt | 34 +++
drivers/video/Kconfig |2 +
drivers/video/mxsfb.c
There is no in-tree mxsfb users using mxsfb_platform_data dotclk_delay.
Let's remove it from mxsfb_platform_data to ease full device tree
adoption of mxsfb driver. If later we have platform/board need to
configure this parameter, we can add it into device tree bindings.
Signed-off-by: Shawn Guo
Use devm_* managed functions to make code a little cleaner.
Signed-off-by: Shawn Guo
---
drivers/video/mxsfb.c | 50 -
1 file changed, 16 insertions(+), 34 deletions(-)
diff --git a/drivers/video/mxsfb.c b/drivers/video/mxsfb.c
index 76c..2c
There is no in-tree users of mxsfb_platform_data fb_phys/fb_size.
With CMA support in the kernel, there is no real need for platform to
reserve memory and pass address and size into driver via platform_data.
So let's remove fb_phys/fb_size from mxsfb_platform_data to ease full
device tree adoption.
The mxsfb driver was converted to device tree by asking platform to
pass mxsfb_platform_data with auxdata. We did this to have mach-mxs
be DT only platform when there was no videomode bindings. Now with
the videomode bindings and helpers in place, the series changes mxsfb
driver to get display_ti
On 03/13/2013 03:33 PM, Thierry Reding wrote:
> On Wed, Mar 13, 2013 at 10:58:02AM -1000, Mitch Bradley wrote:
> [...]
>> In this case, the answer to "what does pcie_controller do?" is
>> "it implements a PCI bus" below. So 'device_type = "pci"' is
>> appropriate.
>
> Alright, that's 2 against 1
On 03/13/2013 05:48 PM, Mitch Bradley wrote:
> On 3/13/2013 11:33 AM, Thierry Reding wrote:
>> On Wed, Mar 13, 2013 at 10:58:02AM -1000, Mitch Bradley wrote:
>> [...]
>>> In this case, the answer to "what does pcie_controller do?" is "it
>>> implements a PCI bus" below. So 'device_type = "pci"' is
Hi Shaik,
On 03/11/2013 07:41 AM, Shaik Ameer Basha wrote:
Hi Sylwester,
Thanks for the review.
Actually I know this is the important patch in this series and I
wanted us to have
enough time to discuss on this patch. That's why I posted this patch
series in hurry.
Sure, I'm glad it was posted
On 03/13/2013 02:27 PM, Christian Daudt wrote:
This adds support for the Broadcom timer, used in the following SoCs:
BCM11130, BCM11140, BCM11351, BCM28145, BCM28155
[snip]
Signed-off-by: Christian Daudt
Acked-by: Arnd Bergmann
Acked-by: John Stultz
Reviewed-by: Stephen Warren
Hey Olof,
Rob,
On 03/13/2013 03:39 PM, Rob Herring wrote:
I fail to see what the hack is. The order of interrupt properties must
be defined by the binding. interrupt-names is auxiliary data and must
not be required by an OS.
It is clear that the order of the interrupts must be defined by the
bindings. B
On Wed, Mar 13, 2013 at 10:58:02AM -1000, Mitch Bradley wrote:
> port hardware used the common programming model, with real config
> headers and stuff, 3/2 would be good because you could use existing
> drivers. But since you need a special root-port driver anyway, why go
> to the trouble of emul
On Wed, Mar 13, 2013 at 11:02:35PM +0100, Thierry Reding wrote:
> Does that look about correct?
By my reading of the spec the entries in ranges should not
have the b,d,f bits set..
Although it is not a big stretch to include them..
> Now the code will actually match the first entry and assume
On Wed, Mar 13, 2013 at 10:58:02AM -1000, Mitch Bradley wrote:
[...]
> But then you run into the problem that the pci variant of struct of_bus
> uses "assigned-addresses" instead of "reg". So it still doesn't work
> as-is. To make it work, you would need to add an "assigned-addresses"
> property
On Wed, Mar 13, 2013 at 10:58:02AM -1000, Mitch Bradley wrote:
[...]
> In this case, the answer to "what does pcie_controller do?" is "it
> implements a PCI bus" below. So 'device_type = "pci"' is appropriate.
Alright, that's 2 against 1. I don't have much of a choice but to yield.
> Having just
On Wed, Mar 13, 2013 at 01:52:35PM -0700, Doug Anderson wrote:
> Hi,
>
> On Tue, Mar 12, 2013 at 9:08 PM, Naveen Krishna Chatradhi
> wrote:
> > This patch adds DT support to NTC driver to parse the
> > platform data.
> >
> > Also adds the support to work as an iio device.
> >
> > During the probe
On 3/13/2013 4:41 PM, Stephen Warren wrote:
On 03/13/2013 01:25 PM, Rhyland Klein wrote:
On 3/12/2013 7:10 PM, Stephen Warren wrote:
On 03/12/2013 04:08 PM, Rhyland Klein wrote:
This change adds the binding documentation for the tps65090-charger.
diff --git
a/Documentation/devicetree/bindings/
On Wed, Mar 13, 2013 at 01:59:01PM -0600, Jason Gunthorpe wrote:
> On Wed, Mar 13, 2013 at 08:26:28PM +0100, Thierry Reding wrote:
>
> > As Mitch already said there's very little chance that the specification
> > update will be ratified through IEEE, so I think that we might just as
> > well put a
Hi,
On Tue, Mar 12, 2013 at 9:08 PM, Naveen Krishna Chatradhi
wrote:
> This patch adds DT support to NTC driver to parse the
> platform data.
>
> Also adds the support to work as an iio device.
>
> During the probe ntc driver gets the respective channels of ADC
> and uses iio_raw_read calls to ge
On 03/13/2013 01:25 PM, Rhyland Klein wrote:
> On 3/12/2013 7:10 PM, Stephen Warren wrote:
>> On 03/12/2013 04:08 PM, Rhyland Klein wrote:
>>> This change adds the binding documentation for the tps65090-charger.
>>> diff --git
>>> a/Documentation/devicetree/bindings/power_supply/tps65090.txt
>>> b/
The exynos ADC won't work without a regulator called "vdd" and a clock
called "adc". Document this fact in the device tree bindings.
Signed-off-by: Doug Anderson
---
Changes in v2: None
Documentation/devicetree/bindings/arm/samsung/exynos-adc.txt | 8
1 file changed, 8 insertions(+)
(some of which is still in-flight) and does the final touches to get
things working on exynos5250-snow (the ARM Chromebook).
These patches were tested on next-20130312 (which includes support for
the common clock framework on exynos) plus the current linux-iio/togreg:
95783f2 iio: adc: add exyno
Without this change the exynos adc controller needed to have its phy
enabled in some out-of-driver C code. Add support for specifying the
phy enable register by listing it in the reg list.
Signed-off-by: Doug Anderson
---
Changes in v2: None
.../devicetree/bindings/arm/samsung/exynos-adc.txt
On Wednesday 13 March 2013 06:59 PM, Wei Yongjun wrote:
From: Wei Yongjun
The variable bits_per_word is initialized but never used
otherwise, so remove the unused variable.
Signed-off-by: Wei Yongjun
---
drivers/spi/spi-tegra20-slink.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/
On Wed, Mar 13, 2013 at 08:26:28PM +0100, Thierry Reding wrote:
> As Mitch already said there's very little chance that the specification
> update will be ratified through IEEE, so I think that we might just as
> well put a corresponding text somewhere below Documentation/devicetree.
Sure, I'm fi
On Wed, Mar 13, 2013 at 11:02:05AM -0600, Jason Gunthorpe wrote:
> On Wed, Mar 13, 2013 at 09:18:15AM +0100, Thierry Reding wrote:
>
> > Mitch already answered this. The specification is now almost 15 years
> > old and it couldn't possibly have foreseen all of the future use-cases.
> > If the spec
On 3/12/2013 7:10 PM, Stephen Warren wrote:
On 03/12/2013 04:08 PM, Rhyland Klein wrote:
This change adds the binding documentation for the tps65090-charger.
diff --git a/Documentation/devicetree/bindings/power_supply/tps65090.txt
b/Documentation/devicetree/bindings/power_supply/tps65090.txt
+E
On Wednesday 13 March 2013 10:16 PM, Benoit Cousson wrote:
Hi Sourav,
I've just applied your branch after a minor subject cleanup for consistency.
git://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git
for_3.10/dts
Thanks Benoit!
Regards,
Benoit
On 03/11/2013 04:42 PM,
On Wed, Mar 13, 2013 at 5:41 PM, Benoit Cousson wrote:
> Hi Javier,
>
> On 03/02/2013 02:52 AM, Javier Martinez Canillas wrote:
>> On Fri, Feb 15, 2013 at 11:03 AM, Cousson, Benoit wrote:
>>> Hi Matthias,
>>>
>>>
>>> On 2/15/2013 10:35 AM, Matthias Brugger wrote:
2013/1/26 Javier Martin
On Mon, Mar 11, 2013 at 3:23 PM, Wei Yongjun wrote:
> From: Wei Yongjun
>
> Using for_each_set_bit() to simplify the code.
>
> Signed-off-by: Wei Yongjun
Barry, can I have your ACK on this?
Yours,
Linus Walleij
___
devicetree-discuss mailing list
de
On 03/13/2013 10:59 AM, Doug Anderson wrote:
> Stephen,
>
> On Wed, Mar 13, 2013 at 9:53 AM, Stephen Warren wrote:
>>> Changes in v4: None
>>
>> Isn't this 'PATCH V3 REPOST' then?
>
> In this case part 2 in the patch series changes but not parts 1 and 3.
> I could have just reposted part 2 with
On Wed, Mar 13, 2013 at 09:18:15AM +0100, Thierry Reding wrote:
> Mitch already answered this. The specification is now almost 15 years
> old and it couldn't possibly have foreseen all of the future use-cases.
> If the specification is too restrictive and Mitch gives his blessing to
> remove some
Stephen,
On Wed, Mar 13, 2013 at 9:53 AM, Stephen Warren wrote:
>> Changes in v4: None
>
> Isn't this 'PATCH V3 REPOST' then?
In this case part 2 in the patch series changes but not parts 1 and 3.
I could have just reposted part 2 with a higher version, but that
makes it a little harder to piec
* Roger Quadros [130313 09:40]:
> On 03/13/2013 06:24 PM, Tony Lindgren wrote:
> > * Roger Quadros [130313 06:46]:
> >> On 03/12/2013 06:40 PM, Tony Lindgren wrote:
> >>> * Roger Quadros [130312 04:47]:
> Hi Tony,
>
> These patches provide the SoC side code required to support
> >
On 03/13/2013 10:36 AM, Doug Anderson wrote:
> The i2c-arbitrator-cros-ec driver implements the arbitration scheme
> that the Embedded Controller (EC) on the ARM Chromebook expects to use
> for bus multimastering. This i2c-arbitrator-cros-ec driver could also
> be used in other places where standa
Hi Sourav,
I've just applied your branch after a minor subject cleanup for consistency.
git://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git
for_3.10/dts
Regards,
Benoit
On 03/11/2013 04:42 PM, Sourav Poddar wrote:
> On Monday 11 March 2013 08:02 PM, Benoit Cousson wrote:
Hi Javier,
On 03/02/2013 02:52 AM, Javier Martinez Canillas wrote:
> On Fri, Feb 15, 2013 at 11:03 AM, Cousson, Benoit wrote:
>> Hi Matthias,
>>
>>
>> On 2/15/2013 10:35 AM, Matthias Brugger wrote:
>>>
>>> 2013/1/26 Javier Martinez Canillas :
On Sat, Jan 26, 2013 at 4:16 PM, Matthias Br
The i2c-arbitrator-cros-ec driver implements the arbitration scheme
that the Embedded Controller (EC) on the ARM Chromebook expects to use
for bus multimastering. This i2c-arbitrator-cros-ec driver could also
be used in other places where standard I2C bus arbitration can't be
used and two extra GP
On 03/13/2013 06:24 PM, Tony Lindgren wrote:
> * Roger Quadros [130313 06:46]:
>> On 03/12/2013 06:40 PM, Tony Lindgren wrote:
>>> * Roger Quadros [130312 04:47]:
Hi Tony,
These patches provide the SoC side code required to support
the changes in the OMAP USB Host drivers done
* Roger Quadros [130313 06:46]:
> On 03/12/2013 06:40 PM, Tony Lindgren wrote:
> > * Roger Quadros [130312 04:47]:
> >> Hi Tony,
> >>
> >> These patches provide the SoC side code required to support
> >> the changes in the OMAP USB Host drivers done in [1], [2] & [3].
> > ...
> >
> >> arch/arm
On 03/13/2013 04:50 PM, Jon Hunter wrote:
>
> On 03/13/2013 10:35 AM, Benoit Cousson wrote:
>> Salut Jon,
>>
>> On 03/12/2013 10:43 PM, Jon Hunter wrote:
>>> Salut Benoit!
>>>
>>> On 03/12/2013 06:00 AM, Benoit Cousson wrote:
+ Seb G.
Hi Jon,
How to you plan to merge that
On 03/13/2013 04:17 PM, Peter Ujfalusi wrote:
> On 03/12/2013 04:20 PM, Roger Quadros wrote:
>> Adding Peter to the loop. I faintly remember him mentioning this issue before
>> for beagle. We really need the deferred probe mechanism or we need to resort
>> to device registering order.
>
> Yes, Bea
On 03/13/2013 10:35 AM, Benoit Cousson wrote:
> Salut Jon,
>
> On 03/12/2013 10:43 PM, Jon Hunter wrote:
>> Salut Benoit!
>>
>> On 03/12/2013 06:00 AM, Benoit Cousson wrote:
>>> + Seb G.
>>>
>>> Hi Jon,
>>>
>>> How to you plan to merge that series?
>>
>> Good question ... my thinking was that you
On 03/13/2013 05:17 PM, Peter Ujfalusi wrote:
> On 03/12/2013 04:20 PM, Roger Quadros wrote:
>> Adding Peter to the loop. I faintly remember him mentioning this issue before
>> for beagle. We really need the deferred probe mechanism or we need to resort
>> to device registering order.
>
> Yes, Bea
Salut Jon,
On 03/12/2013 10:43 PM, Jon Hunter wrote:
> Salut Benoit!
>
> On 03/12/2013 06:00 AM, Benoit Cousson wrote:
>> + Seb G.
>>
>> Hi Jon,
>>
>> How to you plan to merge that series?
>
> Good question ... my thinking was that you or Tony would take 1/2 and
> once that is queued then I woul
Add support for 'depth' property to configure default frame
buffer color depth over device tree.
Signed-off-by: Anatolij Gustschin
---
.../devicetree/bindings/powerpc/fsl/diu.txt|2 ++
drivers/video/fsl-diu-fb.c | 16
2 files changed, 18 ins
On 03/12/2013 04:20 PM, Roger Quadros wrote:
> Adding Peter to the loop. I faintly remember him mentioning this issue before
> for beagle. We really need the deferred probe mechanism or we need to resort
> to device registering order.
Yes, BeagleBoard is a good example. Long story short: we have e
The subject is completely misleading. Make it clear what the scope of
this patch is.
On 03/13/2013 06:26 AM, Vikas Sajjan wrote:
> The FIMD driver expects the "vsync" interrupt to be mentioned as the 1st
> parameter in the FIMD DT node. So to meet this expectation of the driver,
> the FIMD DT node
On Thu, Mar 7, 2013 at 2:17 PM, Ian Lartey wrote:
> From: J Keerthy
>
> Enable DT support for palmas gpio.
>
> Signed-off-by: J Keerthy
This needs to be CC: to devicetree-discuss.
> +static struct of_device_id of_palmas_match_tbl[] = {
> + { .compatible = "ti,palmas-gpio", },
> +
On 03/12/2013 06:40 PM, Tony Lindgren wrote:
> * Roger Quadros [130312 04:47]:
>> Hi Tony,
>>
>> These patches provide the SoC side code required to support
>> the changes in the OMAP USB Host drivers done in [1], [2] & [3].
> ...
>
>> arch/arm/mach-omap2/board-3430sdp.c| 97 +
From: Wei Yongjun
The variable bits_per_word is initialized but never used
otherwise, so remove the unused variable.
Signed-off-by: Wei Yongjun
---
drivers/spi/spi-tegra20-slink.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/spi/spi-tegra20-slink.c b/drivers/spi/spi-tegra20-sl
On 03/12/2013 06:07 PM, Alan Stern wrote:
> On Tue, 12 Mar 2013, Roger Quadros wrote:
>
>> The HSIC devices need to be kept in reset while the EHCI controller
>> is being initialized and only brought out of reset after the
>> initialization is complete, else HSIC devices will not be detected.
>
>
The FIMD driver expects the "vsync" interrupt to be mentioned as the 1st
parameter in the FIMD DT node. So to meet this expectation of the driver,
the FIMD DT node was forced to be made by keeping "vsync" as the 1st
parameter.
this resolves the above mentioned "hack" by introducing
"interrupt-name
On Wed, Mar 13, 2013 at 08:32:53AM +0300, Dan Carpenter wrote:
> "val" has to be signed for the error handling to work.
Applied, thanks.
signature.asc
Description: Digital signature
___
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.or
On Wed, Mar 13, 2013 at 10:18:29AM +0800, Shawn Guo wrote:
> I did not see any objection from you on that patch, so I'm waiting for
> you to publish a branch for it, so that my mxs-dma generic binding
> series can move forward.
I commented on the removal of the const from the name parameter (and
> +
> + fimd: fimd@11c0 {
> + compatible = "samsung,exynos4210-fimd";
> + interrupt-parent = <&combiner>;
> + reg = <0x11c0 0x2>;
> + interrupt-names = "fifo", "vsync", "lcd_sys";
> + interrupts = <11 0>, <11 1>
On 13.03.2013 06:32, Dan Carpenter wrote:
> "val" has to be signed for the error handling to work.
Absolutely.
> Signed-off-by: Dan Carpenter
Acked-by: Daniel Mack
>
> diff --git a/sound/soc/codecs/tas5086.c b/sound/soc/codecs/tas5086.c
> index 008bea4..41d03ae 100644
> --- a/sound/soc/code
On 13 March 2013 15:39, Vikas Sajjan wrote:
> Adds FIMD DT binding documentation both Samsung SoC and Board, with an example
s/documentation both/documentation for both
___
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://list
On Wed, Mar 13, 2013 at 03:41:15PM +0530, Vivek Gautam wrote:
> Hi Felipe,
>
>
> On Wed, Feb 27, 2013 at 8:13 PM, Vivek Gautam
> wrote:
> > Based on 'usb-next'
> >
> > Changes from v5:
> > - Squashed the following change from Felipe in this patch-set:
> >[PATCH] usb: phy: samsung: let it b
Hi Felipe,
On Wed, Feb 27, 2013 at 8:13 PM, Vivek Gautam wrote:
> Based on 'usb-next'
>
> Changes from v5:
> - Squashed the following change from Felipe in this patch-set:
>[PATCH] usb: phy: samsung: let it be built as a module
> - Using EXPORT_SYMBOL_GPL() to export symbols in "samsung-us
Adds FIMD DT binding documentation both Samsung SoC and Board, with an example
Signed-off-by: Vikas Sajjan
---
.../devicetree/bindings/video/samsung-fimd.txt | 58
1 file changed, 58 insertions(+)
create mode 100644 Documentation/devicetree/bindings/video/samsung-fimd
Adds the FIMD AUXDATA node
Signed-off-by: Vikas Sajjan
---
arch/arm/mach-exynos/mach-exynos4-dt.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/mach-exynos/mach-exynos4-dt.c
b/arch/arm/mach-exynos/mach-exynos4-dt.c
index b68115a..b32a929 100644
--- a/arch/arm/mach-exynos/mac
Adds FIMD DT support to Origen quad board
Signed-off-by: Vikas Sajjan
---
arch/arm/boot/dts/exynos4412-origen.dts | 22 ++
1 file changed, 22 insertions(+)
diff --git a/arch/arm/boot/dts/exynos4412-origen.dts
b/arch/arm/boot/dts/exynos4412-origen.dts
index 31e14c4..a6fd41
From: Sachin Kamat
This patch adds the lcd panel related picntrl nodes for Exynos4412 SoC
Signed-off-by: Sachin Kamat
Signed-off-by: Vikas Sajjan
---
arch/arm/boot/dts/exynos4x12-pinctrl.dtsi | 14 ++
1 file changed, 14 insertions(+)
diff --git a/arch/arm/boot/dts/exynos4x12-pi
This adds common FIMD device node for all Exynos4 SoCs.
Signed-off-by: Vikas Sajjan
---
arch/arm/boot/dts/exynos4.dtsi |8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/exynos4.dtsi b/arch/arm/boot/dts/exynos4.dtsi
index 6581bb2..26190e0 100644
--- a/arch/arm/boot/
This patch series adds support for DRM FIMD DT for Exynos4 DT Machines,
specifically for Exynos4412 SoC.
changes since v6:
- addressed comments and added interrupt-names = "fifo", "vsync",
"lcd_sys"
in exynos4.dtsi and re-ordered the interrupt numbering to match the
order in
Benoit,
Will you be queuing this patch series?
Thanks
Kishon
On Thursday 07 March 2013 07:05 PM, Kishon Vijay Abraham I wrote:
Hi Benoit,
Here are the dt data patches to get usb device functional in OMAP platforms.
All the patches deal with modifying arch/arm/boot except one which modifies
D
From: Mugunthan V N
Date: Tue, 12 Mar 2013 14:46:33 +0530
> This patch serires implements the following features in CPSW driver
> * get/set phy link settings
> * interrupt pacing
> * get phy id via ioctl cmd SIOCGMIIPHY
>
> Changes from initial version
> * Made active-slave common for cpts, etht
On Tue, Mar 12, 2013 at 04:08:54PM -0600, Jason Gunthorpe wrote:
> On Tue, Mar 12, 2013 at 10:30:06PM +0100, Thierry Reding wrote:
>
> > > Not going down the of_pci_* code paths for address translation at the
> > > root port bridge nodes is certainly not right.
> >
> > I'm not so sure. Why should
72 matches
Mail list logo
