fw_cfg_showrev() is called by an indirect call in kobj_attr_show(),
which violates clang's CFI checking because fw_cfg_showrev()'s second
parameter is 'struct attribute', whereas the ->show() member of 'struct
kobj_structure' expects the second parameter to be of type 'struct
kobj_attribute'.
$ ca
From: Jan Kiszka
Add support for two Siemens SIMATIC IOT2050 variants, Basic and
Advanced. They are based on the TI AM6528 GP and AM6548 SOCs HS, thus
differ in their number of cores and availability of security features.
Furthermore the Advanced version comes with more RAM, an eMMC and a few
int
On Thu, Feb 11, 2021 at 12:50:46, Krzysztof Wilczyński
wrote:
> Hi Gustavo,
>
> [...]
> > + * Typically this function will be called by the pci driver, which passes
>
> It would be "PCI" here.
Nicely catch.
>
> > + * through argument the 'struct pci_dev *' already pointing for the device
>
On Thu, 11 Feb 2021 08:44:26 +
Christoph Hellwig wrote:
> On Tue, Feb 02, 2021 at 04:59:23PM -0700, Alex Williamson wrote:
> > vfio-pci-igd support knows very little about the device, we're
> > effectively just exposing a firmware table and some of the host bridge
> > config space (read-only)
The Surface System Aggregator Module (SSAM) subsystem provides various
functionalities, which are separated by spreading them across multiple
devices and corresponding drivers. Parts of that functionality / some of
those devices, however, can (as far as we currently know) not be
auto-detected by co
The Surface System Aggregator Module (SSAM) subsystem provides various
functionalities, which are separated by spreading them across multiple
devices and corresponding drivers. Parts of that functionality / some of
those devices, however, can (as far as we currently know) not be
auto-detected by co
The Surface Book 3 has a detachable base part. While the top part
(so-called clipboard) contains the CPU, touchscreen, and primary
battery, the base contains, among other things, a keyboard, touchpad,
and secondary battery.
Those devices do not react well to being accessed when the base part is
de
Add the detachment system (DTX) SSAM device for the Surface Book 3. This
device is accessible under the base (TC=0x11) subsystem.
Signed-off-by: Maximilian Luz
---
drivers/platform/surface/surface_aggregator_registry.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/platform/s
Add HID subsystem (TC=0x15) devices. These devices need to be registered
for 7th-generation Surface models. On previous generations, these
devices are either provided as platform devices via ACPI (Surface Laptop
1 and 2) or implemented as standard USB device.
Signed-off-by: Maximilian Luz
---
..
Add the SSAM platform profile device to the SSAM device registry. This
device is accessible under the thermal subsystem (TC=0x03) and needs to
be registered for all Surface models.
Signed-off-by: Maximilian Luz
---
.../surface/surface_aggregator_registry.c | 15 +++
1 file ch
Add battery subsystem (TC=0x02) devices (battery and AC) to the SSAM
device registry. These devices need to be registered for 7th-generation
Surface models. On 5th- and 6th-generation models, these devices are
handled via the standard ACPI battery/AC interface, which in turn
accesses the same SSAM
The lengthy timeout previously used sometimes resulted in
scheduling problems, detailed below. Therefore reduce the timeout
to 500us. This timeout selection is supported by the benchmarks
collected below with various clock dividers. This is purely the time
spent polling (reported by ktime_get()).
Quoting Lee Jones (2021-01-20 01:30:25)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/bcm/clk-iproc-pll.c:712: warning: Function parameter or member
> 'pll' not described in 'iproc_pll_sw_cfg'
>
> Cc: Michael Turquette
> Cc: Stephen Boyd
> Cc: Ray Jui
> Cc: Scott Branden
Quoting Lee Jones (2021-01-20 01:30:27)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/socfpga/clk-pll.c: In function ‘__socfpga_pll_init’:
> drivers/clk/socfpga/clk-pll.c:83:6: warning: variable ‘rc’ set but not used
> [-Wunused-but-set-variable]
>
> Cc: Dinh Nguyen
> Cc:
Quoting Lee Jones (2021-01-20 01:30:26)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/sifive/fu540-prci.h:16:35: warning: ‘prci_clk_fu540’ defined but
> not used [-Wunused-const-variable=]
> drivers/clk/sifive/fu540-prci.h:16:35: warning: ‘prci_clk_fu540’ defined but
> not
Quoting Lee Jones (2021-01-20 01:30:28)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/socfpga/clk-pll-a10.c: In function ‘__socfpga_pll_init’:
> drivers/clk/socfpga/clk-pll-a10.c:76:6: warning: variable ‘rc’ set but not
> used [-Wunused-but-set-variable]
>
> Cc: Dinh Nguye
Hi "Rafał,
I love your patch! Perhaps something to improve:
[auto build test WARNING on mtd/mtd/next]
[also build test WARNING on mtd/mtd/fixes robh/for-next v5.11-rc7 next-20210211]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we sugge
Quoting Lee Jones (2021-01-20 01:30:31)
> And remove an incorrect entry.
>
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/st/clkgen-pll.c:142: warning: cannot understand function
> prototype: 'struct clkgen_pll '
>
> Cc: Michael Turquette
> Cc: Stephen Boyd
> Cc: Stephen
Quoting Lee Jones (2021-01-20 01:30:29)
> Not much effort has been put into this one.
>
> Demote it for the time being at least.
>
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/mvebu/ap-cpu-clk.c:52: warning: Function parameter or member
> 'ratio_state_reg' not described i
Quoting Lee Jones (2021-01-20 01:30:32)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/st/clkgen-fsyn.c:186: warning: Function parameter or member
> 'data' not described in 'st_clk_quadfs_pll'
> drivers/clk/st/clkgen-fsyn.c:466: warning: Function parameter or member
> 'regs
Quoting Lee Jones (2021-01-20 01:30:35)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/ti/dpll.c:163: warning: Function parameter or member 'user' not
> described in '_register_dpll'
> drivers/clk/ti/dpll.c:163: warning: Excess function parameter 'hw'
> description in '_reg
Quoting Lee Jones (2021-01-20 01:30:33)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/ti/clockdomain.c:107: warning: Function parameter or member 'hw'
> not described in 'omap2_init_clk_clkdm'
> drivers/clk/ti/clockdomain.c:107: warning: Excess function parameter 'clk'
> d
Quoting Lee Jones (2021-01-20 01:30:36)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/ti/gate.c:67: warning: Function parameter or member 'hw' not
> described in 'omap36xx_gate_clk_enable_with_hsdiv_restore'
> drivers/clk/ti/gate.c:67: warning: Excess function parameter 'cl
Quoting Lee Jones (2021-01-20 01:30:39)
> Also demote non-worthy header to standard comment block.
>
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/versatile/clk-icst.c:53: warning: Function parameter or member
> 'map' not described in 'clk_icst'
> drivers/clk/versatile/clk
Quoting Lee Jones (2021-01-20 01:30:40)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/zynq/clkc.c: In function ‘zynq_clk_register_fclk’:
> drivers/clk/zynq/clkc.c:106:14: warning: variable ‘clk’ set but not used
> [-Wunused-but-set-variable]
> drivers/clk/zynq/clkc.c: In f
Quoting Lee Jones (2021-01-26 04:45:21)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/ti/clkt_dpll.c:284: warning: Function parameter or member 'hw'
> not described in 'omap2_dpll_round_rate'
> drivers/clk/ti/clkt_dpll.c:284: warning: Function parameter or member
> 'parent
Quoting Lee Jones (2021-01-26 04:45:20)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/zynq/pll.c:187: warning: Function parameter or member 'name' not
> described in 'clk_register_zynq_pll'
> drivers/clk/zynq/pll.c:187: warning: Function parameter or member 'parent'
> not
Quoting Lee Jones (2021-01-26 04:45:22)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/ti/dpll3xxx.c:414: warning: Function parameter or member 'hw'
> not described in 'omap3_dpll_recalc'
> drivers/clk/ti/dpll3xxx.c:414: warning: Function parameter or member
> 'parent_rate'
Kernel modules are currently only signed when CONFIG_MODULE_SIG is enabled.
The kernel module signing key is a self-signed CA only loaded onto the
.builtin_trusted_key keyring. On secure boot enabled systems with an arch
specific IMA policy enabled, but without MODULE_SIG enabled, kernel modules
a
Quoting Lee Jones (2021-01-26 04:45:23)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/qcom/clk-regmap.c:97: warning: Function parameter or member
> 'dev' not described in 'devm_clk_register_regmap'
>
> Cc: Andy Gross
> Cc: Bjorn Andersson
> Cc: Michael Turquette
> Cc: St
Loading a key on the IMA trusted keyring requires the key be signed
by an existing key on the builtin or secondary trusted keyring.
Creating a Certificate Signing Request (CSR) allows the certificate
to be self-signed or signed by a CA.
This patch generates a self-signed module signing key using C
The kernel build process currently only signs kernel modules when
MODULE_SIG is enabled. Also, sign the kernel modules at build time when
IMA_APPRAISE_MODSIG is enabled.
Signed-off-by: Nayna Jain
---
certs/Kconfig | 2 +-
init/Kconfig | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
The "mrproper" target is still looking for build time generated keys
in the old path instead of certs/ directory.
This patch fixes the path as well removes the names of the files which
are no longer generated.
Signed-off-by: Nayna Jain
Fixes: 28a68f828266 ("modsign: Use single PEM file for autoge
Certificates being loaded onto the IMA trusted keyring must be signed by
a key on either the builtin and secondary trusted keyring.
This patch creates and includes in the kernel image an ephemeral CA
key, at build time when IMA_APPRAISE_MODSIG is enabled.
Signed-off-by: Nayna Jain
---
Makefile
The kernel currently only loads the kernel module signing key onto
the builtin trusted keyring. To support IMA, load the module signing
key selectively either onto builtin or ima keyring based on MODULE_SIG
or MODULE_APPRAISE_MODSIG config respectively; and loads the CA kernel
key onto builtin trus
Quoting Lee Jones (2021-01-26 04:45:26)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/tegra/clk-tegra30.c: In function ‘tegra30_enable_cpu_clock’:
> drivers/clk/tegra/clk-tegra30.c:1107:15: warning: variable ‘reg’ set but not
> used [-Wunused-but-set-variable]
>
> Cc: Pete
On 10/02/21 12:21, Peter Zijlstra wrote:
> On Tue, Feb 09, 2021 at 08:58:15PM +, Song Bao Hua (Barry Song) wrote:
>> So historically, the code has never tried to make sched_groups result
>> in equal size. And it permits the overlapping of local group and remote
>> groups.
>
> Histrorically grou
On Wednesday 10 February 2021 11:08:59 nnet wrote:
> On Wed, Feb 10, 2021, at 10:03 AM, Pali Rohár wrote:
> > > > Hello! Could you please enable userspace governor during kernel
> > > > compilation?
> > > >
> > > > CONFIG_CPU_FREQ_GOV_USERSPACE=y
> > > >
> > > > It can be activated via comman
Quoting Lee Jones (2021-01-26 04:45:28)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/tegra/cvb.c:106: warning: Function parameter or member 'align'
> not described in 'tegra_cvb_add_opp_table'
>
> Cc: Peter De Schrijver
> Cc: Prashant Gaikwad
> Cc: Michael Turquette
> C
Quoting Lee Jones (2021-01-26 04:45:32)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/qcom/gcc-ipq4019.c: In function ‘clk_cpu_div_set_rate’:
> drivers/clk/qcom/gcc-ipq4019.c:1279:6: warning: variable ‘ret’ set but not
> used [-Wunused-but-set-variable]
>
> Cc: Andy Gross
Quoting Lee Jones (2021-01-26 04:45:29)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/ti/dpll44xx.c:114: warning: Function parameter or member 'hw'
> not described in 'omap4_dpll_regm4xen_recalc'
> drivers/clk/ti/dpll44xx.c:114: warning: Function parameter or member
> 'par
On Thu, 11 Feb 2021 17:17:42 +0100
Viktor Rosendahl wrote:
> It seems to work but I discovered during testing that it seems like newer
> kernels have a tendency to lose some latencies in longer bursts. I guess this
> is likely to be another regression in the preemptirqsoff tracer.
Not sure what
Quoting Lee Jones (2021-01-26 04:45:33)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/clk-fixed-mmio.c:62: warning: Function parameter or member
> 'pdev' not described in 'of_fixed_mmio_clk_probe'
>
> Cc: Michael Turquette
> Cc: Stephen Boyd
> Cc: Jan Kotas
> Cc: linux-.
Quoting Lee Jones (2021-01-26 04:45:34)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/clk-npcm7xx.c:438:43: warning: ‘npcm7xx_gates’ defined but not
> used [-Wunused-const-variable=]
> drivers/clk/clk-npcm7xx.c:365:48: warning: ‘npcm7xx_divs_fx’ defined but not
> used [-Wu
Quoting Lee Jones (2021-01-26 04:45:35)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/qcom/mmcc-msm8974.c:85:27: warning: ‘mmcc_xo_mmpll0_1_2_gpll0’
> defined but not used [-Wunused-const-variable=]
> drivers/clk/qcom/mmcc-msm8974.c:77:32: warning:
> ‘mmcc_xo_mmpll0_1_2_gp
/for_next next-20210211]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Sascha-Hauer/quota-Add-mountpath-b
Quoting Lee Jones (2021-01-26 04:45:37)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/qcom/clk-rpm.c:453:29: warning: ‘clk_rpm_branch_ops’ defined but
> not used [-Wunused-const-variable=]
>
> Cc: Andy Gross
> Cc: Bjorn Andersson
> Cc: Michael Turquette
> Cc: Stephen Boy
Em Thu, 11 Feb 2021 18:10:36 +
Nícolas F. R. A. Prado escreveu:
> Print warning when automarkup fails to cross-reference to another
> document, so that it doesn't fail silently.
>
> Signed-off-by: Nícolas F. R. A. Prado
> ---
>
> This patch is marked as RFC because it causes a lot of new w
Quoting Lee Jones (2021-01-26 04:45:38)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/spear/spear1310_clock.c:385:13: warning: no previous prototype
> for ‘spear1310_clk_init’ [-Wmissing-prototypes]
> drivers/clk/spear/spear1340_clock.c:442:13: warning: no previous prototyp
Quoting Lee Jones (2021-01-26 04:45:36)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/clk-xgene.c:229: warning: Function parameter or member 'mask'
> not described in 'xgene_clk_pmd'
> drivers/clk/clk-xgene.c:229: warning: Function parameter or member 'flags'
> not describ
Quoting Lee Jones (2021-01-26 04:45:40)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/zynqmp/divider.c:46: warning: Function parameter or member
> 'max_div' not described in 'zynqmp_clk_divider'
>
> Cc: Michael Turquette
> Cc: Stephen Boyd
> Cc: Michal Simek
> Cc: Rajan
This patch series is a result of running kernel crypto fuzz tests (by
enabling CONFIG_CRYPTO_MANAGER_EXTRA_TESTS) on the transformations
currently supported via the Qualcomm crypto engine on sdm845. The first
nine patches are fixes for various regressions found during testing. The
last two patches
Export and import interfaces save and restore partial transformation
states. The partial states were being stored and restored in struct
sha1_state for sha1/hmac(sha1) transformations and sha256_state for
sha256/hmac(sha256) transformations.This led to a bunch of corner cases
where improper state w
ECB transformations do not have an IV and hence set the ivsize to 0 for
ecb(aes).
Signed-off-by: Thara Gopinath
---
drivers/crypto/qce/skcipher.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/crypto/qce/skcipher.c b/drivers/crypto/qce/skcipher.c
index c2f0469ffb22..
If the available data to transfer is exactly a multiple of block size, save
the last block to be transferred in qce_ahash_final (with the last block
bit set) if this is indeed the end of data stream. If not this saved block
will be transferred as part of next update. If this block is not held back
Return unsupported if any three keys are same for DES3 algorithms
since CE does not support this and the operation causes the engine to
hang.
Signed-off-by: Thara Gopinath
---
v6->v7:
- Fixed sparse warning in patch 4 as pointed out by Herbert Xu.
This means the checking if any
The following are the conditions for requesting AES fallback cipher.
- AES-192
- AES-XTS request with len <= 512 byte (Allow messages of length
less than 512 bytes for all other AES encryption algorithms other
than AES XTS)
- AES-XTS request with len > Q
Crypto engine does not support key1 = key2 for AES XTS algorithm; the
operation hangs the engines. Return -EINVAL in case key1 and key2 are the
same.
Signed-off-by: Thara Gopinath
---
drivers/crypto/qce/skcipher.c | 19 ++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff -
Set the register REG_ENCR_XTS_DU_SIZE to cryptlen for AES XTS
transformation. Anything else causes the engine to return back
wrong results.
Acked-by: Bjorn Andersson
Signed-off-by: Thara Gopinath
---
drivers/crypto/qce/common.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff
Crypto engine BAM dma does not support 0 length data. Return unsupported
if zero length messages are passed for transformation.
Signed-off-by: Thara Gopinath
---
v5->v6:
- Return 0 for zero length messages instead of -EOPNOTSUPP in the
cipher algorithms as pointed out by Eric B
ECB/CBC encryption/decryption requires the data to be blocksize aligned.
Crypto engine hangs on non-block sized operations for these algorithms.
Return invalid data if data size is not blocksize aligned for these
algorithms.
Signed-off-by: Thara Gopinath
---
v5->v6:
- Remove the wrong TO
On Thu, 11 Feb 2021 at 22:37, Georgi Djakov wrote:
>
> The unit address of the epss_l3 node is incorrect and does not match
> the address of its "reg" property. Let's fix it.
>
> Signed-off-by: Georgi Djakov
Reviewed-by: Dmitry Baryshkov
--
With best wishes
Dmitry
src_table is unused and hence remove it from struct qce_cipher_reqctx
Signed-off-by: Thara Gopinath
---
drivers/crypto/qce/cipher.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/crypto/qce/cipher.h b/drivers/crypto/qce/cipher.h
index cffa9fc628ff..850f257d00f3 100644
--- a/drivers/c
totallen is used to get the size of the data to be transformed.
This is also available via nbytes or cryptlen in the qce_sha_reqctx
and qce_cipher_ctx. Similarly offset convey nothing for the supported
encryption and authentication transformations and is always 0.
Remove these two redundant paramet
On Wed, 2021-02-10 at 22:08 +, Pearson, Robert B wrote:
> Looks perfect. Thanks.
+1
Thanks everyone.
Hi Vincenzo,
I love your patch! Yet something to improve:
[auto build test ERROR on next-20210211]
[cannot apply to arm64/for-next/core xlnx/master arm/for-next soc/for-next
kvmarm/next linus/master hnaz-linux-mm/master v5.11-rc7 v5.11-rc6 v5.11-rc5
v5.11-rc7]
[If your patch is applied to the
On Thu, Feb 11, 2021 at 12:28 PM Masahiro Yamada wrote:
>
> On Wed, Feb 10, 2021 at 8:13 PM Viresh Kumar wrote:
> >
> > From: Rob Herring
> >
> > Add a generic rule to apply fdtoverlay in Makefile.lib, so every
> > platform doesn't need to carry the complex rule.
> >
> > The platform's Makefile
On Thu, 11 Feb 2021 at 21:11, Jonathan Marek wrote:
>
> Apply these fixes to the newly added sm8250 display ndoes
> - Use sm8250 compatibles instead of sdm845 compatibles
> - Remove "notused" interconnect (which apparently was blindly copied from
>my old patches)
> - Use dispcc node example
Quoting Adam Ford (2021-02-07 10:51:38)
> There are two registers which can set the load capacitance for
> XTAL1 and XTAL2. These are optional registers when using an
> external crystal. Since XTAL1 and XTAL2 will set to the same value,
> update the binding to support a single property called
> xt
Quoting Adam Ford (2021-02-07 10:51:39)
> There are two registers which can set the load capacitance for
> XTAL1 and XTAL2. These are optional registers when using an
> external crystal. Parse the device tree and set the
> corresponding registers accordingly.
>
> Signed-off-by: Adam Ford
> ---
On Mon, Feb 8, 2021 at 10:58 AM Enrico Weigelt, metux IT consult
wrote:
>
> Also print out the phandle ID on error message, as a debug aid.
I already have this patch applied in my tree. Why do you keep sending it?
Rob
On Thu, Feb 11, 2021 at 9:04 PM kernel test robot wrote:
>
> Hi Vincenzo,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on next-20210211]
> [cannot apply to arm64/for-next/core xlnx/master arm/for-next soc/for-next
> kvmarm/next linus/mas
In preparation to adding support for V4 DP PHY move DP functions to
callbacks at struct qmp_phy_cfg.
Signed-off-by: Dmitry Baryshkov
---
drivers/phy/qualcomm/phy-qcom-qmp.c | 438 +++-
1 file changed, 231 insertions(+), 207 deletions(-)
diff --git a/drivers/phy/qualcomm/
Hi Jonathan,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linux-next/master]
[cannot apply to robh/for-next linux/master linus/master v5.11-rc7]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--
This series adds a driver to provide platform profile support on 5th-
and later generation Microsoft Surface devices with a Surface System
Aggregator Module. On those devices, the platform profile can be used to
influence cooling behavior and power consumption.
To achieve this, a new platform prof
Add support for QMP V4 Combo USB3+DP PHY (for SM8250 platform).
Signed-off-by: Dmitry Baryshkov
---
drivers/phy/qualcomm/phy-qcom-qmp.c | 445 +---
drivers/phy/qualcomm/phy-qcom-qmp.h | 77 +++--
2 files changed, 463 insertions(+), 59 deletions(-)
diff --git a/drivers/p
The ACPI_PLATFORM_PROFILE option essentially provides a library and not
really an independent module. Thus it seems to be more user-friendly to
hide this option and simply make drivers depending on it select it.
Suggested-by: Hans de Goede
Signed-off-by: Maximilian Luz
---
drivers/acpi/Kconfig
The referenced files are named slightly different. Replace '-' with '_'
and drop the .rst ending.
Signed-off-by: Maximilian Luz
---
include/linux/platform_profile.h | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/include/linux/platform_profile.h b/include/linux/platform_
Some devices, including most Microsoft Surface devices, have a platform
profile somewhere inbetween balanced and performance. More specifically,
adding this profile allows the following mapping on Surface devices:
Vendor Name Platform Profile
-
Add a driver to provide platform profile support on 5th- and later
generation Microsoft Surface devices with a Surface System Aggregator
Module. On those devices, the platform profile can be used to influence
cooling behavior and power consumption.
For example, the default 'quiet' profile limits f
On 11/02/2021 21:39, Arnd Bergmann wrote:
On Thu, Feb 11, 2021 at 7:25 PM Grygorii Strashko
wrote:
On 08/02/2021 10:56, Luo Jiaxing wrote:
There is no need to use API with _irqsave in omap_gpio_irq_handler(),
because it already be in a irq-disabled context.
NACK.
Who said that this is alw
Quoting AngeloGioacchino Del Regno (2021-01-13 10:38:10)
> This clock is critical for any access to the GPU: gating it will
> crash the system when the GPU has been initialized (so, you cannot
> gate it unless you deinit the Adreno completely).
>
> So, to achieve a working state with GPU on, set t
Quoting AngeloGioacchino Del Regno (2021-01-13 10:38:09)
> Similarly to MSM8998, any access to the MMSS depends on this clock.
> Gating it will crash the system when RPMCC inits mmssnoc_axi_rpm_clk.
>
> Signed-off-by: AngeloGioacchino Del Regno
>
> ---
Applied to clk-next
On Thu, Feb 11, 2021 at 06:30:44PM +0100, Peter Zijlstra wrote:
> Hi,
>
> Since I had to look at instruction decoding for the stack swizzle thing, I
> ended up with a few more changes to the objtool x86 decoder.
>
> These patches are lightly tested (they build defconfig and allmodconfig using
> G
Quoting AngeloGioacchino Del Regno (2021-01-13 10:38:11)
> From: Martin Botka
>
> Add a driver for the multimedia clock controller found on SDM660
> based devices. This should allow most multimedia device drivers
> to probe and control their clocks.
>
> Signed-off-by: Martin Botka
> Co-develope
Quoting AngeloGioacchino Del Regno (2021-01-13 10:38:12)
> Document the multimedia clock controller found on SDM630/660.
>
> Signed-off-by: AngeloGioacchino Del Regno
>
> ---
Applied to clk-next
Quoting AngeloGioacchino Del Regno (2021-01-13 10:38:13)
> The function clk_gfx3d_determine_rate is selecting different PLLs
> to manage the GFX3D clock source in a special way: this one needs
> to be ping-pong'ed on different PLLs to ensure stability during
> frequency switching (set a PLL rate, l
Quoting AngeloGioacchino Del Regno (2021-01-13 10:38:14)
> In commit 734bdefdb043 ("clk: qcom: rcg2: Stop hardcoding gfx3d
> pingpong parent numbers") the gfx3d ping-pong ops (clk_gfx3d_ops)
> were generalized in order to be able to reuse the same ops for
> more than just one clock for one SoC: fol
On Tue, Feb 9, 2021 at 3:20 AM Sasha Levin wrote:
>
> On Mon, Feb 08, 2021 at 05:50:07PM +, Christoph Hellwig wrote:
> >On Sun, Feb 07, 2021 at 11:13:52AM -0500, Sasha Levin wrote:
> >> +(u8)(LINUX_VERSION_MAJOR), (u8)(LINUX_VERSION_PATCHLEVEL),
> >> +(u16)(LINUX_VERSIO
Remove module bits in the auxiliary bus code since the auxiliary bus
cannot be built as a module and the relevant code is not needed.
Cc: Dave Ertman
Suggested-by: Greg Kroah-Hartman
Signed-off-by: Dave Jiang
---
drivers/base/auxiliary.c |5 -
1 file changed, 5 deletions(-)
diff --git
Quoting AngeloGioacchino Del Regno (2021-01-13 10:38:15)
> In some rare occasions, we want to only set the RETAIN_MEM bit, but
> not the RETAIN_PERIPH one: this is seen on at least SDM630/636/660's
> GPU-GX GDSC, where unsetting and setting back the RETAIN_PERIPH bit
> will generate chaos and panic
Quoting Vinod Koul (2021-02-10 08:16:49)
> Add the GDSC found in GCC for SM8350 SoC
>
> Signed-off-by: Vinod Koul
> ---
Applied to clk-next
Quoting AngeloGioacchino Del Regno (2021-01-13 10:38:17)
> Add device tree bindings for graphics clock controller for
> Qualcomm Technology Inc's SDM630 and SDM660 SoCs.
>
> Signed-off-by: AngeloGioacchino Del Regno
>
> ---
Applied to clk-next
The pull request you sent on Thu, 11 Feb 2021 15:18:43 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git
> tags/gpio-fixes-for-v5.11
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/c05263df6c1ab82277cc3b2778b183b469a71a60
Thank you!
--
Deet-doot-
Quoting AngeloGioacchino Del Regno (2021-01-13 10:38:16)
> The GPUCC manages the clocks for the Adreno GPU found on the
> SDM630, SDM636, SDM660 SoCs.
>
> Signed-off-by: AngeloGioacchino Del Regno
>
> ---
Applied to clk-next
From: Ryan Houdek
Sorry about the noise. I obviously don't work in this ecosystem.
Didn't get any comments previously so I'm resending
The problem:
We need to support 32-bit processes running under a userspace
compatibility layer. The compatibility layer is a AArch64 process.
This means exposing
On Thu, Feb 11, 2021, at 11:55 AM, Pali Rohár wrote:
> On Wednesday 10 February 2021 11:08:59 nnet wrote:
> > On Wed, Feb 10, 2021, at 10:03 AM, Pali Rohár wrote:
> > > > > Hello! Could you please enable userspace governor during kernel
> > > > > compilation?
> > > > >
> > > > > CONFIG_CPU_FRE
On 2/11/21 11:50 AM, AngeloGioacchino Del Regno wrote:
Hey all!
This time around I thought that it would be nice to get some modem
action going on. We have it, it's working (ish), so just.. why not.
Thank you for the patches!
I would like to review these carefully but I'm sorry
I won't be abl
On 2021-02-11 11:29, Paul Moore wrote:
> On Thu, Feb 11, 2021 at 10:16 AM Phil Sutter wrote:
> > Hi,
> >
> > On Thu, Jun 04, 2020 at 09:20:49AM -0400, Richard Guy Briggs wrote:
> > > iptables, ip6tables, arptables and ebtables table registration,
> > > replacement and unregistration configuration
Hello all,
I raised this patch on #linuxfs on IRC, and I got asked if this actually
effects real programs. To demonstrate that it does, I wrote up a simple
C program which just does a table lookup of a prime number. The table is
stored sparsely, so newer versions of GCC+LD automatically put ea
401 - 500 of 1369 matches
Mail list logo
