From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 1/1] gpio: add sloppy logic analyzer using polling
Date: Mon, 20 Dec 2021 21:01:44 +0100 [thread overview]
Message-ID: <CAMuHMdVuxfndapH2eyBVGrqqyoeA9gwrCq1zbbjdxab2DvA-MQ@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdVh60ocfzkJKz8zR1hODr8SWp=sbyHrR3KGx2ntLmuFGQ@mail.gmail.com>
On Mon, Dec 20, 2021 at 3:12 PM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
On Mon, Dec 20, 2021 at 10:07 AM Wolfram Sang
> <wsa+renesas@sang-engineering.com> wrote:
> > + [ -d "$lacpusetdir" ] || mkdir "$lacpusetdir"
> > +
> > + cur_cpu="$(cat "$lacpusetdir"/cpus)"
>
> cat: /dev/cpuset/gpio-sloppy-logic-analyzer/cpus: No such file or directory
>
> I do have a "cpuset.cpus" file.
>
> > + [ "$cur_cpu" = "$isol_cpu" ] && return
> > + [ -z "$cur_cpu" ] || fail "CPU$isol_cpu requested but CPU$cur_cpu already isolated"
> > +
> > + echo "$isol_cpu" > "$lacpusetdir"/cpus || fail "Could not isolate CPU$isol_cpu. Does it exist?"
> > + echo 1 > "$lacpusetdir"/cpu_exclusive
> > + echo 0 > "$lacpusetdir"/mems
>
> No complaint, although the real files have a "cpuset."-prefix again.
>
> [...]
>
> > +workcpu=$(cat "$lacpusetdir"/effective_cpus)
>
> cat: /dev/cpuset/gpio-sloppy-logic-analyzer/effective_cpus: No such
> file or directory
>
> I do have a "cpuset.effective_cpus" file.
>
> > +[ -n "$workcpu" ] || fail "No isolated CPU found"
> > +cpumask=$(printf '%x' $((1 << workcpu)))
> > +instance=${lasysfsdir##*/}
> > +echo "Setting up '$instance': $numsamples samples at ${samplefreq}Hz with ${triggerdat:-no} trigger using CPU$workcpu"
> > +do_capture "$cpumask" &
>
> Anyone with a clue? Thanks!
Documentation/admin-guide/cgroup-v1/cpusets.rst also has the prefixes,
so I'm wondering if you have some "legacy compatibility" config option
enabled?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2021-12-20 20:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-19 13:24 [PATCH v6 0/1] gpio: add simple logic analyzer using polling Wolfram Sang
2021-12-19 13:24 ` [PATCH v6 1/1] gpio: add sloppy " Wolfram Sang
2021-12-20 14:12 ` Geert Uytterhoeven
2021-12-20 20:01 ` Geert Uytterhoeven [this message]
2021-12-22 10:19 ` Wolfram Sang
2021-12-22 10:35 ` Geert Uytterhoeven
2021-12-22 12:58 ` Wolfram Sang
2022-01-07 17:08 ` Geert Uytterhoeven
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=CAMuHMdVuxfndapH2eyBVGrqqyoeA9gwrCq1zbbjdxab2DvA-MQ@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.