From: "Jernej Škrabec" <jernej.skrabec@siol.net>
To: u-boot@lists.denx.de
Subject: [PATCH 0/3] sunxi: Refactoring in prepration for H616
Date: Mon, 11 Jan 2021 20:37:12 +0100 [thread overview]
Message-ID: <2168420.evHQa8Gb3c@kista> (raw)
In-Reply-To: <20210111010306.6872-1-andre.przywara@arm.com>
Dne ponedeljek, 11. januar 2021 ob 02:03:03 CET je Andre Przywara napisal(a):
> Hi,
>
> I came up with those three patches to prepare for the H616.
> Patch 1 simplifies the MMC driver, so the H616 support becomes a
> one-liner.
> Patch 2 cleans up the Ethernet driver, so we can support the same
> compatible strings and fallbacks as Linux.
> Patch 3 prepares the EMAC driver for the second EMAC (100MBit + internal
> PHY). We need more code to actually use that PHY, but it's a start to
> sort out the different syscon register offset.
>
> Jernej, please feel free to include those in your H616 series, at least
> 1/3 and 2/3.
Ok, I'll pick patch 1 and 2.
Best regards,
Jernej
>
> Cheers,
> Andre
>
> Andre Przywara (3):
> mmc: sunxi: Refactor mod clock register offset
> net: sun8i-emac: Always clear syscon EPHY register
> net: sun8i-emac: Simplify EPHY offset calculation
>
> drivers/mmc/sunxi_mmc.c | 84 +++++++++++-----------------------------
> drivers/net/sun8i_emac.c | 43 ++++++++++----------
> 2 files changed, 44 insertions(+), 83 deletions(-)
>
> --
> 2.17.5
>
>
prev parent reply other threads:[~2021-01-11 19:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 1:03 [PATCH 0/3] sunxi: Refactoring in prepration for H616 Andre Przywara
2021-01-11 1:03 ` [PATCH 1/3] mmc: sunxi: Refactor mod clock register offset Andre Przywara
2021-01-11 1:33 ` Jaehoon Chung
2021-01-11 1:03 ` [PATCH 2/3] net: sun8i-emac: Always clear syscon EPHY register Andre Przywara
2021-01-11 1:03 ` [PATCH 3/3] net: sun8i-emac: Simplify EPHY offset calculation Andre Przywara
2021-01-11 19:37 ` Jernej Škrabec [this message]
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=2168420.evHQa8Gb3c@kista \
--to=jernej.skrabec@siol.net \
--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 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.