linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: Andrew Lunn <andrew@lunn.ch>
Cc: linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, Jean Delvare <jdelvare@suse.com>,
	Guenter Roeck <linux@roeck-us.net>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH net-next v2 3/3] net: phy: bcm54140: add hwmon support
Date: Sun, 19 Apr 2020 18:51:33 +0200	[thread overview]
Message-ID: <4fd6d06636898560c405713eb91327e3@walle.cc> (raw)
In-Reply-To: <20200419155655.GK836632@lunn.ch>

Am 2020-04-19 17:56, schrieb Andrew Lunn:
> On Sun, Apr 19, 2020 at 12:12:49PM +0200, Michael Walle wrote:
> 
> Hi Michael
> 
> You have an #if here...
> 
>> +#if IS_ENABLED(CONFIG_HWMON)
>> +static umode_t bcm54140_hwmon_is_visible(const void *data,
>> +					 enum hwmon_sensor_types type,
>> +					 u32 attr, int channel)
>> +{
>> +	switch (type) {
>> +	case hwmon_in:
>> +		switch (attr) {
>> +		case hwmon_in_min:
>> +		case hwmon_in_max:
>> +			return 0644;
>> +		case hwmon_in_label:
>> +		case hwmon_in_input:
>> +		case hwmon_in_alarm:
>> +			return 0444;
>> +		default:
>> +			return 0;
>> +		}
>> +	case hwmon_temp:
>> +		switch (attr) {
>> +		case hwmon_temp_min:
>> +		case hwmon_temp_max:
>> +			return 0644;
>> +		case hwmon_temp_input:
>> +		case hwmon_temp_alarm:
>> +			return 0444;
>> +		default:
>> +			return 0;
>> +		}
>> +	default:
>> +		return 0;
>> +	}
>> +}
> 
> ...
> 
> 
>> +static const struct hwmon_chip_info bcm54140_chip_info = {
>> +	.ops = &bcm54140_hwmon_ops,
>> +	.info = bcm54140_hwmon_info,
>>  };
>> 
>>  static int bcm54140_phy_base_read_rdb(struct phy_device *phydev, u16 
>> rdb)
>> @@ -203,6 +522,72 @@ static int bcm54140_get_base_addr_and_port(struct 
>> phy_device *phydev)
>>  	return 0;
>>  }
> 
> 
> Still inside the #if. Some original code is now inside the #if/#endif.
> Is this correct? Hard to see from just the patch.

Whoops you're correct, something got messed up here. Will
fix that in the next version.

-michael


> 
>> 
>> +/* Check if one PHY has already done the init of the parts common to 
>> all PHYs
>> + * in the Quad PHY package.
>> + */
>> +static bool bcm54140_is_pkg_init(struct phy_device *phydev)
>> +{
>> +	struct bcm54140_phy_priv *priv = phydev->priv;
>> +	struct mii_bus *bus = phydev->mdio.bus;
>> +	int base_addr = priv->base_addr;
>> +	struct phy_device *phy;
>> +	int i;
>> +
> 
> ...
> 
>> +static int bcm54140_phy_probe_once(struct phy_device *phydev)
>> +{
>> +	struct device *hwmon;
>> +	int ret;
>> +
>> +	/* enable hardware monitoring */
>> +	ret = bcm54140_enable_monitoring(phydev);
>> +	if (ret)
>> +		return ret;
>> +
>> +	hwmon = devm_hwmon_device_register_with_info(&phydev->mdio.dev,
>> +						     "BCM54140", phydev,
>> +						     &bcm54140_chip_info,
>> +						     NULL);
>> +	return PTR_ERR_OR_ZERO(hwmon);
>> +}
>> +#endif
> 
> 
> Thanks
>   Andrew

  reply	other threads:[~2020-04-19 16:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-19 10:12 [PATCH net-next v2 1/3] net: phy: broadcom: add helper to write/read RDB registers Michael Walle
2020-04-19 10:12 ` [PATCH net-next v2 2/3] net: phy: add Broadcom BCM54140 support Michael Walle
2020-04-19 15:49   ` Andrew Lunn
2020-04-19 16:33     ` Michael Walle
2020-04-19 16:49       ` Andrew Lunn
2020-04-19 16:56         ` Michael Walle
2020-04-19 10:12 ` [PATCH net-next v2 3/3] net: phy: bcm54140: add hwmon support Michael Walle
2020-04-19 15:56   ` Andrew Lunn
2020-04-19 16:51     ` Michael Walle [this message]
2020-04-19 14:37 Guenter Roeck

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=4fd6d06636898560c405713eb91327e3@walle.cc \
    --to=michael@walle.cc \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=linux@roeck-us.net \
    --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;
as well as URLs for NNTP newsgroup(s).