mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Eddie James <eajames@linux.vnet.ibm.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
	linux-hwmon@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: CONFIG_SENSORS_OCC_P8_I2C
Date: Sun, 4 Dec 2022 18:55:17 +0100	[thread overview]
Message-ID: <Y4zfBRahZJ0QM758@zn.tnic> (raw)

Hi,

make oldconfig asks me here on a x86 machine about this below and it
looks like this should depend on some P8 config item so that it doesn't
show on other architectures.

Right?

Thx.

CONFIG_SENSORS_OCC_P8_I2C:

This option enables support for monitoring sensors provided by the
On-Chip Controller (OCC) on a POWER8 processor. However, this driver
can only run on a baseboard management controller (BMC) connected to
the P8, not the POWER processor itself. Communications with the OCC are
established through I2C bus.

This driver can also be built as a module. If so, the module will be
called occ-p8-hwmon.

Symbol: SENSORS_OCC_P8_I2C [=n]
Type  : tristate
Defined at drivers/hwmon/occ/Kconfig:6
  Prompt: POWER8 OCC through I2C
  Depends on: HWMON [=y] && I2C [=y]
  Location:
    -> Device Drivers
      -> Hardware Monitoring support (HWMON [=y])
        -> POWER8 OCC through I2C (SENSORS_OCC_P8_I2C [=n])
Selects: SENSORS_OCC [=n]

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

             reply	other threads:[~2022-12-04 17:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-04 17:55 Borislav Petkov [this message]
2022-12-04 18:37 ` CONFIG_SENSORS_OCC_P8_I2C Guenter Roeck
2022-12-04 19:13   ` CONFIG_SENSORS_OCC_P8_I2C Borislav Petkov
2022-12-04 21:32     ` CONFIG_SENSORS_OCC_P8_I2C Guenter Roeck
2022-12-04 22:54       ` CONFIG_SENSORS_OCC_P8_I2C Borislav Petkov

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=Y4zfBRahZJ0QM758@zn.tnic \
    --to=bp@alien8.de \
    --cc=eajames@linux.vnet.ibm.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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

all inboxes | Powered by JetHome®