From: Jiri Slaby <jirislaby@kernel.org>
To: "József Horváth" <info@ministro.hu>,
"'Greg Kroah-Hartman'" <gregkh@linuxfoundation.org>
Cc: 'Rob Herring' <robh+dt@kernel.org>,
linux-serial@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Serial: silabs si4455 serial driver
Date: Fri, 11 Dec 2020 06:33:14 +0100 [thread overview]
Message-ID: <9615854e-3012-f22d-07bf-901a5bc7a410@kernel.org> (raw)
In-Reply-To: <20201210194625.GA17516@dincontrollerdev>
On 10. 12. 20, 20:46, József Horváth wrote:
>> Implement the basic serial driver first, and then we can talk about
>> "custom" configurations and the like, using the correct apis.
>
> Without the SI4455_IOC_SEZC call, the driver can't configure the Si4455 and not working at all.
> The cofiguration for interface is provided by user for application.
> It contains the base frequency, channel spacing, modulation, and a lot of more stuff, and generated by Silicon Labs Wireless Development Suite.
> The generated configuration is in a non public(compressed, encrypted...who knows) format, so without this the driver can't provide configuration parameters to Si4455.
request_firmware() comes to my mind then.
thanks,
--
js
suse labs
next prev parent reply other threads:[~2020-12-11 5:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 17:04 József Horváth
2020-12-10 19:03 ` 'Greg Kroah-Hartman'
2020-12-10 19:46 ` József Horváth
2020-12-11 5:33 ` Jiri Slaby [this message]
2020-12-11 5:50 ` 'Greg Kroah-Hartman'
2020-12-11 6:09 ` József Horváth
2020-12-11 6:20 ` 'Greg Kroah-Hartman'
2020-12-11 6:37 ` József Horváth
2020-12-11 7:33 ` 'Greg Kroah-Hartman'
2020-12-11 8:16 ` József Horváth
2020-12-11 8:43 ` 'Greg Kroah-Hartman'
2020-12-11 9:18 ` József Horváth
2020-12-11 12:09 ` 'Greg Kroah-Hartman'
2020-12-11 12:24 ` József Horváth
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=9615854e-3012-f22d-07bf-901a5bc7a410@kernel.org \
--to=jirislaby@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=info@ministro.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robh+dt@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
all inboxes | Powered by JetHome®