Hi Stefan,
On Sun, Jul 2, 2017 at 1:29 AM, wrote:
> On Freitag, 30. Juni 2017 05:49:56 CEST Bin Meng wrote:
>> Hi,
>>
>> On Fri, Jun 23, 2017 at 5:54 PM, Bin Meng wrote:
>> > The only work we need do in usb_setup_descriptor() is to initialize
The Ethernet MAC used in newer Allwinner SoCs (H3, A64, H5) is about to
get an upstream Linux driver very soon (it's already lurking in -next).
This one uses a slightly different binding from the original one used
by the U-Boot driver.
The differences to the old binding are:
- The "syscon" address
Instead of open-coding the fairly generic pinmux setup in the sun8i-emac
driver, let's just use the new common implementation of that.
This has also the advantage of supporting the new, generic pinctrl bindings,
so the driver can cope with the upstream Linux DTs.
Signed-off-by: Andre Przywara
In some bindings a property points to multiple nodes, using a list of
phandles. A prominent example are UART pinctrl nodes, which use one node
to contain the RX/TX pins and another node to describe the lines used
for the hardware handshake.
The current fdtdec_lookup_phandle() helper function to
Instead of hard-coding GPIO pins used for a certain peripheral, we
should just use the pinctrl information from the DT.
The sun8i-emac driver has some simple implementation of that, so
let's just generalize this and copy the code to a more common
location.
On the way we add support for the new,
Both the BananaPi-M64 and the OrangePi-Win use the same Gigabit Ethernet
configuration as the Pine64.
Use the new generic add-on .dtsi file and have symlinks for each board
to enable TFTP boot on these boards.
Signed-off-by: Andre Przywara
---
Currently we add the U-Boot specific Ethernet MAC DT nodes for the
Pine64 via a board-specific add-on .dtsi.
However these nodes and properties in there are actually pretty generic
for all A64 boards which use a PHY connected via RGMII.
Rename the add-on .dtsi to reflect this and make the Pine64
The Ethernet MAC used in newer Allwinner SoCs (H3, A64, H5) is about to
get an upstream Linux driver very soon (it's already lurking in -next).
To support the different binding used for that, enhance our U-Boot driver
to be able to cope with both DT descriptions.
This series contains two parts:
Hi Alan,
On 07/01/2017 06:30 AM, Alan Ott wrote:
> On 06/30/2017 12:00 AM, Jaehoon Chung wrote:
>> On 06/21/2017 12:23 PM, Alan Ott wrote:
>>> Previously this driver appeared to have been half-way converted to the new
>>> driver model and did not work at all.
>>>
>>> Complete the transition to
On Sun, Jul 2, 2017 at 4:20 PM, Gautam Bhat wrote:
> This change sets the VLDO4 settings output to 2.8V in PMIC
> initialization so that the MIPI DSI/CSI input voltage is 2.8V
> as per the schematics. The original code provides an output of
> 3.3V which violates the voltage
This change sets the VLDO4 settings output to 2.8V in PMIC
initialization so that the MIPI DSI/CSI input voltage is 2.8V
as per the schematics. The original code provides an output of
3.3V which violates the voltage mentioned in the schematics.
Signed-off-by: Gautam Bhat
This change sets the VLDO4 settings output to 2.8V in PMIC
initialization. I accidentally noticed this when I was testing
the DSI voltage input which was 3.3V. Not setting the proper voltage
can harm some of the voltage sensitive peripheral.
Changes in v3:
- Used pmic_clrsetbits for consistency.
On 02/07/17 15:17, Maxime Ripard wrote:
Hi,
> On Wed, Jun 07, 2017 at 03:06:55PM +0100, Marc Zyngier wrote:
>>> If that is so fundamentally broken that this is the only benefit, I
>>> guess we might as well use some old-style SMP ops.
>>
>> Broken, for sure. Which is why I'm asking about the
On Sun, 2 Jul 2017 20:36:04 +0800
wrote:
> 在 2017-07-02 19:22,Marc Zyngier 写道:
> > On Sun, 2 Jul 2017 15:08:12 +0800
> > wrote:
> >
> >> 在 2017-06-23 21:50,Chen-Yu Tsai 写道:
> >> > On Fri, Jun 23, 2017 at 9:39 PM, wrote:
> >> >> 在
On Wed, Jun 07, 2017 at 03:06:55PM +0100, Marc Zyngier wrote:
> > If that is so fundamentally broken that this is the only benefit, I
> > guess we might as well use some old-style SMP ops.
>
> Broken, for sure. Which is why I'm asking about the benefits of running
> non-secure on something that
On Mon, Jun 26, 2017 at 07:12:50PM -0500, Grygorii Strashko wrote:
> This is a preparation required for adding Nand DM support. This series
> introduces new API get_nand_dev_by_index() to avoid direct acces to nand_info
> array and updates u-boot to use it. As result, nand_info array is made
在 2017-07-02 19:22,Marc Zyngier 写道:
On Sun, 2 Jul 2017 15:08:12 +0800
wrote:
在 2017-06-23 21:50,Chen-Yu Tsai 写道:
> On Fri, Jun 23, 2017 at 9:39 PM, wrote:
>> 在 2017-06-23 21:35,Maxime Ripard 写道:
>>>
>>> On Fri, Jun 23, 2017 at 09:24:25PM +0800,
On Sun, 2 Jul 2017 15:08:12 +0800
wrote:
> 在 2017-06-23 21:50,Chen-Yu Tsai 写道:
> > On Fri, Jun 23, 2017 at 9:39 PM, wrote:
> >> 在 2017-06-23 21:35,Maxime Ripard 写道:
> >>>
> >>> On Fri, Jun 23, 2017 at 09:24:25PM +0800, icen...@aosc.io wrote:
>
>
在 2017-06-23 21:50,Chen-Yu Tsai 写道:
On Fri, Jun 23, 2017 at 9:39 PM, wrote:
在 2017-06-23 21:35,Maxime Ripard 写道:
On Fri, Jun 23, 2017 at 09:24:25PM +0800, icen...@aosc.io wrote:
在 2017-06-07 20:51,Marc Zyngier 写道:
> On 07/06/17 13:12, Icenowy Zheng wrote:
> >
> >
> > 于
Banana Pi M3 board comes with the A83T EMAC connected to a Realtek
RTL8211E PHY, with a TX delay of 600ps.
Add the necessary DT parts and enable sun8i_emac in the defconfig.
Signed-off-by: Icenowy Zheng
---
arch/arm/dts/sun8i-a83t-sinovoip-bpi-m3.dts | 13 +
The Allwinner A83T SoC has an EMAC which is already supported by
sun8i_emac driver in U-Boot now.
Add a stub device node for it.
The device node cannot work for Linux, because it now lacks the proper
clock definition; however, it can satisfy sun8i_emac driver in U-Boot.
Signed-off-by: Icenowy
Some boards have the EMAC TX/RX lanes wired with a different length with
the clock lane, which can be workarounded by setting a TX/RX delay in
the EMAC.
This kind of delays are already defined in the newest device tree
binding of dwmac-sun8i, which has already entered linux-next.
Add support for
Sometimes the EPHY clock macros are not defined for non-H3/H5 platforms
(e.g. A83T), which makes the driver to fail to be built.
Only build the EPHY clock code when the SoC is H3/H5 by wrap them into
an #ifdef.
Signed-off-by: Icenowy Zheng
---
drivers/net/sun8i_emac.c | 2 ++
This patchset is for Allwinner A83T and Banana Pi M3's Ethernet support.
The first and third patches are for A83T -- the first one enables the
sun8i_emac driver to be built on A83T, and the third one adds a stub
DT node.
The second patch is for all EMACs supported by sun8i_emac, which sets
the
24 matches
Mail list logo