netdev - Re: [RFC] net: qcom/emac: mdiobus-dev fwnode should point to emac-adev

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <17532535-1f9d-0394-b1f9-ce8de3e0d834@codeaurora.org>
Date:   Thu, 25 Jan 2018 10:05:02 -0600
From:   Timur Tabi <timur@...eaurora.org>
To:     Andrew Lunn <andrew@...n.ch>
Cc:     Wang Dongsheng <dongsheng.wang@...-semitech.com>,
        hpuranik@...eaurora.org, yu.zheng@...-semitech.com,
        netdev@...r.kernel.org, Marcin Wojtas <mw@...ihalf.com>
Subject: Re: [RFC] net: qcom/emac: mdiobus-dev fwnode should point to
 emac-adev

On 01/25/2018 09:59 AM, Andrew Lunn wrote:
> I expect we will implement something like acpi_mdiobus_register(), and
> it will take a pointer to an ACPI node. And maybe on top of
> of_mdiobus_register() and of_mdiobus_register() we will add a
> device_mdiobus_register().

Makes sense.  If you remember, please CC me on any patches.

> What i'm trying to avoid is drivers ending up with different ACPI
> bindings. If you don't want to add an ACPI node/property then no
> problems, just don't expect to be able to use any of the optional
> features of the MDIO core, like the GPIOs for reset.

Well, if a new binding is created, we will update our ACPI tables and 
drivers use it.  But we may need to keep the legacy code in emac-phy.c 
for backwards compatibility with older firmware.

-- 
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm
Technologies, Inc.  Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.