From: Conor Dooley <conor@kernel.org>
To: yang tylor <tylor_yang@himax.corp-partner.google.com>
Cc: dmitry.torokhov@gmail.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
jikos@kernel.org, benjamin.tissoires@redhat.com,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
poyuan_chang@himax.corp-partner.google.com, hbarnor@chromium.org,
"jingyliang@chromium.org" <jingyliang@chromium.org>
Subject: Re: [PATCH V2 1/2] dt-bindings: input: Introduce Himax HID-over-SPI device
Date: Fri, 22 Sep 2023 16:31:15 +0100 [thread overview]
Message-ID: <20230922-removable-footwork-f1d4d96d38dd@spud> (raw)
In-Reply-To: <CAGD2q_YsFdDVhE4JCmQSGMWOdpe_yzG8-CdWYPXtjeZsManvgQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]
On Fri, Sep 22, 2023 at 05:43:54PM +0800, yang tylor wrote:
> On Fri, Sep 22, 2023 at 5:22 PM Conor Dooley <conor@kernel.org> wrote:
> >
> > On Fri, Sep 22, 2023 at 03:56:25PM +0800, yang tylor wrote:
> > > On Tue, Sep 19, 2023 at 7:09 PM Conor Dooley <conor@kernel.org> wrote:
> > > > On Tue, Sep 19, 2023 at 05:31:29PM +0800, yang tylor wrote:
> >
> > > > > The behavior of "himax,boot_time_fw_upgrade" seems not stable and
> > > > > should be removed. "himax,fw_in_flash", I use the kernel config for
> > > > > user to select.
> > > >
> > > > That seems like a bad idea, we want to be able to build one kernel that
> > > > works for all hardware at the same time.
> > > >
> > > I see, so I should take that back?
> > > I'll explain more about it.
> >
> > Are there particular ICs where the firmware would always be in flash and
> > others where it would never be? Or is this a choice made by the board or
> > system designer?
> >
> Most cases it's about the system designer's decision. But some ICs may be forced
> to use flash because of its architecture(multiple IC inside, need to
> load firmware to
> multiple IC's sram by master IC). But if there is no limitation on
> this part, most system
> designers will prefer flashless.
Forgive me if I am not understanding correctly, there are some ICs that
will need to load the firmware from flash and there are some where it
will be a decision made by the designer of the board. Is the flash part
of the IC or is it an external flash chip?
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-09-22 15:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 2:49 [PATCH V2 0/2] HID: touchscreen: add himax hid-over-spi driver Tylor Yang
2023-09-19 2:49 ` [PATCH V2 1/2] dt-bindings: input: Introduce Himax HID-over-SPI device Tylor Yang
2023-09-19 8:41 ` Conor Dooley
[not found] ` <CAGD2q_anfBP78jck6AbMNtgAggjOgaB3P6dkmq9tONHP45adFA@mail.gmail.com>
2023-09-19 11:09 ` Conor Dooley
2023-09-22 7:56 ` yang tylor
2023-09-22 9:22 ` Conor Dooley
2023-09-22 9:43 ` yang tylor
2023-09-22 15:31 ` Conor Dooley [this message]
2023-09-25 1:44 ` yang tylor
2023-09-25 8:41 ` Conor Dooley
2023-09-25 10:16 ` yang tylor
2023-09-26 9:02 ` Conor Dooley
2023-09-26 9:52 ` yang tylor
2023-09-26 12:53 ` Conor Dooley
2023-09-28 2:12 ` yang tylor
2023-09-28 16:56 ` Conor Dooley
2023-10-02 10:44 ` yang tylor
2023-10-09 17:52 ` Conor Dooley
2023-10-12 2:30 ` yang tylor
2023-10-12 15:24 ` Conor Dooley
2023-10-13 2:15 ` yang tylor
2023-09-19 18:17 ` Rob Herring
2023-09-19 2:49 ` [PATCH V2 2/2] HID: touchscreen: Add initial support for Himax HID-over-SPI Tylor Yang
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=20230922-removable-footwork-f1d4d96d38dd@spud \
--to=conor@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hbarnor@chromium.org \
--cc=jikos@kernel.org \
--cc=jingyliang@chromium.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=poyuan_chang@himax.corp-partner.google.com \
--cc=robh+dt@kernel.org \
--cc=tylor_yang@himax.corp-partner.google.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;
as well as URLs for NNTP newsgroup(s).