From: Rob Herring <robh@kernel.org>
To: Frank Rowand <frowand.list@gmail.com>
Cc: "Florian Fainelli" <f.fainelli@gmail.com>,
"Petr Štetiar" <ynezz@true.cz>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
"Mark Rutland" <mark.rutland@arm.com>,
"Andrew Lunn" <andrew@lunn.ch>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"John Crispin" <john@phrozen.org>, "Felix Fietkau" <nbd@nbd.name>
Subject: Re: [PATCH] of_net: add mtd-mac-address support to of_get_mac_address()
Date: Mon, 29 Apr 2019 19:48:45 -0500 [thread overview]
Message-ID: <20190430004845.GA29722@bogus> (raw)
In-Reply-To: <93770c6a-5f99-38f6-276b-316c00176cac@gmail.com>
On Tue, Apr 16, 2019 at 08:01:56PM -0700, Frank Rowand wrote:
> Hi Rob,
>
> On 4/16/19 5:29 PM, Florian Fainelli wrote:
> >
> >
> > On 16/04/2019 13:05, Petr Štetiar wrote:
> >> From: John Crispin <john@phrozen.org>
> >>
> >> Many embedded devices have information such as MAC addresses stored
> >> inside MTD devices. This patch allows us to add a property inside a node
> >> describing a network interface. The new property points at a MTD
> >> partition with an offset where the MAC address can be found.
> >>
> >> This patch has originated in OpenWrt some time ago, so in order to
> >> consider usefulness of this patch, here are some real-world numbers
> >> which hopefully speak for themselves:
> >>
> >> * mtd-mac-address used 497 times in 357 device tree files
> >> * mtd-mac-address-increment used 74 times in 58 device tree files
> >> * mtd-mac-address-increment-byte used 1 time in 1 device tree file
> >>
> >> Signed-off-by: John Crispin <john@phrozen.org>
> >> Signed-off-by: Felix Fietkau <nbd@nbd.name>
> >> [cleanup of the patch for upstream submission]
> >> Signed-off-by: Petr Štetiar <ynezz@true.cz>
> >> ---
> >
> > [snip]
> >
> >> +static const void *of_get_mac_address_mtd(struct device_node *np)
> >> +{
> >> +#ifdef CONFIG_MTD
> >> + void *addr;
> >> + size_t retlen;
> >> + int size, ret;
> >> + u8 mac[ETH_ALEN];
> >> + phandle phandle;
> >> + const char *part;
> >> + const __be32 *list;
> >> + struct mtd_info *mtd;
> >> + struct property *prop;
> >> + u32 mac_inc = 0;
> >> + u32 inc_idx = ETH_ALEN-1;
> >> + struct device_node *mtd_np = NULL;
> >
> > Reverse christmas tree would look a bit nicer here.
>
> Do we a variable declaration format preference for drivers/of/*?
We'd better get one. It's all the rage.
How about fallen Christmas tree:
int a;
bool fallen;
char christmas_tree;
int for_our;
int dt;
Rob
next prev parent reply other threads:[~2019-04-30 0:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 20:05 [PATCH] of_net: add mtd-mac-address support to of_get_mac_address() Petr Štetiar
2019-04-17 0:29 ` Florian Fainelli
2019-04-17 3:01 ` Frank Rowand
2019-04-30 0:48 ` Rob Herring [this message]
2019-04-30 1:15 ` Frank Rowand
2019-04-17 5:00 ` Heiner Kallweit
2019-04-17 8:06 ` Maxime Ripard
2019-04-17 8:06 ` Maxime Ripard
2019-04-17 9:49 ` Petr Štetiar
2019-04-17 10:15 ` Maxime Ripard
2019-04-17 10:15 ` Maxime Ripard
2019-04-17 12:10 ` Petr Štetiar
2019-04-17 16:06 ` Petr Štetiar
2019-04-17 18:05 ` Maxime Ripard
2019-04-17 18:05 ` Maxime Ripard
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=20190430004845.GA29722@bogus \
--to=robh@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=frowand.list@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=john@phrozen.org \
--cc=mark.rutland@arm.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=ynezz@true.cz \
/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.