From: Tobias Junghans <tobias.junghans@inhub.de>
To: rishi gupta <gupt21@gmail.com>
Cc: "open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 2/2] HID: mcp2221: configure GP pins for GPIO function
Date: Mon, 30 Aug 2021 15:30:01 +0200 [thread overview]
Message-ID: <1931977.PIDvDuAF1L@306e6e011c15> (raw)
In-Reply-To: <CALUj-gvwPJW6qND7_8eBPLjdXe9OienMeSNu7zAgq6Q-YEitiQ@mail.gmail.com>
Hi Rishi,
Sure, this can always happen – like with any other kinds of (e.g. SoC) GPIOs
where you have to take care and/or keep track of your system's permissions
(which should prevent non-root applications from doing bad things such as
playing with GPIO settings or wiping your storage). As written, the code
changes do no harm unless you enforce it.
Best regards
Tobias
> By mistake during development it may happen or a rogue application can
> knowingly play with our hardware (commercial product may be
> vulnerable). What are your thoughts?
>
> -Rishi
>
next prev parent reply other threads:[~2021-08-30 13:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 15:27 [PATCH 1/2] HID: mcp2221: enable HID I/O during probe Tobias Junghans
2021-08-18 15:27 ` [PATCH 2/2] HID: mcp2221: configure GP pins for GPIO function Tobias Junghans
[not found] ` <CALUj-gtmN70HwzvtsO7rss0LXboFC0h9Dgfakt6UEvC_6FdAwA@mail.gmail.com>
2021-08-20 7:18 ` Tobias Junghans
2021-08-30 9:11 ` rishi gupta
2021-08-30 13:09 ` Tobias Junghans
2021-08-30 13:17 ` rishi gupta
2021-08-30 13:30 ` Tobias Junghans [this message]
2021-09-02 7:13 ` rishi gupta
2021-09-16 23:13 ` Linus Walleij
2021-09-19 10:42 ` rishi gupta
2021-09-24 17:36 ` Jim Posen
2022-04-06 15:54 ` [PATCH 1/2] HID: mcp2221: enable HID I/O during probe rishi gupta
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=1931977.PIDvDuAF1L@306e6e011c15 \
--to=tobias.junghans@inhub.de \
--cc=benjamin.tissoires@redhat.com \
--cc=gupt21@gmail.com \
--cc=jikos@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-input@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).