3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Andreas Larsson
commit 07b5ab3f71d318e52c18cc3b73c1d44c908aacfa upstream.
Signed-off-by: Andreas Larsson
Signed-off-by: David S. Miller
Cc: Guenter Roeck
Signed-off-by: Greg Kroah-Hartman
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Oliver Hartkopp
commit 0aaa81377c5a01f686bcdb8c7a6929a7bf330c68 upstream.
Muyu Yu provided a POC where user root with CAP_NET_ADMIN can create a CAN
frame modification rule that makes the
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
The backport of commit afeaade90db4 "media: em28xx: make
v4l2-compliance happier by starting sequence on zero" added a
reset on em28xx_v4l2::field_count to em28xx_ctrl_notify(),
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
[It's a minimal fix for a bug that was fixed incidentally by a large
refactoring in v4.8.]
In the CTS template, when the input length is <= one block cipher block
(e.g. <= 16
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 7d033c9f6a7fd3821af75620a0257db87c2b552a ]
This patch makes sure the flow label in the IPv6 header
forged in ipv6_local_error() is initialized.
BUG: KMSAN:
Quoting Abel Vesa (2019-01-18 04:54:13)
> Before multiplying by PLL_FRAC_DENOM, the temp64 needs to be
> temp64 = rate * 2 - divfi * parent_rate * 8, instead of:
> temp64 = (rate * 2 - divfi) * parent_rate
>
> Fixes: 6209624b9a5c1e ("clk: imx: Add fractional PLL output clock")
> Signed-off-by:
Quoting Derek Basehore (2018-12-20 16:31:00)
> It's not required to traverse the entire clk tree when the parents
> array contains a NULL value. You already have the parent clk_core
> pointer, so you can just compare the parent->name and parent_names[i]
> pointers.
>
> In cases where clk names
On Thu, Jan 24, 2019 at 12:54 PM Rafael J. Wysocki wrote:
>
> On Monday, January 21, 2019 11:46:43 PM CET Sinan Kaya wrote:
> > Add BACKLIGHT_LCD_SUPPORT for ACPI_CMPC to fix the
> > warning: unmet direct dependencies detected for BACKLIGHT_CLASS_DEVICE.
> >
> > ACPI_CMPC selects
On Thu, Jan 24, 2019 at 7:57 PM Sinan Kaya wrote:
>
> Add BACKLIGHT_LCD_SUPPORT for SAMSUNG_Q10 to fix the
> warning: unmet direct dependencies detected for BACKLIGHT_CLASS_DEVICE.
>
> SAMSUNG_Q10 selects BACKLIGHT_CLASS_DEVICE but BACKLIGHT_CLASS_DEVICE
> depends on BACKLIGHT_LCD_SUPPORT.
>
>
On Thu, 24 Jan 2019, Peng Fan wrote:
> Hi stefano,
>
> > -Original Message-
> > From: Stefano Stabellini [mailto:sstabell...@kernel.org]
> > Sent: 2019年1月24日 7:44
> > To: h...@infradead.org
> > Cc: Stefano Stabellini ; Peng Fan
> > ; m...@redhat.com; jasow...@redhat.com;
> >
On Fri, Jan 25, 2019 at 5:04 AM Greg KH wrote:
>
> On Thu, Jan 24, 2019 at 06:54:15PM +, Will Deacon wrote:
> > From: Dave Airlie
> >
> > This commit is not required upstream, but is required for the 4.9.y
> > stable series.
> >
> > Upstream commit 101110f6271c ("Kbuild: always define
On Thu, 24 Jan 2019 20:01:13 +0100,
Sameer Pujar wrote:
>
>
> On 1/25/2019 12:13 AM, Takashi Iwai wrote:
> > On Thu, 24 Jan 2019 19:15:12 +0100,
> > Sameer Pujar wrote:
> >>
> >> On 1/24/2019 9:34 PM, Takashi Iwai wrote:
> >>> On Thu, 24 Jan 2019 16:57:11 +0100,
> >>> Sameer Pujar wrote:
>
Hi Joerg,
On Thu, Jan 24, 2019 at 6:42 AM Joerg Roedel wrote:
>
> Hi Diego,
>
> thanks for the report!
You're welcome, many thanks for your quick reply.
>
> On Thu, Jan 24, 2019 at 01:57:31AM -0200, Diego Viola wrote:
> > [10499.577192] WARNING: CPU: 2 PID: 3487 at arch/x86/kvm/mmu.c:2066
> >
On 1/24/19 6:17 AM, Michal Hocko wrote:
> and nr_cpus set to 4. The underlying reason is tha the device is bound
> to node 2 which doesn't have any memory and init_cpu_to_node only
> initializes memory-less nodes for possible cpus which nr_cpus restrics.
> This in turn means that proper zonelists
On Thu, 24 Jan 2019 18:36:43 +0100,
Sameer Pujar wrote:
>
> If CONFIG_PM is disabled or runtime PM calls are forbidden, the clocks
> will not be ON. This could cause issue during probe, where hda init
> setup is done. This patch checks whether runtime PM is enabled or not.
> If disabled, clocks
changes are legitimate. To move forward, maybe it's not worth spending too
much time on a grand unification of string theory, there are simpler
solutions: the Intel machine drivers already do get the platform driver name
as an platform_data argument, so we could modify the dailinks platform
On Thu, Jan 24, 2019 at 06:54:15PM +, Will Deacon wrote:
> From: Dave Airlie
>
> This commit is not required upstream, but is required for the 4.9.y
> stable series.
>
> Upstream commit 101110f6271c ("Kbuild: always define endianess in
> kconfig.h") ensures that either __LITTLE_ENDIAN or
On 1/25/2019 12:13 AM, Takashi Iwai wrote:
On Thu, 24 Jan 2019 19:15:12 +0100,
Sameer Pujar wrote:
On 1/24/2019 9:34 PM, Takashi Iwai wrote:
On Thu, 24 Jan 2019 16:57:11 +0100,
Sameer Pujar wrote:
The runtime PM count is incremented and set to active during hda codec
device init, but it is
__fls() is returning an unsigned long, but fls() and fls64() are
both returning a (signed) int.
As we need a signed int as right operand of "<<" (as Linus pointed out),
change __fls() to fls() for 32bit and also adjust masking the lowest bit
to be a signed int.
Now the 32bit and the 64bit
Dne ponedeljek, 21. januar 2019 ob 10:57:57 CET je Chen-Yu Tsai napisal(a):
> On Mon, Jan 21, 2019 at 5:50 PM Maxime Ripard
wrote:
> > Hi,
> >
> > I'm a bit late to the party, sorry for that.
> >
> > On Sat, Jan 12, 2019 at 09:56:11AM +0800, Chen-Yu Tsai wrote:
> > > On Sat, Jan 12, 2019 at
On 1/23/19 11:37 PM, Daniel Colascione wrote:
While I think there's definitely a place for eBPF as part of the
Android performance toolkit, I think most users will end up using it
through rich front-end performance collection and analysis tools (of
the sort I'm working on) rather than directly
Quoting Lubomir Rintel (2019-01-20 22:22:56)
> It seems that the kernel has no business managing this clock: once the SP
> clock is disabled, it's not sufficient to just enable it in order to bring
> the SP core back up.
>
> Pretty sure nothing ever used this and it's safe to remove.
>
> This
Quoting Dmitry Torokhov (2019-01-23 14:05:45)
> On Mon, Jan 21, 2019 at 07:22:54AM +0100, Lubomir Rintel wrote:
> > Turns out this is not such a great idea. Once the SP clock is disabled,
> > it's not sufficient to just enable in order to bring the SP core back up.
> >
> > It seems that the
From: Dave Airlie
This commit is not required upstream, but is required for the 4.9.y
stable series.
Upstream commit 101110f6271c ("Kbuild: always define endianess in
kconfig.h") ensures that either __LITTLE_ENDIAN or __BIG_ENDIAN is
defined to reflect the endianness of the target CPU
Quoting Lubomir Rintel (2019-01-20 22:22:55)
> It seems that the kernel has no business managing this clock: once the SP
> clock is disabled, it's not sufficient to just enable in order to bring the
> SP core back up. Just let the firmware keep it enabled and don't expose it
> to drivers.
>
>
Quoting Lubomir Rintel (2019-01-20 22:22:54)
> Turns out this is not such a great idea. Once the SP clock is disabled,
> it's not sufficient to just enable in order to bring the SP core back up.
>
> It seems that the kernel has no business managing this clock. Just let
> the firmware keep it
The patch
regulator: bd718x7: Constify regulator_ops
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and
The patch
regulator: bd9571mwv: Constify regulator_ops
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
By the way, why do we need to store the qh in urb->hcpriv?
qh can always be accessible through urb->ep->hcpriv
Wouldn't it be better to drop entire urb->hcpriv usage?
ср, 23 янв. 2019 г. в 20:52, Matwey V. Kornilov :
>
> We assign "urb->hcpriv = qh;" a few lines down. The valid qh for the urb is
The patch
regulator: bd70528: Constify regulator_linear_range and regulator_ops
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime
On 1/24/19 11:37 AM, Colin King wrote:
From: Colin Ian King
Don't populate the const arrays on the stack but instead make
it static. Makes the object code smaller, for example:
Before:
textdata bss dec hex filename
141078832 224 231635a7b bytcht_es8316.o
Hello RT Folks!
I'm pleased to announce the 3.18.132-rt112 stable release.
This release is just an update to the new stable 3.18.132 version
and no RT specific changes have been made.
You can get this release via the git tree at:
On Tue, Jan 22, 2019 at 08:01:15PM -0600, Pierre-Louis Bossart wrote:
> changes are legitimate. To move forward, maybe it's not worth spending too
> much time on a grand unification of string theory, there are simpler
> solutions: the Intel machine drivers already do get the platform driver name
Feiyang FY07024DI26A30-D is 1024x600, 4-lane MIPI-DSI LCD panel.
Add panel driver for it.
Signed-off-by: Jagan Teki
---
Changes for v5:
- rebase on master
- adjust the hporch values to satisfy the refresh
Changes for v4:
- use simple structure for command init
- update proper comments on power,
Feiyang FY07024DI26A30-D is 1024x600, 4-lane MIPI-DSI LCD panel.
Add dt-bingings for it.
Signed-off-by: Jagan Teki
Reviewed-by: Rob Herring
---
Changes for v4, v3:
- none
Changes for v2:
- new patch, derived from another dsi series
.../display/panel/feiyang,fy07024di26a30d.txt | 20
On Thu, 24 Jan 2019 19:15:12 +0100,
Sameer Pujar wrote:
>
>
> On 1/24/2019 9:34 PM, Takashi Iwai wrote:
> > On Thu, 24 Jan 2019 16:57:11 +0100,
> > Sameer Pujar wrote:
> >> The runtime PM count is incremented and set to active during hda codec
> >> device init, but it is decremented and set to
On Tue, Jan 22, 2019 at 08:54:59AM +, Yogesh Narayan Gaur wrote:
> Hello Mark,
>
> Can you please apply below patch in SPI tree?
> Patch has been reviewed by Boris and Frieder.
Please don't send content free pings and please allow a reasonable time
for review. People get busy, go on
Good day Mathieu,
On 1/24/2019 9:37 PM, Mathieu Poirier wrote:
Good day Sai,
On Wed, 23 Jan 2019 at 13:18, Sai Prakash Ranjan
wrote:
Hi Mathieu,
On 1/24/2019 12:44 AM, Mathieu Poirier wrote:
On Wed, 23 Jan 2019 at 05:12, Sai Prakash Ranjan
wrote:
That depends on whether the ETMs have
On Thu, Jan 24, 2019 at 11:13:29AM +0800, Wei Hu (Xavier) wrote:
>
>
> On 2019/1/24 6:40, Jason Gunthorpe wrote:
> > On Sat, Jan 19, 2019 at 11:36:06AM +0800, Wei Hu (Xavier) wrote:
> >
> >> +static int hns_roce_v2_cmd_hw_resetting(struct hns_roce_dev *hr_dev,
> >> +
On Thu, Jan 24, 2019 at 12:03:37AM -0500, Theodore Y. Ts'o wrote:
> On Thu, Jan 10, 2019 at 05:01:17PM -0800, Eric Biggers wrote:
> >
> > Indeed, Chandan Rajendra sent out a new version of the patch which fixes the
> > problem (by removing the 'select BLOCK' from fs/ubifs/Kconfig), but it never
>
ST7701 designed for small and medium sizes of TFT LCD display, is
capable of supporting up to 480RGBX864 in resolution. It provides
several system interfaces like MIPI/RGB/SPI.
Currently added support for Techstar TS8550B which is ST7701 based
480x854, 2-lane MIPI DSI LCD panel.
Driver now
Techstar TS8550B MIPI DSI panel is 480x854, 2-lane MIPI DSI LCD panel
with inbuilt ST7701 chip.
The default regulator names in ST7701 chip is renamed in Techstar TS8550B
so, add specific binding names for them.
Signed-off-by: Jagan Teki
Reviewed-by: Rob Herring
---
Changes for v8, v7:
-
On 23/01/2019 12:14, Andrew Murray wrote:
[...]
+static inline void smmu_pmu_counter_set_value(struct smmu_pmu
*smmu_pmu,
+ u32 idx, u64 value)
+{
+ if (smmu_pmu->counter_mask & BIT(32))
+ writeq(value, smmu_pmu->reloc_base +
On Thu, Jan 24, 2019 at 01:07:58PM -0500, Sven Van Asbroeck wrote:
> On Tue, Jan 22, 2019 at 1:52 PM Greg KH wrote:
> >
> > SPDX "GPL-2.0+" please.
> >
> > > would be if this code was derived from v2-only code that can't be
> > > relicensed anymore.
> >
> > Are you _sure_ you want v2+? I ask as
On 1/24/2019 9:37 PM, Marc Gonzalez wrote:
On 23/01/2019 21:17, Sai Prakash Ranjan wrote:
On 1/24/2019 12:44 AM, Mathieu Poirier wrote:
What version of the Kryo CPU?
There is no Kryo version for MSM8996 (its only given as Kryo), MSM8998
onwards we have Kryo versions like Kryo 280 and so
On Thu, Jan 24, 2019 at 06:01:17PM +0100, Michal Hocko wrote:
> On Thu 24-01-19 11:00:10, Johannes Weiner wrote:
> [...]
> > We cannot fully eliminate a risk for regression, but it strikes me as
> > highly unlikely, given the extremely young age of cgroup2-based system
> > management and
Hello,
syzbot found the following crash on:
HEAD commit:30bac164aca7 Revert "Change mincore() to count "mapped" pa..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17b824c0c0
kernel config: https://syzkaller.appspot.com/x/.config?x=505743eba4e4f68
Hi Suzuki,
On 1/24/2019 4:49 PM, Suzuki K Poulose wrote:
Hi Sai,
That looks fine with me. But as Mathieu said, this needs to be a separate
patch. But before all that please could you provide me the PIDR4 value for
the Kryo A75 and A55 please ?
Sure.
PIDR4 value is 0x4.
I get it now. So
On Thu, Jan 24, 2019 at 05:23:59PM +0800, Herbert Xu wrote:
> On Thu, Jan 24, 2019 at 09:50:35AM +0100, Ard Biesheuvel wrote:
> >
> > Thanks for yet another round of cleanup
> >
> > I'll look into these, but I'd like to clarify one thing first.
> >
> > IIUC, you are trying to deal with the case
__fls() is returning an unsigned long, but fls() and fls64() are
both returning a (signed) int.
As we need a signed int as right operand of "<<" (as Linus pointed out),
change __fls() to fls() for 32bit and also adjust masking the lowest bit
to be a signed int.
Now the 32bit and the 64bit
On Thu, Jan 24, 2019 at 02:03:06PM +0100, v...@amazon.com wrote:
> diff --git a/fs/devpts/inode.c b/fs/devpts/inode.c
> index c538145..553a3f3 100644
> --- a/fs/devpts/inode.c
> +++ b/fs/devpts/inode.c
> @@ -455,6 +455,7 @@ devpts_fill_super(struct super_block *s, void *data, int
> silent)
>
On Thu, 2019-01-24 at 19:14 +0100, Mathieu Malaterre wrote:
> > I'm not sure this will work on all platforms, didn't something like
> > alpha pad out u8's to u32 when not requiring packing?
>
> I was not aware of that.
TBH, I'm not actually sure about that. Pure hearsay. If anyone knows,
I'd
During refactor in commit 9e478066eae4 ("mac80211: fix MU-MIMO
follow-MAC mode") a new struct 'action' was declared with packed
attribute as:
struct {
struct ieee80211_hdr_3addr hdr;
u8 category;
u8 action_code;
} __packed action;
But since struct
On 1/24/19 3:31 PM, Andy Shevchenko wrote:
There are new types and helpers that are supposed to be used in new code.
As a preparation to get rid of legacy types and API functions do
the conversion here.
Signed-off-by: Andy Shevchenko
---
v2:
- convert instance_uuid to guid_t and get rid of
On 1/24/2019 9:34 PM, Takashi Iwai wrote:
On Thu, 24 Jan 2019 16:57:11 +0100,
Sameer Pujar wrote:
The runtime PM count is incremented and set to active during hda codec
device init, but it is decremented and set to suspend during exit only.
Hence the runtime PM status is always active and hda
On Thu, Jan 24, 2019 at 7:08 PM Johannes Berg wrote:
>
> On Thu, 2019-01-24 at 19:05 +0100, Mathieu Malaterre wrote:
> > During refactor in commit 9e478066eae4 ("mac80211: fix MU-MIMO
> > follow-MAC mode") a new struct 'action' was declared with packed
> > attribute as:
> >
> > struct {
> >
The rcu_qs is disabling IRQs by self so no need to do the same in raise_softirq
but instead we can save some cycles using raise_softirq_irqoff directly.
CC: Paul E. McKenney
Signed-off-by: Cyrill Gorcunov
---
The prev patch body has been screwed, sorry.
kernel/rcu/tiny.c |2 +-
1 file
Bananapi M64 comes with an optional sensor based on the ov5640,
add support for it with below pin information.
- PE13, PE12 via i2c-gpio bitbanging
- CLK_CSI_MCLK as external clock
- PE1 as external clock pin muxing
- DLDO3 as AVDD supply
- ALDO1 as DOVDD supply
- ELDO3 as DVDD supply
- PE16 gpio
Add CSI support for Allwinner A64. Here is previous series[1]
Changes for v7:
- Drop quirk change, and add as suggusted by Maxime
- Use csi instead csi0 in pinctrl function
Changes for v6:
- set the mod rate in seett_power instead of probe
Changes for v5:
- Add mod_rate quirk for better handling
On Thu, 2019-01-24 at 19:05 +0100, Mathieu Malaterre wrote:
> During refactor in commit 9e478066eae4 ("mac80211: fix MU-MIMO
> follow-MAC mode") a new struct 'action' was declared with packed
> attribute as:
>
> struct {
> struct ieee80211_hdr_3addr hdr;
> u8 category;
>
CSI block in Allwinner A64 has similar features as like in H3,
but the default CSI_SCLK rate cannot work properly to drive the
connected sensor interface.
The tested mod cock rate is 300 MHz and BSP vfe media driver is also
using the same rate. Unfortunately there is no valid information about
On 1/24/19 3:25 AM, Jianchao Wang wrote:
> Hi Jens
>
> These two patches are small optimization for accessing the queue mapping
> in hot path. It saves the queue mapping results into blk_mq_ctx directly,
> then we needn't do the complicated bounce on queue_hw_ctx[] map[] and
> mq_map[].
I like
Add dts node details for Allwinner A64 CSI controller.
A64 CSI has similar features as like in H3, but the CSI_SCLK
need to update it to 300MHz than default clock rate.
Signed-off-by: Jagan Teki
---
arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 20 +++
1 file changed, 20
Some camera modules have the SoC feeding a master clock to the sensor
instead of having a standalone crystal. This clock signal is generated
from the clock control unit and output from the CSI MCLK function of
pin PE1.
Add a pinmux setting for it for camera sensors to reference.
Signed-off-by:
On Tue, Jan 22, 2019 at 1:52 PM Greg KH wrote:
>
> SPDX "GPL-2.0+" please.
>
> > would be if this code was derived from v2-only code that can't be
> > relicensed anymore.
>
> Are you _sure_ you want v2+? I ask as I am forced to :)
>
The licencing choice confuses me. Why would I choose a
Allwinner A64 CSI is a single channel time-multiplexed BT.656
protocol interface.
Add separate compatible string for A64 since it require explicit
change in sun6i_csi driver to update default CSI_SCLK rate.
Reviewed-by: Rob Herring
Signed-off-by: Jagan Teki
---
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
In this particular case put the fall through comment on a separate line so
as to match the regular expression expected by GCC.
This commit removes the following warning:
The rcu_qs is disabling IRQs by self so no need to do the same in raise_softirq,
instead we can save some cycles using raise_softirq_irqoff directly.
CC: Paul E. McKenney
Signed-off-by: Cyrill Gorcunov
---
kernel/rcu/tiny.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index:
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
This commit removes the following warning:
net/bluetooth/l2cap_core.c:4223:6: warning: this statement may fall through
[-Wimplicit-fallthrough=]
Cc: Gustavo Padovan
On one hand commit 28644c809f44 ("regmap: Add the rbtree cache support")
added 'regcache_rbtree_node' as packed structure, while on the other hand
commit e977145aeaad ("[RBTREE] Add explicit alignment to sizeof(long)
for struct rb_node.") declared struct 'rb_node' as aligned.
Solve the ambiguity
During refactor in commit 9e478066eae4 ("mac80211: fix MU-MIMO
follow-MAC mode") a new struct 'action' was declared with packed
attribute as:
struct {
struct ieee80211_hdr_3addr hdr;
u8 category;
u8 action_code;
} __packed action;
But since struct
There is a plan to build the kernel with -Wimplicit-fallthrough and
these places in the code produced warnings (W=1).
This commit removes the following warnings:
fs/ext2/inode.c:1237:7: warning: this statement may fall through
[-Wimplicit-fallthrough=]
fs/ext2/inode.c:1244:7: warning: this
We now using a common macro for PM operations in Intel LPSS driver,
and, since that macro relies on the definition and macro from linux/pm.h
header file, it's logical to include it directly in intel-lpss.h.
Otherwise it's a bit fragile and requires a proper ordering
of header inclusion in C files.
On Thu, Jan 24, 2019 at 03:17:27PM +0100, Michal Hocko wrote:
> a friendly ping for this. Does anybody see any problem with this
> approach?
FWIW, it looks fine to me.
It'd just be nice to have a few more words in the changelog about *how* the
x86 init was reworked ;-)
> On Mon 14-01-19
On Wed, Jan 23, 2019 at 05:44:57PM +0100, Paul Menzel wrote:
> From: Corey Minyard
> Date: Thu, 15 Feb 2018 16:58:26 -0600
>
> [ upstream commit bc48fa1b9d3b04106055b27078da824cd209865a ]
>
> Realtek has some sort of "Virtual" IPMI device on the PCI bus as a
> KCS controller, but whatever it
The ov5640_try_frame_interval operation updates the FPS as per user
input based on default ov5640_frame_rate, OV5640_30_FPS which is failed
to update when user trigger 15fps.
So, initialize the default ov5640_frame_rate to OV5640_15_FPS so-that
it can satisfy to update all fps.
Fixes:
Add BACKLIGHT_LCD_SUPPORT for SAMSUNG_Q10 to fix the
warning: unmet direct dependencies detected for BACKLIGHT_CLASS_DEVICE.
SAMSUNG_Q10 selects BACKLIGHT_CLASS_DEVICE but BACKLIGHT_CLASS_DEVICE
depends on BACKLIGHT_LCD_SUPPORT.
Copy BACKLIGHT_LCD_SUPPORT dependency into SAMSUNG_Q10 to fix:
Add BACKLIGHT_LCD_SUPPORT for ACPI_CMPC to fix the
warning: unmet direct dependencies detected for BACKLIGHT_CLASS_DEVICE.
ACPI_CMPC selects BACKLIGHT_CLASS_DEVICE but BACKLIGHT_CLASS_DEVICE
depends on BACKLIGHT_LCD_SUPPORT.
Copy BACKLIGHT_LCD_SUPPORT dependency into ACPI_CMPC to fix
WARNING:
Amarula A64 Relic has STLM75 sensor for digital temperature
and thermal watchdog.
Add support for it.
Signed-off-by: Jagan Teki
---
Note: the respective driver change is already in mainline
On Thu, Jan 24, 2019 at 05:18:12PM +0100, Thierry Reding wrote:
> On Thu, Jan 24, 2019 at 12:01:55PM -0300, Ezequiel Garcia wrote:
> > On Tue, 2018-10-30 at 10:15 +0100, Heiko Stuebner wrote:
> > > From: Nickey Yang
> > >
> > > Support Kingdisplay kd097d04 9.7" 1536x2048 TFT LCD panel,
> > > it
On Mon, Jan 21, 2019 at 10:12:02AM +0100, Linus Walleij wrote:
> This converts the GPIO regulator driver to use decriptors only.
This patch breaks the build for me:
drivers/regulator/gpio-regulator.c: In function ‘gpio_regulator_probe’:
drivers/regulator/gpio-regulator.c:256:33: error: ‘dev’
Move xtalk scanning to a later boot stage to be able using things like
kmalloc and friends.
Signed-off-by: Thomas Bogendoerfer
---
arch/mips/sgi-ip27/ip27-init.c | 3 ---
arch/mips/sgi-ip27/ip27-xtalk.c | 13 -
2 files changed, 12 insertions(+), 4 deletions(-)
diff --git
Introduced bridge_read/bridge_write/bridge_set/bridge_clr for accessing
bridge register and get rid of volatile declarations. Also removed
all typedefs from arch/mips/include/asm/pci/bridge.h and cleaned up
language in arch/mips/pci/ops-bridge.c
Signed-off-by: Thomas Bogendoerfer
---
Converted bridge code to a platform driver using the PCI generic driver
framework and use adding platform devices during xtalk scan. This allows
easier sharing bridge drvier for other SGI platforms like IP30 (Octane) and
IP35 (Origin 3k, Fuel, Tezro).
Signed-off-by: Thomas Bogendoerfer
---
Replace hub register access with __raw_readq/__raw_writeq and get
rid of hubreg_t completely. Also remove no longer (probably never)
used defines
Signed-off-by: Thomas Bogendoerfer
---
arch/mips/include/asm/sn/addrs.h | 63 +++-
Bridge ASIC is widely used in different SGI systems, but the connected
chipset is either HUB, HEART or BEDROCK. This commit abstracts chipset
irq setup and moves the bridge related irq setup to bridge code.
Signed-off-by: Thomas Bogendoerfer
---
arch/mips/include/asm/pci/bridge.h| 2 -
Topology and NMI output needs pr_cont() to look the way it was in the
old days of printk.
Signed-off-by: Thomas Bogendoerfer
---
arch/mips/sgi-ip27/ip27-memory.c | 28 +-
arch/mips/sgi-ip27/ip27-nmi.c| 62
2 files changed, 45
This commit rearranges the HUB interrupt code by using MIPS_IRQ_CPU
interrupt handling code and modern Linux IRQ framework features to get
rid of global and per cpu arrays. It also adds support for irq affinity
setting.
Signed-off-by: Thomas Bogendoerfer
---
arch/mips/Kconfig
SGI IP27 (Origin/Onyx2) and SGI IP30 (Octane) have a similair
architecture and share some hardware (ioc3/bridge). To share
the software parts this patchset reworks SGI IP27 interrupt
and pci bridge code. By using features Linux gained during the
many years since SGI IP27 code was integrated this
On 1/24/2019 5:52 AM, Rafael J. Wysocki wrote:
Andy/Darren, these two seem to be for you, but I can take them too as
related to ACPI tagentially, so please let me know.
I'll post V2 to fix a "fat-finger" in summary. I was hoping to receive a
feedback until now.
I'll get the V2 out.
On 1/24/2019 5:51 AM, Rafael J. Wysocki wrote:
Is anyone taking this or should I?
Nobody replied to this yet. I was hoping this series to go through acpi
tree like the rest of the other fixes.
On 1/24/2019 5:51 AM, Rafael J. Wysocki wrote:
Is anyone taking this or should I?
This got applied:
https://git.kernel.org/tip/625210cfa6c0c26ea422f655bf68288176f174e6
> On 24 Jan 2019, at 19:39, Vitaly Kuznetsov wrote:
>
> Liran Alon writes:
>
>>> On 24 Jan 2019, at 19:15, Vitaly Kuznetsov wrote:
>>>
>>> We shouldn't probably be suggesting using Enlightened VMCS when it's not
>>> enabled (not supported from guest's point of view). System reset through
Hi everyone / Linus
For my Master's dissertation at Kent University I've built a platform
and GUI to automate the process of submitting kernel module
configurations and installing kernel modules from those configurations.
Developers submit kernel module source code including a special file
Liran Alon writes:
>> On 24 Jan 2019, at 19:15, Vitaly Kuznetsov wrote:
>>
>> We shouldn't probably be suggesting using Enlightened VMCS when it's not
>> enabled (not supported from guest's point of view). System reset through
>> synthetic MSR is not recommended neither by genuine Hyper-V nor
On 1/23/19 9:40 PM, Michael Ellerman wrote:
> On Tue, 2019-01-08 at 21:00:10 UTC, "Gustavo A. R. Silva" wrote:
>> One of the more common cases of allocation size calculations is finding the
>> size of a structure that has a zero-sized array at the end, along with memory
>> for some number of
From: Colin Ian King
Don't populate the const arrays on the stack but instead make
it static. Makes the object code smaller, for example:
Before:
textdata bss dec hex filename
141078832 224 231635a7b bytcht_es8316.o
After:
textdata bss dec
If CONFIG_PM is disabled or runtime PM calls are forbidden, the clocks
will not be ON. This could cause issue during probe, where hda init
setup is done. This patch checks whether runtime PM is enabled or not.
If disabled, clocks are enabled in probe() and disabled in remove()
This patch does
On Thu, Jan 24, 2019 at 02:43:02PM +0100, Jaroslav Kysela wrote:
> If I look to the dma_buf_fd() implementation:
> fd = get_unused_fd_flags(flags);
> fd_install(fd, dmabuf->file);
> .. what if we just add one new ioctl to the ALSA's PCM API which will
> return a new anonymous inode
On Thu, Jan 24, 2019 at 07:25:53PM +0200, Mike Rapoport wrote:
> On Thu, Jan 24, 2019 at 04:51:53PM +, Mark Rutland wrote:
> > On Thu, Jan 24, 2019 at 04:19:33PM +, Christophe Leroy wrote:
> > > Since only the virtual address of allocated blocks is used,
> > > lets use functions returning
901 - 1000 of 1508 matches
Mail list logo
