Ryan Mallon wrote:
On 22/12/11 01:32, Michal Simek wrote:
NO_IRQ shouldn't be used by any driver. All Microblaze
drivers are fixed that's why NO_IRQ can be removed.
This only describes half of what the patch does. You should also state
that arch/microblaze/pci/pci-common.c has references to
Hi Stephen,
-Original Message-
From: Stephen Warren [mailto:swar...@nvidia.com]
Sent: Wednesday, December 21, 2011 8:39 AM
To: Dong Aisheng-B29396; linux-ker...@vger.kernel.org
Cc: linus.wall...@stericsson.com; s.ha...@pengutronix.de;
rob.herr...@calxeda.com;
Hi Rob,
On 12/20/2011 5:42 PM, Rob Herring wrote:
On 12/20/2011 10:27 AM, Benoit Cousson wrote:
Add initial DT support to retrieve the frequency using a
DT attribute instead of the pdata pointer if of_node exist.
Add documentation for omap i2c controller binding.
Based on original patches
Hello,
On Wed, Dec 21, 2011 at 08:28:47PM +, Alan Cox wrote:
On Wed, 21 Dec 2011 16:05:59 +0100
Uwe Kleine-König u.kleine-koe...@pengutronix.de wrote:
Signed-off-by: Uwe Kleine-König u.kleine-koe...@pengutronix.de
---
Hello,
note that ARCH_EFM32 isn't in mainline yet, so to be
On Wed, Dec 21, 2011 at 11:00:44PM +0800, Shawn Guo wrote:
It improves mc13xxx dt binding document on how the regulator name
is being used for binding a mc13892 regulator device.
Signed-off-by: Shawn Guo shawn@linaro.org
Cc: Samuel Ortiz sa...@linux.intel.com
Reviewed-by: Mark Brown
On Wed, Dec 21, 2011 at 11:00:45PM +0800, Shawn Guo wrote:
It's not really necessary to add a prefix 'MC13892__' for each mc13892
regulator name, since the chip must have been identified as mc13892
when we look at the regulator name.
Applied, thanks.
Signed-off-by: Shawn Guo
On Wed, Dec 21, 2011 at 11:00:46PM +0800, Shawn Guo wrote:
It adds device tree probe support for mc13892-regulator driver.
Applied, thanks.
___
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
On Thu, Dec 22, 2011 at 11:08:30AM +, Mark Brown wrote:
On Wed, Dec 21, 2011 at 11:00:45PM +0800, Shawn Guo wrote:
It's not really necessary to add a prefix 'MC13892__' for each mc13892
regulator name, since the chip must have been identified as mc13892
when we look at the regulator
From: Dong Aisheng dong.aish...@linaro.org
Make this macro easier to use(do not need to pass properties, a node is
enough), also change to a more sensible name as for_each_child_of_node.
Signed-off-by: Dong Aisheng dong.aish...@linaro.org
Cc: Grant Likely grant.lik...@secretlab.ca
Cc: Rob
On 12/21/2011 07:40 PM, Jeff Garzik wrote:
On 12/21/2011 07:14 PM, David Miller wrote:
From: Rob Herringrobherri...@gmail.com
Date: Wed, 21 Dec 2011 17:25:15 -0600
On 12/21/2011 04:38 PM, David Miller wrote:
It depends upon CONFIG_OF_IRQ which not all CONFIG_OF platforms
support,
in
Hi Olof,
On 12/20/2011 10:24 PM, Olof Johansson wrote:
Hi,
On Tue, Dec 20, 2011 at 8:27 AM, Benoit Coussonb-cous...@ti.com wrote:
diff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
index a43d002..dcbc1ec 100644
--- a/drivers/i2c/busses/i2c-omap.c
+++
Hi Jon,
Has this been applied? I cannot see it in the repo.
Please can you let me know about the status of this patch?
Regards,
Simon
Simon,
Sorry. Except for a minor we should test this comment
from David, I thought my devtree patch queue was empty.
If you (or anyone else) has an
Hi Tony and Rob,
Here is the updated version of the i2c + twl DT adaptation series.
This update, compared to v3 [1], is fixing the twl-core build for non-OMAP
platform.
Per Olof's suggestion, adding the of.h include in the i2c driver to avoid
problem in case on non-DT build.
Patches are based
In the case of DT, the PMIC and SR initialization will be done using
a completely different mechanism.
Disable this part if a DT blob is available.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Acked-by: Kevin Hilman khil...@ti.com
---
arch/arm/mach-omap2/pm.c |8
1 files changed,
Add initial DT support to retrieve the frequency using a
DT attribute instead of the pdata pointer if of_node exist.
Add documentation for omap i2c controller binding.
Based on original patches from Manju and Grant.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Cc: Ben Dooks
Add initial device-tree support for twl familly chips.
The current version is missing the regulator entries due
to the lack of DT regulator bindings for the moment.
Only the simple sub-modules that do not depend on
platform_data information can be initialized properly.
Add irqdomain support.
Add
Add i2c controllers nodes into the main ocp bus.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Cc: Grant Likely grant.lik...@secretlab.ca
Cc: Rob Herring rob.herr...@calxeda.com
---
arch/arm/boot/dts/omap4.dtsi | 28
1 files changed, 28 insertions(+), 0
Add the DT support for the TI rtc-twl present in the twl4030
and twl6030 devices.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Cc: Alessandro Zummo a.zu...@towertech.it
---
Documentation/devicetree/bindings/rtc/twl-rtc.txt | 12
drivers/rtc/rtc-twl.c
Add i2c controllers nodes into the main ocp bus.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Cc: Grant Likely grant.lik...@secretlab.ca
Cc: Rob Herring rob.herr...@calxeda.com
---
arch/arm/boot/dts/omap3.dtsi | 21 +
1 files changed, 21 insertions(+), 0 deletions(-)
Add a dedicated DTS file for the twl6030 Power IC.
This chip is a big SoC that will be reused in a lot of various
OMAP4+ boards.
Note: This file is supposed to be included in a board DTS that will
create the twl node in order to allow the twl reference to work.
Exmaple:
...
i2c1 {
twl:
Add a dedicated DTS file for the twl4030/5030 Power + Audio IC.
This chip is a big SoC that will be reused in a lot of various
OMAP3 boards.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Cc: Grant Likely grant.lik...@secretlab.ca
Cc: Rob Herring rob.herr...@calxeda.com
---
Update pandaboard dts file with required clock frequencies
for the i2c client devices existing on pandaboard.
Add the twl6030 node in i2c1 controller.
This is the minimal support needed to boot OMAP4 boards
without any crash.
The support for all the features included in this MFD will be
added
Add required clock frequencies for the i2c client devices existing
on beagle board.
Add the twl4030 basic description with only the twl_rtc module.
Add the EEPROM node.
Based on original patch from Manju:
http://www.spinics.net/lists/linux-omap/msg55831.html
Signed-off-by: Benoit Cousson
Update DTS file with required clock frequencies
for the i2c client devices existing on sdp4430.
Add the twl6030 node inside the i2c1 controller node.
This is the minimal support needed to boot OMAP4 boards
without any crash.
The support for all the features included in this MFD will be
added
This mainly reverts the commit that was adding the i2c static init.
Since the i2c and twl nodes are now present, there is no need
for the static initialization anymore.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Cc: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/board-generic.c |
On 12/20/2011 10:27 AM, Benoit Cousson wrote:
Hi Tony and Rob,
Here is the updated version of the i2c + twl DT adaptation series.
This update, compared to v2 [1], is adding some dedicated dtsi files for
the twl PMIC and audio IC. These devices will contain a huge amount of
regulator nodes
On 12/22/2011 06:19 AM, Dong Aisheng wrote:
From: Dong Aisheng dong.aish...@linaro.org
Make this macro easier to use(do not need to pass properties, a node is
enough), also change to a more sensible name as for_each_child_of_node.
Signed-off-by: Dong Aisheng dong.aish...@linaro.org
Cc:
Hi Shawn,
On Wed, Dec 21, 2011 at 11:00:44PM +0800, Shawn Guo wrote:
It improves mc13xxx dt binding document on how the regulator name
is being used for binding a mc13892 regulator device.
Signed-off-by: Shawn Guo shawn@linaro.org
Cc: Samuel Ortiz sa...@linux.intel.com
Thanks, patch
The MPIC code checks for a big-endian property and sets the flag
MPIC_BIG_ENDIAN if one is present. Unfortunately, the PowerQUICC-III
compatible device-tree does not specify it, so all of the board ports
need to manually set that flag when calling mpic_alloc().
Document the flag and add it to
Hi Benoit,
On Thu, Dec 22, 2011 at 03:56:37PM +0100, Benoit Cousson wrote:
Add initial device-tree support for twl familly chips.
The current version is missing the regulator entries due
to the lack of DT regulator bindings for the moment.
Only the simple sub-modules that do not depend on
Hello.
On 12/22/2011 04:38 PM, Rob Herring wrote:
It depends upon CONFIG_OF_IRQ which not all CONFIG_OF platforms
support,
in particular sparc does not support CONFIG_OF_PLATFORM because it
precomputes all IRQs at boot time when it scans the device tree so all
of the CONFIG_OF_IRQ
Hello all,
With the following series of patches, most new MPC85xx platforms should
be able to get away with just this code (assuming updated dtb):
struct mpic *mpic = mpic_alloc(NULL, 0, 0, 0, OpenPIC);
mpic_init(mpic);
Several of the hard-coded flags can now be provided as properties in
The mpic_alloc() function takes a flags parameter and assigns it into
the mpic-flags variable fairly early on, but several later pieces of
code detect various device-tree properties and save them into the
mpic-flags variable (EG: big-endian = MPIC_BIG_ENDIAN).
Unfortunately, a number of codepaths
The MPIC code checks for a big-endian property and sets the flag
MPIC_BIG_ENDIAN if one is present, although prior to the mpic-flags
fixup that would never have worked anways.
Unfortunately, even now that it works properly, the Freescale mpic
device-node (the PowerQUICC-III-compatible one) does
The Freescale MPIC (and perhaps others in the future) is incapable of
routing non-IPI interrupts to more than once CPU at a time. Currently
all of the Freescale boards msut pass the MPIC_SINGLE_DEST_CPU flag to
mpic_alloc(), but that information should really be present in the
device-tree.
Older
The mpic-irq_count variable is only used as a software error-checking
limit to determine whether or not an IRQ number is valid. In board code
which does not manually specify an IRQ count to mpic_alloc(), i.e. 0, it
is automatically detected from the number of ISUs and the ISU size.
In practice,
The FreeScale PowerQUICC-III-compatible (mpc85xx/mpc86xx) MPICs do not
correctly report the number of hardware interrupt sources, so software
needs to override the detected value with 256.
To avoid needing to write custom board-specific code to detect that
scenario, allow it to be easily
There are two separate flags controlling whether or not the MPIC is
reset during initialization, which is completely unnecessary, and only
one of them can be specified in the device tree.
Also, most platforms in-tree right now do actually want to reset the
MPIC during initialization anyways,
Device tree bindings for the EMC tables on tegra.
Signed-off-by: Olof Johansson o...@lixom.net
Cc: Rob Herring robherri...@gmail.com
Cc: devicetree-discuss@lists.ozlabs.org
---
.../devicetree/bindings/arm/tegra/emc.txt | 100
arch/arm/boot/dts/tegra20.dtsi
Add the known i2c devices on seaboard to the i2c table.
Also rename the temperature sensor device node, and mark it as a nct1008 instead
of an adt7461 (which it is -- the chips are compatible though).
Signed-off-by: Olof Johansson o...@lixom.net
---
arch/arm/boot/dts/tegra-seaboard.dts | 29
As simple as can be right now; just one ID and no custom properties to parse.
Signed-off-by: Olof Johansson o...@lixom.net
---
drivers/staging/iio/light/isl29018.c |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/drivers/staging/iio/light/isl29018.c
Just like isl29018; trivial addition. Using both asahi-kasei,ak8975 and
the non-prefixed version (I couldn't figure out if Asahi Kasei had a
stock symbol to use, I only found numerical indexes for their stock info).
Signed-off-by: Olof Johansson o...@lixom.net
---
42 matches
Mail list logo
