Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: linux-tegra@vger.kernel.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Cc: Tom Mounet <tommounet@gmail.com>,
	Julia Lawall <julia.lawall@inria.fr>,
	Marc Dietrich <marvin24@gmx.de>,
	Greg KH <gregkh@linuxfoundation.org>
Subject: [RFC] staging: nvec: cannot configure to compile driver for testing
Date: Sun, 30 Jun 2024 12:37:53 +0200	[thread overview]
Message-ID: <13cd3ec0-0f4f-4119-b2a5-f74e33e3c862@gmail.com> (raw)

Hi,

to test the patch:

[PATCH v3] staging: nvec: Use x instead of x != NULL to improve readability.
https://lore.kernel.org/linux-staging/66804898.5d0a0220.6df0f.4f0a@mx.google.com/T/#u

I would like to compile the driver nvec. But the issue I have is that I 
cannot configure to compile it.


When start make menuconfig

and search with / for NVEC I can see:

Symbol: MFD_NVEC [=n] 
                                                        Type  : tristate 
 
                                        Defined at 
drivers/staging/nvec/Kconfig:2 
                                              Prompt: NV Tegra Embedded 
Controller SMBus Interface 
                              Depends on: STAGING [=y] && I2C [=y] && 
GPIOLIB [=y] && ARCH_TEGRA 
                Location: 
 
  -> Device Drivers 
                                                      (2)   -> Staging 
drivers (STAGING [=y])
	 -> NV Tegra Embedded Controller SMBus Interface (MFD_NVEC [=n])
Selects: MFD_CORE [=y] 


But I cannot jump or go into "NV Tegra Embedded Controller SMBus Interface"

In my .config file there is no string "NVEC" at all.

How to config this driver to be compiled?

Thanks for your support.

Bye Philipp

             reply	other threads:[~2024-06-30 10:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-30 10:37 Philipp Hortmann [this message]
2024-07-01  2:13 ` [RFC] staging: nvec: cannot configure to compile driver for testing Ágatha Isabelle Chris Moreira Guedes
2024-07-01 19:26   ` Philipp Hortmann

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=13cd3ec0-0f4f-4119-b2a5-f74e33e3c862@gmail.com \
    --to=philipp.g.hortmann@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=julia.lawall@inria.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=linux-tegra@vger.kernel.org \
    --cc=marvin24@gmx.de \
    --cc=tommounet@gmail.com \
    /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