linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/6] ARM: shmobile: kzm9g-reference: Add missing i2c devices
Date: Fri, 23 Jan 2015 09:57:32 +0000	[thread overview]
Message-ID: <CAMuHMdWU-dc23h244mrh5Ma9GLTppbWV6ZcZJ8bMkeCHi2g2Lg@mail.gmail.com> (raw)
In-Reply-To: <1420573329-12762-1-git-send-email-geert+renesas@glider.be>

Hi Simon,

On Fri, Jan 23, 2015 at 5:23 AM, Simon Horman <horms@verge.net.au> wrote:
> On Thu, Jan 22, 2015 at 11:53:50AM +0900, Simon Horman wrote:
>> On Thu, Jan 08, 2015 at 08:55:50AM +0900, Simon Horman wrote:
>> > On Tue, Jan 06, 2015 at 08:42:03PM +0100, Geert Uytterhoeven wrote:
>> > >   Hi Simon, Magnus,
>> > >
>> > > This patch series adds i2c devices that are supported by kzm9g-legacy
>> > > but missing on kzm9g-reference (and -multiplatform).
>> > >
>> > > The first patch ("ARM: shmobile: sh73a0 dtsi: Set control-parent for
>> > > all irqpin nodes") is a prerequisite to avoid causing an interrupt
>> > > storm when accessing the adxl345 accelerometer through
>> > > /dev/input/event1, which requires a power-cycle to recover from.
>> > >
>> > > Parts of this series and of the individual patches were written by
>> > > Laurent Pinchart.
>> > >
>> > > Thanks for applying!
>> >
>> > Thanks, done.
>>
>> For the record: Olof has asked for review comments for the BSC driver and
>> binding patches. Accordingly I have dropped them, and these patches which
>> depend on them, from next.
>>
>> This dependency may be due to the way the branches are arranged, rather
>> than actual dependencies of the code. But regardless I am dropping all
>> effected branches for now.
>
> I have now had a chance to re-examine these patches and it seems
> to me that they do not depend on the BSC driver (or anything else).
> With that in mind I have queued them up in the dt-for-v3.21 branch
> as part of renesas-devel-20150123-v3.19-rc5.
>
> Please take a moment to see if what I have done makes sense to you.

OK, Thanks!

> For reference this covers the following patches which comprised this series:
>
> Geert Uytterhoeven (4):
>   ARM: shmobile: kzm9g-reference dts: Sort i2c0 children by unit address
>   ARM: shmobile: kzm9g-reference dts: Add ak8975 magnetometer node
>   ARM: shmobile: kzm9g-reference dts: Add adxl345 accelerometer node
>   ARM: shmobile: kzm9g-reference dts: Add r2025sd rtc node
>
> Laurent Pinchart (2):
>   ARM: shmobile: sh73a0 dtsi: Set control-parent for all irqpin nodes
>   ARM: shmobile: kzm9g-reference dts: Add st1232 touchscreen node

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

      parent reply	other threads:[~2015-01-23  9:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 19:42 [PATCH 0/6] ARM: shmobile: kzm9g-reference: Add missing i2c devices Geert Uytterhoeven
2015-01-07 23:55 ` Simon Horman
2015-01-22  2:53 ` Simon Horman
2015-01-23  4:23 ` Simon Horman
2015-01-23  9:57 ` Geert Uytterhoeven [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAMuHMdWU-dc23h244mrh5Ma9GLTppbWV6ZcZJ8bMkeCHi2g2Lg@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=linux-sh@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).