From: grygorii.strashko@ti.com (Grygorii Strashko)
To: linux-arm-kernel@lists.infradead.org
Subject: gpio-syscon for Keystone 2 - DT bindings mismatch code expectation?
Date: Fri, 27 Mar 2015 12:21:45 +0200 [thread overview]
Message-ID: <55152F39.5090805@ti.com> (raw)
In-Reply-To: <CACRpkdYVkdLEEae8JHSsBEtMyhMx0yqN8RLhP2reoV+r5gA+JA@mail.gmail.com>
On 03/27/2015 12:12 PM, Linus Walleij wrote:
> On Mon, Mar 23, 2015 at 10:55 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
>
>> Linus, Grygorii,
>>
>> I'm trying to understand what's happening to make Keystone2 print
>> this at boot:
>>
>> gpio-syscon soc:keystone_dsp_gpio at 02620240: can't read the dir register offset!
>> gpio-syscon soc:keystone_dsp_gpio at 2620244: can't read the dir register offset!
>> gpio-syscon soc:keystone_dsp_gpio at 2620248: can't read the dir register offset!
>> gpio-syscon soc:keystone_dsp_gpio at 262024c: can't read the dir register offset!
>> gpio-syscon soc:keystone_dsp_gpio at 2620250: can't read the dir register offset!
>> gpio-syscon soc:keystone_dsp_gpio at 2620254: can't read the dir register offset!
>> gpio-syscon soc:keystone_dsp_gpio at 2620258: can't read the dir register offset!
>> gpio-syscon soc:keystone_dsp_gpio at 262025c: can't read the dir register offset!
>
> Grygorii are you looking into this?
Yes. Seems you've found the patch already )
https://lkml.org/lkml/2015/3/24/908
regards,
-grygorii
WARNING: multiple messages have this Message-ID (diff)
From: Grygorii Strashko <grygorii.strashko-l0cyMroinI0@public.gmane.org>
To: Linus Walleij
<linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Russell King - ARM Linux
<linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>
Cc: "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: gpio-syscon for Keystone 2 - DT bindings mismatch code expectation?
Date: Fri, 27 Mar 2015 12:21:45 +0200 [thread overview]
Message-ID: <55152F39.5090805@ti.com> (raw)
In-Reply-To: <CACRpkdYVkdLEEae8JHSsBEtMyhMx0yqN8RLhP2reoV+r5gA+JA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 03/27/2015 12:12 PM, Linus Walleij wrote:
> On Mon, Mar 23, 2015 at 10:55 PM, Russell King - ARM Linux
> <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org> wrote:
>
>> Linus, Grygorii,
>>
>> I'm trying to understand what's happening to make Keystone2 print
>> this at boot:
>>
>> gpio-syscon soc:keystone_dsp_gpio@02620240: can't read the dir register offset!
>> gpio-syscon soc:keystone_dsp_gpio@2620244: can't read the dir register offset!
>> gpio-syscon soc:keystone_dsp_gpio@2620248: can't read the dir register offset!
>> gpio-syscon soc:keystone_dsp_gpio@262024c: can't read the dir register offset!
>> gpio-syscon soc:keystone_dsp_gpio@2620250: can't read the dir register offset!
>> gpio-syscon soc:keystone_dsp_gpio@2620254: can't read the dir register offset!
>> gpio-syscon soc:keystone_dsp_gpio@2620258: can't read the dir register offset!
>> gpio-syscon soc:keystone_dsp_gpio@262025c: can't read the dir register offset!
>
> Grygorii are you looking into this?
Yes. Seems you've found the patch already )
https://lkml.org/lkml/2015/3/24/908
regards,
-grygorii
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-03-27 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 21:55 gpio-syscon for Keystone 2 - DT bindings mismatch code expectation? Russell King - ARM Linux
2015-03-23 21:55 ` Russell King - ARM Linux
2015-03-27 10:12 ` Linus Walleij
2015-03-27 10:12 ` Linus Walleij
2015-03-27 10:21 ` Grygorii Strashko [this message]
2015-03-27 10:21 ` Grygorii Strashko
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=55152F39.5090805@ti.com \
--to=grygorii.strashko@ti.com \
--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.