From: <wsa@the-dreams.de>
To: Qii Wang <qii.wang@mediatek.com>
Cc: devicetree@vger.kernel.org, srv_heupstream@mediatek.com,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
linux-mediatek@lists.infradead.org, linux-i2c@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/4] add i2c support for mt8192
Date: Wed, 5 Aug 2020 23:42:42 +0200 [thread overview]
Message-ID: <20200805214242.GA2182@kunai> (raw)
In-Reply-To: <1596624742-14727-1-git-send-email-qii.wang@mediatek.com>
[-- Attachment #1.1: Type: text/plain, Size: 1461 bytes --]
On Wed, Aug 05, 2020 at 06:52:18PM +0800, Qii Wang wrote:
> This series are based on 5.8-rc1 and we provide four i2c patches
> to support mt8192 SoC.
>
> Main changes compared to v2:
> --delete unused I2C_DMA_4G_MODE
>
> Main changes compared to v1:
> --modify the commit with access more than 8GB dram
> --add Reviewed-by and Acked-by from Yingjoe, Matthias and Rob
>
> Qii Wang (4):
> i2c: mediatek: Add apdma sync in i2c driver
> i2c: mediatek: Add access to more than 8GB dram in i2c driver
> dt-bindings: i2c: update bindings for MT8192 SoC
> i2c: mediatek: Add i2c compatible for MediaTek MT8192
>
> .../devicetree/bindings/i2c/i2c-mt65xx.txt | 1 +
Applied to for-next, thanks!
Sidenote: I get these warnings when compiling the driver:
drivers/i2c/busses/i2c-mt65xx.c:267: warning: Function parameter or member 'min_low_ns' not described in 'i2c_spec_values'
drivers/i2c/busses/i2c-mt65xx.c:267: warning: Function parameter or member 'min_high_ns' not described in 'i2c_spec_values'
drivers/i2c/busses/i2c-mt65xx.c:267: warning: Function parameter or member 'min_su_sta_ns' not described in 'i2c_spec_values'
drivers/i2c/busses/i2c-mt65xx.c:267: warning: Function parameter or member 'max_hd_dat_ns' not described in 'i2c_spec_values'
drivers/i2c/busses/i2c-mt65xx.c:267: warning: Function parameter or member 'min_su_dat_ns' not described in 'i2c_spec_values'
Is someone interested to fix these?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
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:[~2020-08-05 21:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 10:52 [PATCH v3 0/4] add i2c support for mt8192 Qii Wang
2020-08-05 10:52 ` [PATCH v3 1/4] i2c: mediatek: Add apdma sync in i2c driver Qii Wang
2020-08-05 10:52 ` [PATCH v3 2/4] i2c: mediatek: Add access to more than 8GB dram " Qii Wang
2020-08-05 10:52 ` [PATCH v3 3/4] dt-bindings: i2c: update bindings for MT8192 SoC Qii Wang
2020-08-05 10:52 ` [PATCH v3 4/4] i2c: mediatek: Add i2c compatible for MediaTek MT8192 Qii Wang
2020-08-05 21:42 ` wsa [this message]
2020-08-06 6:30 ` [PATCH v3 0/4] add i2c support for mt8192 Matthias Brugger
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=20200805214242.GA2182@kunai \
--to=wsa@the-dreams.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=qii.wang@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=srv_heupstream@mediatek.com \
/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).