From: jian.hu@amlogic.com (Jian Hu)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 0/2] i2c: meson: add support for Meson G12A SoC i2c controller
Date: Thu, 29 Nov 2018 19:55:43 +0800 [thread overview]
Message-ID: <b2bceaf4-92ce-92a4-c382-713d29ae3b70@amlogic.com> (raw)
In-Reply-To: <8a6a204b28523e5a181f9e85dda18fade76a26a3.camel@baylibre.com>
On 2018/11/29 19:02, Jerome Brunet wrote:
> On Thu, 2018-11-29 at 18:59 +0800, Jian Hu wrote:
>> 1)Add G12A SoC i2c compatible string in dt-bindings.
>> 2)Add compatible and data for G12A I2C controller driver.
>>
>> Jian Hu (2):
>> dt-bindings: i2c: meson: add Meson G12A SoC i2c compatible string
>> i2c: meson: add support for Meson G12A SoC I2C controller
>
> Looks to me that the g12a is compatible with the axg. What is the point of
> adding this new compatible string ?
>
I am okay if it is reasonable below in file
arch/arm64/boot/dts/amlogic/meson-g12a.dtsi. I2c controller node just
uses axg's compatible.
i2c0: i2c at 1f000 {
compatible = "amlogic,meson-axg-i2c";
reg = <0x0 0x1f000 0x0 0x20>;
interrupts = <GIC_SPI 21 IRQ_TYPE_EDGE_RISING>;
clocks = <&clkc CLKID_I2C>;
#address-cells = <1>;
#size-cells = <0>;
status = "disabled";
};
If it is, I just submit the i2c controller node in meson-g12a.dtsi.
>>
>> Documentation/devicetree/bindings/i2c/i2c-meson.txt | 1 +
>> drivers/i2c/busses/i2c-meson.c | 5 +++++
>> 2 files changed, 6 insertions(+)
>>
>
>
> .
>
next prev parent reply other threads:[~2018-11-29 11:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 10:59 [PATCH 0/2] i2c: meson: add support for Meson G12A SoC i2c controller Jian Hu
2018-11-29 10:59 ` [PATCH 1/2] dt-bindings: i2c: meson: add Meson G12A SoC i2c compatible string Jian Hu
2018-11-29 10:59 ` [PATCH 2/2] i2c: meson: add support for Meson G12A SoC I2C controller Jian Hu
2018-11-29 11:26 ` Neil Armstrong
2018-11-29 12:18 ` Jian Hu
2018-11-29 11:02 ` [PATCH 0/2] i2c: meson: add support for Meson G12A SoC i2c controller Jerome Brunet
2018-11-29 11:55 ` Jian Hu [this message]
2018-12-11 20:36 ` Wolfram Sang
2018-12-11 21:41 ` Kevin Hilman
2018-12-11 21:45 ` Wolfram Sang
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=b2bceaf4-92ce-92a4-c382-713d29ae3b70@amlogic.com \
--to=jian.hu@amlogic.com \
--cc=linus-amlogic@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 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).