From: Serge Semin <Sergey.Semin@baikalelectronics.ru>
To: Joel Stanley <joel@jms.id.au>
Cc: Serge Semin <fancer.lancer@gmail.com>,
Wolfram Sang <wsa@the-dreams.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rob Herring <robh+dt@kernel.org>,
<devicetree-compiler@vger.kernel.org>,
David Gibson <david@gibson.dropbear.id.au>,
<linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v3 2/2] checks: Improve i2c reg property checking
Date: Tue, 2 Jun 2020 11:01:04 +0300 [thread overview]
Message-ID: <20200602080104.4vqobktck357j52v@mobilestation> (raw)
In-Reply-To: <20200528085650.1417942-3-joel@jms.id.au>
On Thu, May 28, 2020 at 06:26:50PM +0930, Joel Stanley wrote:
> The i2c bindings in the kernel tree describe support for 10 bit
> addressing, which must be indicated with the I2C_TEN_BIT_ADDRESS flag.
> When this is set the address can be up to 10 bits. When it is not set
> the address is a maximum of 7 bits.
>
> See Documentation/devicetree/bindings/i2c/i2c.txt.
>
> Take into account this flag when checking the address is valid.
>
> Signed-off-by: Joel Stanley <joel@jms.id.au>
> ---
> v2: Mask reg when checking the 10-bit size
> ---
> checks.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/checks.c b/checks.c
> index feb1721f2603..3fe979a63290 100644
> --- a/checks.c
> +++ b/checks.c
> @@ -1023,6 +1023,7 @@ static void check_i2c_bus_bridge(struct check *c, struct dt_info *dti, struct no
> WARNING(i2c_bus_bridge, check_i2c_bus_bridge, NULL, &addr_size_cells);
>
> #define I2C_OWN_SLAVE_ADDRESS (1 << 30)
> +#define I2C_TEN_BIT_ADDRESS (1 << 31)
As Andy neatly pointed out here:
https://lore.kernel.org/lkml/20200527133656.GV1634618@smile.fi.intel.com/
(1 << 31) is UB.
-Sergey
>
> static void check_i2c_bus_reg(struct check *c, struct dt_info *dti, struct node *node)
> {
> @@ -1057,10 +1058,13 @@ static void check_i2c_bus_reg(struct check *c, struct dt_info *dti, struct node
> reg = fdt32_to_cpu(*(cells++));
> /* Ignore I2C_OWN_SLAVE_ADDRESS */
> reg &= ~I2C_OWN_SLAVE_ADDRESS;
> - if (reg > 0x3ff)
> +
> + if ((reg & I2C_TEN_BIT_ADDRESS) && ((reg & ~I2C_TEN_BIT_ADDRESS) > 0x3ff))
> FAIL_PROP(c, dti, node, prop, "I2C address must be less than 10-bits, got \"0x%x\"",
> reg);
> -
> + else if (reg > 0x7f)
> + FAIL_PROP(c, dti, node, prop, "I2C address must be less than 7-bits, got \"0x%x\". Set I2C_TEN_BIT_ADDRESS for 10 bit addresses or fix the property",
> + reg);
> }
> }
> WARNING(i2c_bus_reg, check_i2c_bus_reg, NULL, ®_format, &i2c_bus_bridge);
> --
> 2.26.2
>
next prev parent reply other threads:[~2020-06-02 8:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 8:56 [PATCH v3 0/2] dtc: Improve checks for i2c reg properties Joel Stanley
2020-05-28 8:56 ` [PATCH v3 1/2] checks: Remove warning for I2C_OWN_SLAVE_ADDRESS Joel Stanley
2020-05-28 8:56 ` [PATCH v3 2/2] checks: Improve i2c reg property checking Joel Stanley
2020-06-02 8:01 ` Serge Semin [this message]
2020-06-02 8:28 ` Andy Shevchenko
2020-06-04 7:14 ` David Gibson
2020-05-29 22:33 ` [PATCH v3 0/2] dtc: Improve checks for i2c reg properties 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=20200602080104.4vqobktck357j52v@mobilestation \
--to=sergey.semin@baikalelectronics.ru \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree-compiler@vger.kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=wsa@the-dreams.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
all inboxes | Powered by JetHome®