From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: berlin: add GPIO nodes for the BG2Q
Date: Tue, 15 Apr 2014 14:50:14 +0200 [thread overview]
Message-ID: <534D2B06.6000408@gmail.com> (raw)
In-Reply-To: <20140415114848.GA2813@piout.net>
On 04/15/2014 01:48 PM, Alexandre Belloni wrote:
> On 15/04/2014 at 12:26:11 +0200, Sebastian Hesselbarth wrote :
>> On 04/15/2014 12:00 PM, Jisheng Zhang wrote:
>>> On Tue, 15 Apr 2014 02:23:03 -0700
>>> Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote:
>>>> I am fine with using nr-gpios property now, but I guess BG2Q also
>>>> has that CONFIG[1,2] registers to actually read out the features
>>>> synthesized in? If I find some time, I'll prepare a patch for
>>>> dw-apb-gpio to exploit that (optional) information instead of
>>>> using nr-gpios.
>>>
>>> The problem is CONFIG1/2 registers don't exist on some versions.
>>> For example, the version used in BG2/BG2CD. So nr-gpio is necessary
>>> if we want to support these versions.
>>
>> Hmm, are you sure about BG2? I remember reading it and it contains
>> sane values. Anyway, a proper patch for dw-apb-gpio would include
>> checking for sane (e.g. non-zero) values. And nr-gpios will always
>> stay as fall-back just because e.g. sunxi does not have the CONFIG
>> registers.
>
> Shouldn't that be use nr-gpios and if not available, read the CONFIG
> registers? Else, what about bogus registers ?
Probably, it is a better idea to only look for CONFIG registers if
nr-gpios is not set. Anyway, I'll really have to find more time first ;)
Sebastian
WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: "Jisheng Zhang" <jszhang@marvell.com>,
"Jimmy Xu" <zmxu@marvell.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Antoine Ténart" <antoine.tenart@free-electrons.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/2] ARM: dts: berlin: add GPIO nodes for the BG2Q
Date: Tue, 15 Apr 2014 14:50:14 +0200 [thread overview]
Message-ID: <534D2B06.6000408@gmail.com> (raw)
In-Reply-To: <20140415114848.GA2813@piout.net>
On 04/15/2014 01:48 PM, Alexandre Belloni wrote:
> On 15/04/2014 at 12:26:11 +0200, Sebastian Hesselbarth wrote :
>> On 04/15/2014 12:00 PM, Jisheng Zhang wrote:
>>> On Tue, 15 Apr 2014 02:23:03 -0700
>>> Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote:
>>>> I am fine with using nr-gpios property now, but I guess BG2Q also
>>>> has that CONFIG[1,2] registers to actually read out the features
>>>> synthesized in? If I find some time, I'll prepare a patch for
>>>> dw-apb-gpio to exploit that (optional) information instead of
>>>> using nr-gpios.
>>>
>>> The problem is CONFIG1/2 registers don't exist on some versions.
>>> For example, the version used in BG2/BG2CD. So nr-gpio is necessary
>>> if we want to support these versions.
>>
>> Hmm, are you sure about BG2? I remember reading it and it contains
>> sane values. Anyway, a proper patch for dw-apb-gpio would include
>> checking for sane (e.g. non-zero) values. And nr-gpios will always
>> stay as fall-back just because e.g. sunxi does not have the CONFIG
>> registers.
>
> Shouldn't that be use nr-gpios and if not available, read the CONFIG
> registers? Else, what about bogus registers ?
Probably, it is a better idea to only look for CONFIG registers if
nr-gpios is not set. Anyway, I'll really have to find more time first ;)
Sebastian
WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: "Jisheng Zhang" <jszhang@marvell.com>,
"Antoine Ténart" <antoine.tenart@free-electrons.com>,
"Jimmy Xu" <zmxu@marvell.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] ARM: dts: berlin: add GPIO nodes for the BG2Q
Date: Tue, 15 Apr 2014 14:50:14 +0200 [thread overview]
Message-ID: <534D2B06.6000408@gmail.com> (raw)
In-Reply-To: <20140415114848.GA2813@piout.net>
On 04/15/2014 01:48 PM, Alexandre Belloni wrote:
> On 15/04/2014 at 12:26:11 +0200, Sebastian Hesselbarth wrote :
>> On 04/15/2014 12:00 PM, Jisheng Zhang wrote:
>>> On Tue, 15 Apr 2014 02:23:03 -0700
>>> Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote:
>>>> I am fine with using nr-gpios property now, but I guess BG2Q also
>>>> has that CONFIG[1,2] registers to actually read out the features
>>>> synthesized in? If I find some time, I'll prepare a patch for
>>>> dw-apb-gpio to exploit that (optional) information instead of
>>>> using nr-gpios.
>>>
>>> The problem is CONFIG1/2 registers don't exist on some versions.
>>> For example, the version used in BG2/BG2CD. So nr-gpio is necessary
>>> if we want to support these versions.
>>
>> Hmm, are you sure about BG2? I remember reading it and it contains
>> sane values. Anyway, a proper patch for dw-apb-gpio would include
>> checking for sane (e.g. non-zero) values. And nr-gpios will always
>> stay as fall-back just because e.g. sunxi does not have the CONFIG
>> registers.
>
> Shouldn't that be use nr-gpios and if not available, read the CONFIG
> registers? Else, what about bogus registers ?
Probably, it is a better idea to only look for CONFIG registers if
nr-gpios is not set. Anyway, I'll really have to find more time first ;)
Sebastian
next prev parent reply other threads:[~2014-04-15 12:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 8:07 [PATCH 0/2] ARM: berlin: add GPIO support for the BG2Q Antoine Ténart
2014-04-15 8:07 ` Antoine Ténart
2014-04-15 8:07 ` Antoine Ténart
2014-04-15 8:07 ` [PATCH 1/2] ARM: berlin: add the LIBGPIO as a dependency " Antoine Ténart
2014-04-15 8:07 ` Antoine Ténart
2014-04-15 8:07 ` Antoine Ténart
2014-04-15 9:07 ` Jisheng Zhang
2014-04-15 9:07 ` Jisheng Zhang
2014-04-15 9:26 ` Antoine Ténart
2014-04-15 9:26 ` Antoine Ténart
2014-04-15 9:26 ` Antoine Ténart
2014-04-15 9:16 ` Sebastian Hesselbarth
2014-04-15 9:16 ` Sebastian Hesselbarth
2014-04-15 9:16 ` Sebastian Hesselbarth
2014-04-15 9:27 ` Antoine Ténart
2014-04-15 9:27 ` Antoine Ténart
2014-04-15 8:07 ` [PATCH 2/2] ARM: dts: berlin: add GPIO nodes " Antoine Ténart
2014-04-15 8:07 ` Antoine Ténart
2014-04-15 9:23 ` Sebastian Hesselbarth
2014-04-15 9:23 ` Sebastian Hesselbarth
2014-04-15 9:23 ` Sebastian Hesselbarth
2014-04-15 9:35 ` Antoine Ténart
2014-04-15 9:35 ` Antoine Ténart
2014-04-15 9:35 ` Antoine Ténart
2014-04-15 10:00 ` Jisheng Zhang
2014-04-15 10:00 ` Jisheng Zhang
2014-04-15 10:00 ` Jisheng Zhang
2014-04-15 10:26 ` Sebastian Hesselbarth
2014-04-15 10:26 ` Sebastian Hesselbarth
2014-04-15 10:26 ` Sebastian Hesselbarth
2014-04-15 11:48 ` Alexandre Belloni
2014-04-15 11:48 ` Alexandre Belloni
2014-04-15 11:48 ` Alexandre Belloni
2014-04-15 12:50 ` Sebastian Hesselbarth [this message]
2014-04-15 12:50 ` Sebastian Hesselbarth
2014-04-15 12:50 ` Sebastian Hesselbarth
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=534D2B06.6000408@gmail.com \
--to=sebastian.hesselbarth@gmail.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.