On Sat, Jun 8, 2013 at 4:50 AM, Tony Lindgren wrote:
> For wake-up events from deeper idle modes we need to check the
> configured padconf registers for the wake-up bit and then call
> the related interrupt handler.
>
> Done in collaboration with Roger Quadros .
>
> Cc: Haojian Zhuang
> Cc: Peter
On Sat, Jun 8, 2013 at 11:27 PM, Tony Lindgren wrote:
> * Haojian Zhuang [130608 02:43]:
>>
>> Manjunathappa's pinctrl-single patch on enhancing bits is already merged.
>> This patch conflicts with his patch.
>>
>> Could you rebase your patches?
>
> Sure. Looks like Linus W forgot to push out the
On Sat, Jun 8, 2013 at 4:50 AM, Tony Lindgren wrote:
> At least on omaps, each board typically has at least one device
> configured as wake-up capable from deeper idle modes. In the
> deeper idle modes the normal interrupt wake-up path won't work
> as the logic is powered off and separate wake-up
Hi Zhangfei Gao,
On Sun, Jun 09, 2013 at 10:36:42AM +0800, Zhangfei Gao wrote:
> Add support hisilicon i2c driver, which reuse designware i2c ip
>
> Signed-off-by: Zhangfei Gao
> ---
> .../devicetree/bindings/i2c/i2c-designware-hs.txt | 30 +++
> drivers/i2c/busses/Kconfig
On 06/08/2013 02:31 AM, Haojian Zhuang wrote:
> On 8 June 2013 03:18, Stephen Warren wrote:
>> On 06/06/2013 09:30 AM, Christian Ruppert wrote:
>>> On Thu, Jun 06, 2013 at 10:32:21PM +0800, Haojian Zhuang wrote:
On 6 June 2013 22:11, Christian Ruppert
wrote:
> On Wed, Jun 05, 2013
On Sat, Jun 08, 2013 at 03:38:52PM -0300, Ezequiel Garcia wrote:
> > mbus {
> >ranges = <0x012f 0 0xe800 0x800>
> >devbus-bootcs {
> >ranges = <0 0x012f 0 0x800>
> >}
> > }
> >
> > We shouldn't mangle the DT format just to make it convenient for
> > hum
Hi Jason, Arnd:
Thanks for your reviews!
I agree with most of your suggestions so far. However, I'd like to discuss
one point before we move forward with the other (imo, less importants)
issues. See below.
On Fri, Jun 07, 2013 at 02:00:54PM -0600, Jason Gunthorpe wrote:
[...]
>
>
> Is the rang
Quoting Shawn Guo (2013-06-07 20:02:41)
> On Fri, Jun 07, 2013 at 10:52:54AM -0700, Mike Turquette wrote:
> > Yes, there was a time when I was firmly against doing such a thing.
> > However I'm not sure it is so bad now. More and more SoCs are going to
> > keep getting merged into the kernel and t
On Fri, Jun 07, 2013 at 01:44:30PM -0600, Jason Gunthorpe wrote:
> On Fri, Jun 07, 2013 at 09:10:35PM +0200, Arnd Bergmann wrote:
> > On Friday 07 June 2013, Ezequiel Garcia wrote:
> > > + np = of_find_matching_node(NULL, of_mvebu_mbus_ids);
> > > + if (!np) {
> > > + pr_e
For wake-up events from deeper idle modes we need to check the
configured padconf registers for the wake-up bit and then call
the related interrupt handler.
Done in collaboration with Roger Quadros .
Cc: Haojian Zhuang
Cc: Peter Ujfalusi
Cc: devicetree-discuss@lists.ozlabs.org
Signed-off-by: Ro
* Haojian Zhuang [130608 02:43]:
>
> Manjunathappa's pinctrl-single patch on enhancing bits is already merged.
> This patch conflicts with his patch.
>
> Could you rebase your patches?
Sure. Looks like Linus W forgot to push out the branch as I don't see
it yet in the pinctrl tree. Here's a ver
On Fri, Jun 07, 2013 at 01:47:49PM -0300, Ezequiel Garcia wrote:
> These properties are not needed so it's safe to remove them.
>
> Signed-off-by: Ezequiel Garcia
> ---
> arch/arm/boot/dts/armada-370.dtsi | 4
> 1 file changed, 4 deletions(-)
Also as mentioned by Thomas, applied to mvebu/d
On Fri, Jun 07, 2013 at 01:47:38PM -0300, Ezequiel Garcia wrote:
> In order to clean message printing, we replace pr_info with pr_fmt.
> This is purely cosmetic change, with the sole purpose of making
> the code a bit more readable.
>
> Signed-off-by: Ezequiel Garcia
> ---
> drivers/bus/mvebu-mb
Hi Tushar,
On Thursday 06 of June 2013 16:32:52 Tushar Behera wrote:
> Cpufreq driver for EXYNOS4210 is not a platform driver, hence it is not
> possible to provide the regulator supply name through DT bindings.
> Since the cpufreq driver requires the regulator to be named as
> 'vdd_arm', the rela
On Thursday 06 of June 2013 16:52:28 Tushar Behera wrote:
> cpufreq driver for EXYNOS4 based SoCs are not platform drivers, hence
> we cannot currently pass the clock names through a device tree node.
> Instead, we need to make them available through a global alias.
>
> 'armclk', 'moutcore', 'mout
On 06/08/2013 04:49 PM, Alexey Brodkin wrote:
> >> + if (!priv->phy_node) {
> >> + dev_err(&pdev->dev, "failed to retrieve phy description "
> >> + "from device tree\n");
> >
> > Coalesce formats please
>
> Could you please clarify how should I format lines in question?
Hi Chander,
On Thursday 06 of June 2013 16:31:17 Chander Kashyap wrote:
> In preparation of adding support for Exynos5420, which has many
> peripherals similar to Exynos5250, a new common Exynos5 device tree
> source file is created out of the existing Exynos5250 device tree
> source file. Only th
On Sat, Jun 8, 2013 at 4:50 AM, Tony Lindgren wrote:
> Let's replace is_pinconf with flags and add struct pcs_soc so we
> can support also other features like pin wake-up events. Let's
> export the probe so the SoC specific modules can pass their
> SoC specific data to pinctrl-single if needed.
>
On 8 June 2013 03:18, Stephen Warren wrote:
> On 06/06/2013 09:30 AM, Christian Ruppert wrote:
>> On Thu, Jun 06, 2013 at 10:32:21PM +0800, Haojian Zhuang wrote:
>>> On 6 June 2013 22:11, Christian Ruppert
>>> wrote:
On Wed, Jun 05, 2013 at 09:44:27AM +0800, Haojian Zhuang wrote:
> On 3
Luke,
On Friday 07 of June 2013 22:29:34 luke.leighton wrote:
> On Fri, Jun 7, 2013 at 7:59 PM, Thomas Petazzoni
>
> wrote:
> > Maxime will reply to this in more details, but I believe the status
is:
> > * Interrupt controller is working.
> > * Clock drivers are working.
> > * Pinctrl is wor
Hi Shawn!
On Sat, Jun 08, 2013 at 12:49:47PM +0800, Shawn Guo wrote:
> On Fri, Jun 07, 2013 at 10:37:08AM +0200, Steffen Trumtrar wrote:
> > From: Markus Niebel
> >
> > Since 18 bit is supported as datawidth in device tree it should be
> > supported in driver. Beside the LDB channel the IPU chan
21 matches
Mail list logo
