From: "Vokáč Michal" <Michal.Vokac@ysoft.com>
To: Rob Herring <robh@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Andrew Lunn <andrew@lunn.ch>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Fabio Estevam <fabio.estevam@nxp.com>,
Shawn Guo <shawnguo@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] ARM: dts: imx: Add Y Soft IOTA Draco, Hydra and Ursa boards
Date: Tue, 8 Jan 2019 14:25:34 +0000 [thread overview]
Message-ID: <353b8f62-e265-c3c1-e352-d33c204eb6dc@ysoft.com> (raw)
In-Reply-To: <49371bd4-6ab9-31c3-dd48-800becac17e3@ysoft.com>
On 8.1.2019 12:43, Vokáč Michal wrote:
> On 29.12.2018 00:25, Rob Herring wrote:
>> On Tue, Dec 18, 2018 at 02:42:11PM +0000, Vokáč Michal wrote:
[...]
>>> +&i2c3 {
>>> + clock-frequency = <100000>;
>>> + pinctrl-names = "default";
>>> + pinctrl-0 = <&pinctrl_i2c3>;
>>> + status = "disabled";
>>> +
>>> + gpio_oled: gpio@41 {
>>> + compatible = "nxp,pca9536";
>>> + gpio-controller;
>>> + #gpio-cells = <2>;
>>> + reg = <0x41>;
>>> + vcc-supply = <&sw2_reg>;
>>> + status = "disabled";
>>> + };
>>> +
>>> + oled: oled@3d {
>>> + compatible = "solomon,ssd1305fb-i2c";
>>
>> Not documented.
>
> OK, I will send a separate patch for that.
Rob, I double checked that and it actually is already documented.
Not in a way that you would find the whole compatible string though..
See https://elixir.bootlin.com/linux/v5.0-rc1/source/Documentation/devicetree/bindings/display/ssd1307fb.txt#L4
Are you OK with that as it is?
Thanks,
Michal
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-08 14:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 14:42 [PATCH v2] ARM: dts: imx: Add Y Soft IOTA Draco, Hydra and Ursa boards Vokáč Michal
2018-12-28 18:20 ` Fabio Estevam
2019-01-08 11:40 ` Vokáč Michal
2018-12-28 23:25 ` Rob Herring
2019-01-08 11:43 ` Vokáč Michal
2019-01-08 14:25 ` Vokáč Michal [this message]
2019-01-08 14:53 ` Rob Herring
2019-01-08 14:56 ` Rob Herring
2019-01-08 15:00 ` Vokáč Michal
2019-01-08 16:09 ` Vokáč Michal
2019-01-08 18:11 ` Rob Herring
2019-01-10 13:57 ` Shawn Guo
2019-01-10 14:06 ` Vokáč Michal
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=353b8f62-e265-c3c1-e352-d33c204eb6dc@ysoft.com \
--to=michal.vokac@ysoft.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=shawnguo@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