From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: "Shravan, S" <s.shravan@intel.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Mark Gross <mgross@linux.intel.com>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
"An, Sudhakar" <sudhakar.an@intel.com>
Subject: Re: [PATCH 0/1] [x86] BIOS SAR Driver for M.2 Intel Modems
Date: Tue, 15 Jun 2021 20:01:25 +0200 [thread overview]
Message-ID: <c7c3d395-826b-fc34-b396-a9c7631d981b@metux.net> (raw)
In-Reply-To: <MWHPR11MB1455D055108F1DBEA6EB9285E3319@MWHPR11MB1455.namprd11.prod.outlook.com>
On 14.06.21 13:48, Shravan, S wrote:
Hi,
> Why is it not a part of some generic subsystem under wireless network subsystem?
>
> -- This driver is instantiated only when the BIOS on given host exposes ACPI node corresponding to the BIOS SAR. This depends on support of the BIOS SAR feature by given OEM.
> -- It is agnostic of the wireless technology like WWAN, WiFi and BT. Hence, it is not made specific to any given wireless network subsystem.
>
> Please do let me know if you need more information.
the problems I see here:
1. the device uapi is very vendor specific
2. its unclear for which air interface is the data really retrieved ?
3. unclear how userland this should really handle in a generic way
--> how does it know which device to tune ?
4. does it really need to be (non-portable) ioctls ?
by the way, who hat that funny idea putting such information into acpi
in such a weird way ?
--mtx
--
---
Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert
werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren
GPG/PGP-Schlüssel zu.
---
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
next prev parent reply other threads:[~2021-06-15 18:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 3:22 [PATCH 0/1] [x86] BIOS SAR Driver for M.2 Intel Modems Shravan S
2021-04-28 3:22 ` [PATCH 1/1] [x86]: BIOS Dynamic SAR driver for Intel M.2 Modem Shravan S
2021-06-13 14:22 ` [PATCH 0/1] [x86] BIOS SAR Driver for M.2 Intel Modems Andy Shevchenko
2021-06-14 11:48 ` Shravan, S
2021-06-15 18:01 ` Enrico Weigelt, metux IT consult [this message]
2021-06-15 20:28 ` Andy Shevchenko
2021-06-23 14:03 ` Shravan, S
2021-06-28 14:07 ` Enrico Weigelt, metux IT consult
2021-06-28 15:04 ` Andy Shevchenko
2021-06-28 16:40 ` Enrico Weigelt, metux IT consult
2021-06-17 14:28 ` Hans de Goede
2021-06-17 14:36 ` Hans de Goede
2021-06-23 14:12 ` Shravan, S
2021-06-28 15:23 ` Enrico Weigelt, metux IT consult
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=c7c3d395-826b-fc34-b396-a9c7631d981b@metux.net \
--to=lkml@metux.net \
--cc=andy.shevchenko@gmail.com \
--cc=hdegoede@redhat.com \
--cc=mgross@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=s.shravan@intel.com \
--cc=sudhakar.an@intel.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.