Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: "Ágatha Isabelle Chris Moreira Guedes" <code@agatha.dev>
Cc: linux-tegra@vger.kernel.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org, Tom Mounet <tommounet@gmail.com>,
	Julia Lawall <julia.lawall@inria.fr>,
	Marc Dietrich <marvin24@gmx.de>,
	Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [RFC] staging: nvec: cannot configure to compile driver for testing
Date: Mon, 1 Jul 2024 21:26:45 +0200	[thread overview]
Message-ID: <e4006c92-b5ff-4f28-9cf7-3f5c2a808234@gmail.com> (raw)
In-Reply-To: <yhpx2piocn5bkzaqec7mdyosb7x5zpws5l52lmx4xnejmr5xeh@6s3oe4cagcen>

On 7/1/24 04:13, Ágatha Isabelle Chris Moreira Guedes wrote:
> Hi!
> 
> On Sun, Jun 30, 2024 at 12:37:53PM GMT, Philipp Hortmann wrote:
>> 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"
> 
> Have you checked whether you have its dependencies enabled?
> 
> It seems like you have STAGING, I2C and GPIOLIB, but not ARCH_TEGRA.
> 
> Is your kernel configured for the right architecture? Are you using
> ARCH=arm environment variable? You can do this by running the command:
> 
> $ ARCH=arm make menuconfig
> 
>> In my .config file there is no string "NVEC" at all.
> 
> If it's generated by `make menuconfig` and you don't have the
> dependencies, as far as I can recall it's not supposed to have this
> string at all.
> 
>> How to config this driver to be compiled?
> 
> I haven't worked much with kernel for ARM-based SoCs, but I think as
> soon as you have your kernel properly configured for the correct
> architecture and having all dependencies met  you'll see it there. I
> just tested and it shows up for me
> 


Hi,

thanks for the hints. Here the steps I took on my x86_64:

saved my .config file.
sudo apt install gcc-aarch64-linux-gnu
export ARCH=arm64
export CROSS_COMPILE=aarch64-linux-gnu-
make defconfig
make menuconfig
	used / NVEC to find driver(s) and set them all to modules
make scripts prepare modules_prepare
make -j6
make -C . M=drivers/staging/nvec

Thanks for your support.

Bye Philipp












      reply	other threads:[~2024-07-01 19:26 UTC|newest]

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

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=e4006c92-b5ff-4f28-9cf7-3f5c2a808234@gmail.com \
    --to=philipp.g.hortmann@gmail.com \
    --cc=code@agatha.dev \
    --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