From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH] [RFC] net: smc911x: Drop the standalone EEPROM example
Date: Tue, 17 Mar 2020 19:39:49 +0100 [thread overview]
Message-ID: <53e05978-b941-08bc-18a7-6551f3cc1e88@gmail.com> (raw)
In-Reply-To: <20200317183004.GV12423@bill-the-cat>
On 3/17/20 7:30 PM, Tom Rini wrote:
> On Tue, Mar 17, 2020 at 07:23:07PM +0100, Marek Vasut wrote:
>> On 3/17/20 7:10 PM, Masahiro Yamada wrote:
>>> On Sun, Mar 15, 2020 at 8:19 AM Marek Vasut <marek.vasut@gmail.com> wrote:
>>>>
>>>> Drop the example, for two reasons. First, it is tapping directly into
>>>> the IO accessors of the SMC911x, while it should instead go through
>>>> the net device API. Second, this makes conversion of the SMC911x driver
>>>> to DM real hard.
>>>>
>>>> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
>>>> Cc: Joe Hershberger <joe.hershberger@ni.com>
>>>> Cc: Tom Rini <trini@konsulko.com>
>>>> ---
>>>> examples/standalone/Makefile | 1 -
>>>> examples/standalone/smc911x_eeprom.c | 379 ---------------------------
>>>> 2 files changed, 380 deletions(-)
>>>> delete mode 100644 examples/standalone/smc911x_eeprom.c
>>>
>>>
>>> Yeah, I was disturbed by this example code.
>>>
>>> I agree we should drop it.
>>>
>>> Reviewed-by: Masahiro Yamada <yamada.masahiro@socionext.com>
>>
>> Well I dunno. Can this be rewritten on top of DM somehow ? Do we even
>> have U-Boot application API to access DM EEPROM ?
>
> We should just drop it I think. The biggest surface we have today for
> external application is EFI application now, not U-Boot specific API.
> We can't drop the API but we don't expand it without very good reason.
But this drops the ability to access the SMC911x EEPROM too.
So maybe we need some DM EEPROM implementation in the SMC911x driver ?
Does anyone have SMC911x with an external EEPROM ?
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2020-03-17 18:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-14 23:18 [PATCH] [RFC] net: smc911x: Drop the standalone EEPROM example Marek Vasut
2020-03-17 17:45 ` Joe Hershberger
2020-03-17 18:10 ` Masahiro Yamada
2020-03-17 18:23 ` Marek Vasut
2020-03-17 18:30 ` Tom Rini
2020-03-17 18:39 ` Marek Vasut [this message]
2020-03-17 18:42 ` Tom Rini
2020-03-17 18:43 ` Marek Vasut
2020-03-17 18:44 ` Tom Rini
2020-03-17 18:53 ` Marek Vasut
2020-03-17 18:54 ` Tom Rini
[not found] ` <CANr=Z=bAAoVsFJcqDYe-9qLrqLu9X0h5e_jqeDKv5bSAP5bGnw@mail.gmail.com>
2020-03-18 0:59 ` Tom Rini
2020-03-18 1:14 ` Joe Hershberger
2020-03-18 1:16 ` Marek Vasut
2020-06-12 21:15 ` Tom Rini
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=53e05978-b941-08bc-18a7-6551f3cc1e88@gmail.com \
--to=marek.vasut@gmail.com \
--cc=u-boot@lists.denx.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