lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180626064736.msxcnsi5rsnxp62k@kekkonen.localdomain>
Date:   Tue, 26 Jun 2018 09:47:36 +0300
From:   Sakari Ailus <sakari.ailus@...ux.intel.com>
To:     alanx.chiang@...el.com
Cc:     linux-i2c@...r.kernel.org, andy.yeh@...el.com,
        andriy.shevchenko@...el.com, rajmohan.mani@...el.com,
        andy.shevchenko@...il.com, brgl@...ev.pl, robh+dt@...nel.org,
        mark.rutland@....com, arnd@...db.de, gregkh@...uxfoundation.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/2] eeprom: at24: Add support for address-width
 property

Hi Alan,

On Tue, Jun 26, 2018 at 02:22:08PM +0800, alanx.chiang@...el.com wrote:
> From: "alanx.chiang" <alanx.chiang@...el.com>
> 
> Provide a flexible way to determine the addressing bits of eeprom.
> Pass the addressing bits to driver through address-width property.
> 
> Signed-off-by: Alan Chiang <alanx.chiang@...el.com>
> Signed-off-by: Andy Yeh <andy.yeh@...el.com>
> 
> ---
> since v1
> -- Add a warn message for 8-bit addressing.
> 
> ---
>  drivers/misc/eeprom/at24.c | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
> 
> diff --git a/drivers/misc/eeprom/at24.c b/drivers/misc/eeprom/at24.c
> index 0c125f2..231afcd 100644
> --- a/drivers/misc/eeprom/at24.c
> +++ b/drivers/misc/eeprom/at24.c
> @@ -478,6 +478,22 @@ static void at24_properties_to_pdata(struct device *dev,
>  	if (device_property_present(dev, "no-read-rollover"))
>  		chip->flags |= AT24_FLAG_NO_RDROL;
>  
> +	err = device_property_read_u32(dev, "address-width", &val);
> +	if (!err) {
> +		switch (val) {
> +		case 8:
> +			chip->flags &= ~AT24_FLAG_ADDR16;
> +			dev_warn(dev, "address-width is 8, clear the ADD16 bit\n");

Even though the default is 8 address bits, I don't see a need to issue a
warning if the address-width property sets that to 8 explicitly. I.e. only
warn if the flag was set.

> +			break;
> +		case 16:
> +			chip->flags |= AT24_FLAG_ADDR16;
> +			break;
> +		default:
> +			dev_warn(dev, "Bad \"address-width\" property: %u\n",
> +				 val);
> +		}
> +	}
> +
>  	err = device_property_read_u32(dev, "size", &val);
>  	if (!err)
>  		chip->byte_len = val;

-- 
Regards,

Sakari Ailus
sakari.ailus@...ux.intel.com

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ