Netdev List
 help / color / mirror / Atom feed
From: Timur Tabi <timur@codeaurora.org>
To: Arnd Bergmann <arnd@arndb.de>, "David S. Miller" <davem@davemloft.net>
Cc: Hemanth Puranik <hpuranik@codeaurora.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH, net-next] qcom-emag: hide ACPI specific functions
Date: Fri, 25 May 2018 19:22:09 -0500	[thread overview]
Message-ID: <d625691f-a240-23ee-3751-d577c5e72423@codeaurora.org> (raw)
In-Reply-To: <20180525213714.2120604-1-arnd@arndb.de>

On 5/25/18 4:37 PM, Arnd Bergmann wrote:
> +#ifdef CONFIG_ACPI
>   static int emac_sgmii_irq_clear(struct emac_adapter *adpt, u8 irq_bits)
>   {
>   	struct emac_sgmii *phy = &adpt->phy;
> @@ -288,6 +289,7 @@ static struct sgmii_ops qdf2400_ops = {
>   	.link_change = emac_sgmii_common_link_change,
>   	.reset = emac_sgmii_common_reset,
>   };
> +#endif

This seems wrong.  The SGMII interrupt handler should still be viable on 
a device-tree system.  There is a DT compatibility entry for the qdf2432.

Looks like that most recent patch on net-next broke DT support, when it 
removed these lines:

-	phy->open = emac_sgmii_open;
-	phy->close = emac_sgmii_close;
-	phy->link_up = emac_sgmii_link_up;
-	phy->link_down = emac_sgmii_link_down;

I'll take it look at it next week when I'm back in the office.

-- 
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.

  reply	other threads:[~2018-05-26  0:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25 21:37 [PATCH, net-next] qcom-emag: hide ACPI specific functions Arnd Bergmann
2018-05-26  0:22 ` Timur Tabi [this message]
2018-05-27  1:30   ` Timur Tabi

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=d625691f-a240-23ee-3751-d577c5e72423@codeaurora.org \
    --to=timur@codeaurora.org \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=hpuranik@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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