All of lore.kernel.org
 help / color / mirror / Atom feed
From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: Status of gpio-pxa driver and dummy clock
Date: Sun, 04 Mar 2012 11:25:06 +0100	[thread overview]
Message-ID: <87aa3wu0hp.fsf@free.fr> (raw)
In-Reply-To: <CAN1soZwtVm=qBw97AeeysfTXhCQg7XonKkHAE_dn6EYbLHnKBw@mail.gmail.com> (Haojian Zhuang's message of "Sun, 4 Mar 2012 09:05:47 +0800")

Haojian Zhuang <haojian.zhuang@gmail.com> writes:

> On Sun, Mar 4, 2012 at 5:34 AM, Robert Jarzmik <robert.jarzmik@free.fr> wrote:
>> Hi Haojian,
>>
>> As you certainly know, Russell reverted the patch "ARM: pxa: add dummy clock for
>> sa1100-rtc", id a55b5adaf403c4d032e0871ad4ee3367782f4db6. As a consequence, the
>> dummy clock for gpio-pxa was removed, causing breakage of gpio-pxa driver.
>>
>> I wonder if you (or somebody through you) sent an update to fix the gpio-pxa by
>> either fixing gpio-pxa or adding back "pxa-gpio" clock. As of today, I see no
>> fix in 3.3-rc free (Linus tree).
>>
>
> This patch is already merged into arm-soc tree for v3.4. I don't have
> a plan to push it into
> v3.3.

Oh, you should push it to 3.3. It's a fix, and the mioa701 board is broken (and
probably many others PXA based boards too) because no GPIO is available (as
probe function of pxa-gpio always fail on clk_get()).

If you don't want to push it to 3.3, I'll have to send a fix to Arnd to fix the
breakage.

Without it, a PXA based kernel (pxa2xx) will hang in its boot phase, on the
first gpio_get_* or gpio_set_*, which is called by many drivers.

Cheers.

-- 
Robert

  reply	other threads:[~2012-03-04 10:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-03 21:34 Status of gpio-pxa driver and dummy clock Robert Jarzmik
2012-03-04  1:05 ` Haojian Zhuang
2012-03-04 10:25   ` Robert Jarzmik [this message]
2012-03-04 18:26     ` Paul Parsons
2012-03-05 12:22       ` Haojian Zhuang
2012-03-05 22:08         ` Robert Jarzmik
2012-03-05 22:48           ` Paul Parsons
2012-03-06 11:48             ` Jonathan Cameron

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=87aa3wu0hp.fsf@free.fr \
    --to=robert.jarzmik@free.fr \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.