From: Rob Herring <robh@kernel.org>
To: Marek Vasut <marex@denx.de>
Cc: Linus Walleij <linus.walleij@linaro.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: gpio: altera-fpga-mgr: Add Altera FPGA manager GPIO bindings
Date: Wed, 17 Oct 2018 14:51:29 -0500 [thread overview]
Message-ID: <20181017195129.GA21054@bogus> (raw)
In-Reply-To: <0fcdb6a1-f9c9-5af7-64b3-141d0f80c8fb@denx.de>
On Tue, Oct 16, 2018 at 11:26:02AM +0200, Marek Vasut wrote:
> On 10/16/2018 09:37 AM, Linus Walleij wrote:
> > On Fri, Oct 12, 2018 at 5:12 PM Marek Vasut <marex@denx.de> wrote:
> >> On 10/11/2018 10:44 AM, Linus Walleij wrote:
> >>> On Wed, Oct 10, 2018 at 9:23 PM Marek Vasut <marex@denx.de> wrote:
> >>>
> >>>> Add DT bindings for the GPI / GPO block in the Altera SoCFPGA FPGA manager.
> >>>> The GPIO block in the FPGA manager has two 32bit registers, one for setting
> >>>> 32 GPOs and another one for reading 32 GPIs, both of which can be mapped to
> >>>> separate physical pads.
> >>>>
> >>>> Signed-off-by: Marek Vasut <marex@denx.de>
> >>>> Cc: Rob Herring <robh+dt@kernel.org>
> >>>> Cc: Linus Walleij <linus.walleij@linaro.org>
> >>> (...)
> >>>
> >>>> +- gpio,syscon-dev: phandle/offset pair. The phandle to syscon used to
> >>>> + access device state control registers and the offset of device's specific
> >>>> + registers within device state control registers range.
> >>> (...)
> >>>> + gpio,syscon-dev = <&fpgamgr0 0x10>;
> >>>
> >>> I didn't see that before.
> >>>
> >>> It is usually not a good idea to encode register offsets into the
> >>> device tree.
> >>>
> >>> I think the register offset should be in the driver and determined
> >>> from the compatible-string. If that is not possible, the compatible
> >>> strings do not really indicate compatibility, if you see what I mean.
> >>>
> >>> As for the name of the variable, why not just use:
> >>>
> >>> syscon = <&fpgamgr0>;
> >>>
> >>> It seems simple enough without any gpio,* prefix or explicitly
> >>> suffixing it with a "-dev" - every node in the device tree is a device
> >>> by definition so skip that.
> >>
> >> Isn't it better to just have one compatible string for all SoCFPGAs and
> >> handle the possible difference in offset where the registers are in DT?
> >> It's the same as "reg" property which we use to describe where a certain
> >> block is in the address space.
> >
> > You have a point.
> >
> > What about:
> >
> > syscon = <&fpgamgr0>;
> > reg = <0x10>;
> > ?
> >
> > You can just parse out "reg" in the driver.
> >
> > I mean reg is intuitively for that, so...
>
> But drivers/gpio/gpio-syscon.c already parses the gpio,syscon-dev
> binding, including the register offset. Why reinvent a new one if there
> already is one which fits perfectly ? :)
Maybe so, but it is undocumented. And if you look at the Rockchip
addition to the driver, it was done a different way.
Can't this be a child of the fpgamgr?
Rob
next prev parent reply other threads:[~2018-10-17 19:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 19:23 [PATCH] dt-bindings: gpio: altera-fpga-mgr: Add Altera FPGA manager GPIO bindings Marek Vasut
2018-10-11 8:44 ` Linus Walleij
2018-10-12 14:11 ` Marek Vasut
2018-10-16 7:37 ` Linus Walleij
2018-10-16 9:26 ` Marek Vasut
2018-10-17 19:51 ` Rob Herring [this message]
2018-10-17 20:21 ` Marek Vasut
2018-10-17 23:05 ` Rob Herring
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=20181017195129.GA21054@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=marex@denx.de \
/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).