All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sekhar Nori <nsekhar@ti.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
	Kevin Hilman <khilman@kernel.org>,
	Russell King <linux@armlinux.org.uk>,
	Grygorii Strashko <grygorii.strashko@ti.com>,
	"David S . Miller" <davem@davemloft.net>,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Lukas Wunner <lukas@wunner.de>, Rob Herring <robh@kernel.org>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org>,
	David Lechner <david@lechnology.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Andrew Lunn <andrew@lunn.ch>, Jonathan Corbet <corbet@lwn.net>
Cc: netdev@vger.kernel.org, linux-omap@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH v4 02/18] Documentation: nvmem: document lookup entries
Date: Mon, 16 Jul 2018 17:44:09 +0530	[thread overview]
Message-ID: <ce90989e-e548-3b16-e2ac-5f0ef81eefda@ti.com> (raw)
In-Reply-To: <20180629094039.7543-3-brgl@bgdev.pl>

On Friday 29 June 2018 03:10 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> 
> Describe the usage of nvmem cell lookup tables.
> 
> Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> ---
>  Documentation/nvmem/nvmem.txt | 28 ++++++++++++++++++++++++++++
>  1 file changed, 28 insertions(+)
> 
> diff --git a/Documentation/nvmem/nvmem.txt b/Documentation/nvmem/nvmem.txt
> index 8d8d8f58f96f..9d5e3ca2b4f3 100644
> --- a/Documentation/nvmem/nvmem.txt
> +++ b/Documentation/nvmem/nvmem.txt
> @@ -58,6 +58,34 @@ static int qfprom_probe(struct platform_device *pdev)
>  It is mandatory that the NVMEM provider has a regmap associated with its
>  struct device. Failure to do would return error code from nvmem_register().
>  
> +Additionally it is possible to create nvmem cell lookup entries and register
> +them with the nvmem framework from machine code as shown in the example below:
> +
> +static struct nvmem_cell_lookup foobar_lookup = {
> +	.info = {
> +		.name = "mac-address",
> +		.offset = 0xd000,
> +		.bytes = ERH_ALEN,

ETH_ALEN. Will fix while applying.

Regards,
Sekhar

WARNING: multiple messages have this Message-ID (diff)
From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 02/18] Documentation: nvmem: document lookup entries
Date: Mon, 16 Jul 2018 17:44:09 +0530	[thread overview]
Message-ID: <ce90989e-e548-3b16-e2ac-5f0ef81eefda@ti.com> (raw)
In-Reply-To: <20180629094039.7543-3-brgl@bgdev.pl>

On Friday 29 June 2018 03:10 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> 
> Describe the usage of nvmem cell lookup tables.
> 
> Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> ---
>  Documentation/nvmem/nvmem.txt | 28 ++++++++++++++++++++++++++++
>  1 file changed, 28 insertions(+)
> 
> diff --git a/Documentation/nvmem/nvmem.txt b/Documentation/nvmem/nvmem.txt
> index 8d8d8f58f96f..9d5e3ca2b4f3 100644
> --- a/Documentation/nvmem/nvmem.txt
> +++ b/Documentation/nvmem/nvmem.txt
> @@ -58,6 +58,34 @@ static int qfprom_probe(struct platform_device *pdev)
>  It is mandatory that the NVMEM provider has a regmap associated with its
>  struct device. Failure to do would return error code from nvmem_register().
>  
> +Additionally it is possible to create nvmem cell lookup entries and register
> +them with the nvmem framework from machine code as shown in the example below:
> +
> +static struct nvmem_cell_lookup foobar_lookup = {
> +	.info = {
> +		.name = "mac-address",
> +		.offset = 0xd000,
> +		.bytes = ERH_ALEN,

ETH_ALEN. Will fix while applying.

Regards,
Sekhar

WARNING: multiple messages have this Message-ID (diff)
From: Sekhar Nori <nsekhar@ti.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
	Kevin Hilman <khilman@kernel.org>,
	Russell King <linux@armlinux.org.uk>,
	Grygorii Strashko <grygorii.strashko@ti.com>,
	"David S . Miller" <davem@davemloft.net>,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Lukas Wunner <lukas@wunner.de>, Rob Herring <robh@kernel.org>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org>,
	David Lechner <david@lechnology.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Andrew Lunn <andrew@lunn.ch>, Jonathan Corbet <corbet@lwn.net>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>,
	<netdev@vger.kernel.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH v4 02/18] Documentation: nvmem: document lookup entries
Date: Mon, 16 Jul 2018 17:44:09 +0530	[thread overview]
Message-ID: <ce90989e-e548-3b16-e2ac-5f0ef81eefda@ti.com> (raw)
In-Reply-To: <20180629094039.7543-3-brgl@bgdev.pl>

On Friday 29 June 2018 03:10 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> 
> Describe the usage of nvmem cell lookup tables.
> 
> Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> ---
>  Documentation/nvmem/nvmem.txt | 28 ++++++++++++++++++++++++++++
>  1 file changed, 28 insertions(+)
> 
> diff --git a/Documentation/nvmem/nvmem.txt b/Documentation/nvmem/nvmem.txt
> index 8d8d8f58f96f..9d5e3ca2b4f3 100644
> --- a/Documentation/nvmem/nvmem.txt
> +++ b/Documentation/nvmem/nvmem.txt
> @@ -58,6 +58,34 @@ static int qfprom_probe(struct platform_device *pdev)
>  It is mandatory that the NVMEM provider has a regmap associated with its
>  struct device. Failure to do would return error code from nvmem_register().
>  
> +Additionally it is possible to create nvmem cell lookup entries and register
> +them with the nvmem framework from machine code as shown in the example below:
> +
> +static struct nvmem_cell_lookup foobar_lookup = {
> +	.info = {
> +		.name = "mac-address",
> +		.offset = 0xd000,
> +		.bytes = ERH_ALEN,

ETH_ALEN. Will fix while applying.

Regards,
Sekhar

  reply	other threads:[~2018-07-16 12:14 UTC|newest]

Thread overview: 98+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-29  9:40 [PATCH v4 00/18] ARM: davinci: step towards removing at24_platform_data Bartosz Golaszewski
2018-06-29  9:40 ` Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 01/18] nvmem: add support for cell lookups Bartosz Golaszewski
2018-06-29  9:40   ` Bartosz Golaszewski
2018-06-29  9:40   ` Bartosz Golaszewski
2018-07-16 12:19   ` Srinivas Kandagatla
2018-07-16 12:19     ` Srinivas Kandagatla
2018-07-16 12:20   ` Srinivas Kandagatla
2018-07-16 12:20     ` Srinivas Kandagatla
2018-06-29  9:40 ` [PATCH v4 02/18] Documentation: nvmem: document lookup entries Bartosz Golaszewski
2018-06-29  9:40   ` Bartosz Golaszewski
2018-07-16 12:14   ` Sekhar Nori [this message]
2018-07-16 12:14     ` Sekhar Nori
2018-07-16 12:14     ` Sekhar Nori
2018-07-16 12:18   ` Srinivas Kandagatla
2018-07-16 12:18     ` Srinivas Kandagatla
2018-06-29  9:40 ` [PATCH v4 03/18] ARM: davinci: dm365-evm: use nvmem lookup for mac address Bartosz Golaszewski
2018-06-29  9:40   ` Bartosz Golaszewski
2018-06-29  9:40   ` Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 04/18] ARM: davinci: dm644-evm: " Bartosz Golaszewski
2018-06-29  9:40   ` Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 05/18] ARM: davinci: dm646x-evm: " Bartosz Golaszewski
2018-06-29  9:40   ` Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 06/18] ARM: davinci: da830-evm: " Bartosz Golaszewski
2018-06-29  9:40   ` Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 07/18] ARM: davinci: mityomapl138: add nvmem cells lookup entries Bartosz Golaszewski
2018-06-29  9:40   ` Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 08/18] net: davinci_emac: potentially get the MAC address from MTD Bartosz Golaszewski
2018-06-29  9:40   ` Bartosz Golaszewski
2018-06-29 20:09   ` David Lechner
2018-06-29 20:09     ` David Lechner
2018-06-29 20:35     ` David Lechner
2018-06-29 20:35       ` David Lechner
2018-07-02  7:41       ` Bartosz Golaszewski
2018-07-02  7:41         ` Bartosz Golaszewski
2018-07-03 16:39   ` Florian Fainelli
2018-07-03 16:39     ` Florian Fainelli
2018-07-03 16:47     ` David Lechner
2018-07-03 16:47       ` David Lechner
2018-07-04  7:09     ` Ladislav Michl
2018-07-04  7:09       ` Ladislav Michl
2018-07-04  7:09       ` Ladislav Michl
2018-07-04  8:29       ` Bartosz Golaszewski
2018-07-04  8:29         ` Bartosz Golaszewski
2018-07-04  8:29         ` Bartosz Golaszewski
2018-07-04  8:29         ` Bartosz Golaszewski
2018-07-04  9:04         ` Sekhar Nori
2018-07-04  9:04           ` Sekhar Nori
2018-07-04  9:04           ` Sekhar Nori
2018-07-13 18:00           ` Bartosz Golaszewski
2018-07-13 18:00             ` Bartosz Golaszewski
2018-07-13 18:00             ` Bartosz Golaszewski
2018-07-13 18:00             ` Bartosz Golaszewski
2018-07-16  8:50             ` Sekhar Nori
2018-07-16  8:50               ` Sekhar Nori
2018-07-16  8:50               ` Sekhar Nori
2018-07-16  8:56               ` Srinivas Kandagatla
2018-07-16  8:56                 ` Srinivas Kandagatla
2018-07-16 11:57                 ` Sekhar Nori
2018-07-16 11:57                   ` Sekhar Nori
2018-07-16 11:57                   ` Sekhar Nori
2018-07-16 12:10                   ` Greg Kroah-Hartman
2018-07-16 12:10                     ` Greg Kroah-Hartman
2018-07-16 12:10                     ` Greg Kroah-Hartman
2018-07-16 12:10                     ` Greg Kroah-Hartman
2018-07-16 12:13                     ` Sekhar Nori
2018-07-16 12:13                       ` Sekhar Nori
2018-07-16 12:13                       ` Sekhar Nori
2018-07-20  5:04                 ` Sekhar Nori
2018-07-20  5:04                   ` Sekhar Nori
2018-07-20  5:04                   ` Sekhar Nori
2018-07-27  9:52                   ` Sekhar Nori
2018-07-27  9:52                     ` Sekhar Nori
2018-07-27  9:52                     ` Sekhar Nori
2018-06-29  9:40 ` [PATCH v4 09/18] ARM: davinci: da850-evm: remove dead MTD code Bartosz Golaszewski
2018-06-29  9:40   ` Bartosz Golaszewski
2018-06-29 17:09   ` David Lechner
2018-06-29 17:09     ` David Lechner
2018-07-02  7:28     ` Bartosz Golaszewski
2018-07-02  7:28       ` Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 10/18] net: davinci_emac: use nvmem to retrieve the mac address Bartosz Golaszewski
2018-06-29  9:40   ` Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 11/18] ARM: davinci: mityomapl138: don't read the MAC address from machine code Bartosz Golaszewski
2018-06-29  9:40   ` Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 12/18] ARM: davinci: dm365-evm: use device properties for at24 eeprom Bartosz Golaszewski
2018-06-29  9:40   ` Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 13/18] ARM: davinci: da830-evm: " Bartosz Golaszewski
2018-06-29  9:40   ` Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 14/18] ARM: davinci: dm644x-evm: " Bartosz Golaszewski
2018-06-29  9:40   ` Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 15/18] ARM: davinci: dm646x-evm: " Bartosz Golaszewski
2018-06-29  9:40   ` Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 16/18] ARM: davinci: sffsdr: fix the at24 eeprom device name Bartosz Golaszewski
2018-06-29  9:40   ` Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 17/18] ARM: davinci: sffsdr: use device properties for at24 eeprom Bartosz Golaszewski
2018-06-29  9:40   ` Bartosz Golaszewski
2018-06-29  9:40 ` [PATCH v4 18/18] ARM: davinci: remove dead code related to MAC address reading Bartosz Golaszewski
2018-06-29  9:40   ` Bartosz Golaszewski

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=ce90989e-e548-3b16-e2ac-5f0ef81eefda@ti.com \
    --to=nsekhar@ti.com \
    --cc=andrew@lunn.ch \
    --cc=bgolaszewski@baylibre.com \
    --cc=brgl@bgdev.pl \
    --cc=corbet@lwn.net \
    --cc=dan.carpenter@oracle.com \
    --cc=davem@davemloft.net \
    --cc=david@lechnology.com \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=grygorii.strashko@ti.com \
    --cc=ivan.khoronzhuk@linaro.org \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lukas@wunner.de \
    --cc=netdev@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=srinivas.kandagatla@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.