On Wed, Aug 08, 2018 at 12:02:48PM -0600, Lina Iyer wrote:
> On Wed, Aug 08 2018 at 04:56 -0600, Lorenzo Pieralisi wrote:
> >On Mon, Aug 06, 2018 at 11:37:55AM +0200, Rafael J. Wysocki wrote:
> >>On Fri, Aug 3, 2018 at 1:42 PM, Ulf Hansson wrote:
> >>> [...]
> >>>
> >
> > Assuming that I
On Wed, Aug 08, 2018 at 12:02:48PM -0600, Lina Iyer wrote:
> On Wed, Aug 08 2018 at 04:56 -0600, Lorenzo Pieralisi wrote:
> >On Mon, Aug 06, 2018 at 11:37:55AM +0200, Rafael J. Wysocki wrote:
> >>On Fri, Aug 3, 2018 at 1:42 PM, Ulf Hansson wrote:
> >>> [...]
> >>>
> >
> > Assuming that I
On 09.08.2018 00:31, Dave Chinner wrote:
> On Wed, Aug 08, 2018 at 12:27:34PM +0200, Michal Hocko wrote:
>> [CC Josh - the whole series is
>> http://lkml.kernel.org/r/153365347929.19074.12509495712735843805.stgit@localhost.localdomain]
>>
>> On Wed 08-08-18 13:17:44, Kirill Tkhai wrote:
>>> On
On 09.08.2018 00:31, Dave Chinner wrote:
> On Wed, Aug 08, 2018 at 12:27:34PM +0200, Michal Hocko wrote:
>> [CC Josh - the whole series is
>> http://lkml.kernel.org/r/153365347929.19074.12509495712735843805.stgit@localhost.localdomain]
>>
>> On Wed 08-08-18 13:17:44, Kirill Tkhai wrote:
>>> On
On 08/08/18 17:57, Christoph Hellwig wrote:
> On Wed, Aug 08, 2018 at 05:47:40PM +0100, Marc Zyngier wrote:
>> The original GIC driver deals with 2.5 revisions of the architecture
>> (yes, there was something pre-GICv1...), and implementers have been
>> creative to the extreme. Still, we could
On 08/08/18 17:57, Christoph Hellwig wrote:
> On Wed, Aug 08, 2018 at 05:47:40PM +0100, Marc Zyngier wrote:
>> The original GIC driver deals with 2.5 revisions of the architecture
>> (yes, there was something pre-GICv1...), and implementers have been
>> creative to the extreme. Still, we could
The patch
regmap: Add regmap_noinc_read API
has been applied to the regmap tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus
The patch
regmap: Add regmap_noinc_read API
has been applied to the regmap tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus
The patch
ASoC: da7219: Add delays to capture path to remove DC offset noise
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
The patch
ASoC: da7219: Add delays to capture path to remove DC offset noise
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
On Tue, Aug 07, 2018 at 05:52:17PM +0300, Stefan Popa wrote:
> From: Crestez Dan Leonard
>
> The regmap API usually assumes that bulk read operations will read a
> range of registers but some I2C/SPI devices have certain registers for
The following changes since commit
On Tue, Aug 07, 2018 at 05:52:17PM +0300, Stefan Popa wrote:
> From: Crestez Dan Leonard
>
> The regmap API usually assumes that bulk read operations will read a
> range of registers but some I2C/SPI devices have certain registers for
The following changes since commit
On Thu, 2018-08-09 at 11:15 +0200, Hans de Goede wrote:
> On systems with ACPI instantiated i2c-clients, normally there is 1
> fw_node
> per i2c-device and that fw-node contains 1 I2cSerialBus resource for
> that 1
> i2c-device.
>
> But in some rare cases the manufacturer has decided to describe
On Thu, 2018-08-09 at 11:15 +0200, Hans de Goede wrote:
> On systems with ACPI instantiated i2c-clients, normally there is 1
> fw_node
> per i2c-device and that fw-node contains 1 I2cSerialBus resource for
> that 1
> i2c-device.
>
> But in some rare cases the manufacturer has decided to describe
On Wed, 8 Aug 2018 10:44:18 -0400
Tony Krowiak wrote:
> diff --git a/drivers/s390/crypto/vfio_ap_drv.c
> b/drivers/s390/crypto/vfio_ap_drv.c
> new file mode 100644
> index 000..d7e39ad
> --- /dev/null
> +++ b/drivers/s390/crypto/vfio_ap_drv.c
> @@ -0,0 +1,115 @@
> +//
On Wed, 8 Aug 2018 10:44:18 -0400
Tony Krowiak wrote:
> diff --git a/drivers/s390/crypto/vfio_ap_drv.c
> b/drivers/s390/crypto/vfio_ap_drv.c
> new file mode 100644
> index 000..d7e39ad
> --- /dev/null
> +++ b/drivers/s390/crypto/vfio_ap_drv.c
> @@ -0,0 +1,115 @@
> +//
On some i.MX SoCs' low power mode, UART iomux settings
may be lost, need to add pinctrl sleep/default mode switch
during suspend/resume to make sure UART iomux settings are
correct after resume.
Signed-off-by: Anson Huang
---
drivers/tty/serial/imx.c | 5 +
1 file changed, 5 insertions(+)
In noirq suspend/resume stage with no_console_suspend enabled,
.imx_console_write() may be called to print out log_buf
message by .printk(), so there will be race condition between
.imx_console_write() and .serial_imx_save/restore_context(),
need to add lock to protect the registers save/restore
On some i.MX SoCs' low power mode, UART iomux settings
may be lost, need to add pinctrl sleep/default mode switch
during suspend/resume to make sure UART iomux settings are
correct after resume.
Signed-off-by: Anson Huang
---
drivers/tty/serial/imx.c | 5 +
1 file changed, 5 insertions(+)
In noirq suspend/resume stage with no_console_suspend enabled,
.imx_console_write() may be called to print out log_buf
message by .printk(), so there will be race condition between
.imx_console_write() and .serial_imx_save/restore_context(),
need to add lock to protect the registers save/restore
On Thu, 2018-08-09 at 11:15 +0200, Hans de Goede wrote:
> Now that we init the status field to ACPI_STA_DEFAULT rather then to
> 0,
> the workaround for acpi_match_device_ids() always returning -ENOENT
> when
> status is 0 is no longer needed.
>
Always good to have only "minus" statistics
On Thu, 2018-08-09 at 11:15 +0200, Hans de Goede wrote:
> Now that we init the status field to ACPI_STA_DEFAULT rather then to
> 0,
> the workaround for acpi_match_device_ids() always returning -ENOENT
> when
> status is 0 is no longer needed.
>
Always good to have only "minus" statistics
On Thu, 2018-08-09 at 11:15 +0200, Hans de Goede wrote:
> Some devices have multiple I2cSerialBus resources and for things to
> work
> an i2c-client must be instantiated for each, each with its own
> i2c_device_id.
>
> Normally we only instantiate an i2c-client for the first resource,
> using
>
On Thu, 2018-08-09 at 11:15 +0200, Hans de Goede wrote:
> Some devices have multiple I2cSerialBus resources and for things to
> work
> an i2c-client must be instantiated for each, each with its own
> i2c_device_id.
>
> Normally we only instantiate an i2c-client for the first resource,
> using
>
> As for the rest of the series I'll wait from comments from Wolfram and
> the other reviewers.
Well, I acked patch 4 now because I like the general approach. I can't
say much about the rest since this is mostly ACPI/FW related.
Thanks Hans, for keeping at it.
signature.asc
Description: PGP
> As for the rest of the series I'll wait from comments from Wolfram and
> the other reviewers.
Well, I acked patch 4 now because I like the general approach. I can't
say much about the rest since this is mostly ACPI/FW related.
Thanks Hans, for keeping at it.
signature.asc
Description: PGP
On Thu, Aug 09, 2018 at 11:15:58AM +0200, Hans de Goede wrote:
> On systems with ACPI instantiated i2c-clients, normally there is 1 fw_node
> per i2c-device and that fw-node contains 1 I2cSerialBus resource for that 1
> i2c-device.
>
> But in some rare cases the manufacturer has decided to
On Thu, Aug 9, 2018 at 11:58 AM, Hans de Goede wrote:
> Hi,
>
> On 09-08-18 11:51, Andy Shevchenko wrote:
>>
>> On Thu, Aug 9, 2018 at 12:39 PM, Hans de Goede
>> wrote:
>>>
>>> On 09-08-18 11:35, Rafael J. Wysocki wrote:
On Thu, Aug 9, 2018 at 11:15 AM, Hans de Goede
wrote:
>>
>>
On Thu, Aug 9, 2018 at 11:58 AM, Hans de Goede wrote:
> Hi,
>
> On 09-08-18 11:51, Andy Shevchenko wrote:
>>
>> On Thu, Aug 9, 2018 at 12:39 PM, Hans de Goede
>> wrote:
>>>
>>> On 09-08-18 11:35, Rafael J. Wysocki wrote:
On Thu, Aug 9, 2018 at 11:15 AM, Hans de Goede
wrote:
>>
>>
On Thu, Aug 09, 2018 at 11:15:58AM +0200, Hans de Goede wrote:
> On systems with ACPI instantiated i2c-clients, normally there is 1 fw_node
> per i2c-device and that fw-node contains 1 I2cSerialBus resource for that 1
> i2c-device.
>
> But in some rare cases the manufacturer has decided to
On Wed, Aug 08, 2018 at 12:02:48PM -0600, Lina Iyer wrote:
[...]
> I will not speak to any comparison of benchmarks between OSI and PC.
> AFAIK, there are no platforms supporting both.
>
That's the fundamental issue here. So we have never ever done a proper
comparison.
> But, the OSI feature
On Wed, Aug 08, 2018 at 12:02:48PM -0600, Lina Iyer wrote:
[...]
> I will not speak to any comparison of benchmarks between OSI and PC.
> AFAIK, there are no platforms supporting both.
>
That's the fundamental issue here. So we have never ever done a proper
comparison.
> But, the OSI feature
Hi,
On 09-08-18 11:51, Andy Shevchenko wrote:
On Thu, Aug 9, 2018 at 12:39 PM, Hans de Goede wrote:
On 09-08-18 11:35, Rafael J. Wysocki wrote:
On Thu, Aug 9, 2018 at 11:15 AM, Hans de Goede
wrote:
I've applied the v4 of this patch and I don't think there are any
changes from it here.
Hi,
On 09-08-18 11:51, Andy Shevchenko wrote:
On Thu, Aug 9, 2018 at 12:39 PM, Hans de Goede wrote:
On 09-08-18 11:35, Rafael J. Wysocki wrote:
On Thu, Aug 9, 2018 at 11:15 AM, Hans de Goede
wrote:
I've applied the v4 of this patch and I don't think there are any
changes from it here.
From: Al Viro
smack ->d_instantiate() uses ->setxattr(), so to be able to call it before
we'd hashed the new dentry and attached it to inode, we need ->setxattr()
instances getting the inode as an explicit argument rather than obtaining
it from dentry.
Similar change for ->getxattr() had been
From: Al Viro
smack ->d_instantiate() uses ->setxattr(), so to be able to call it before
we'd hashed the new dentry and attached it to inode, we need ->setxattr()
instances getting the inode as an explicit argument rather than obtaining
it from dentry.
Similar change for ->getxattr() had been
From: Al Viro
commit ce23e640133484eebc20ca7b7668388213e11327 upstream.
Signed-off-by: Al Viro
[sw0312.kim: backport to 3.18]
Signed-off-by: Seung-Woo Kim
---
Documentation/filesystems/porting |6 +
.../staging/lustre/lustre/llite/llite_internal.h |4 +-
From: Al Viro
commit ce23e640133484eebc20ca7b7668388213e11327 upstream.
Signed-off-by: Al Viro
[sw0312.kim: backport to 3.18]
Signed-off-by: Seung-Woo Kim
---
Documentation/filesystems/porting |6 +
.../staging/lustre/lustre/llite/llite_internal.h |4 +-
From: Al Viro
commit b296821a7c42fa58baa17513b2b7b30ae66f3336 upstream.
... and do not assume they are already attached to each other
Signed-off-by: Al Viro
[sw0312.kim: backport to 3.18 including ext3]
Signed-off-by: Seung-Woo Kim
---
fs/9p/acl.c |7 ---
From: Al Viro
preparation for similar switch in ->setxattr() (see the next commit for
rationale).
Signed-off-by: Al Viro
[sw0312.kim: backport to 3.18 including ext3]
Signed-off-by: Seung-Woo Kim
---
fs/9p/acl.c |7 +++
fs/9p/xattr_security.c |5 +++--
From: Al Viro
commit b96809173e94ea2fa8c19c2e40e8545a1821bf57 upstream.
Signed-off-by: Al Viro
[sw0312.kim: backport to 3.18]
Signed-off-by: Seung-Woo Kim
---
fs/dcache.c | 18 +++---
1 files changed, 7 insertions(+), 11 deletions(-)
diff --git a/fs/dcache.c b/fs/dcache.c
From: Al Viro
commit b296821a7c42fa58baa17513b2b7b30ae66f3336 upstream.
... and do not assume they are already attached to each other
Signed-off-by: Al Viro
[sw0312.kim: backport to 3.18 including ext3]
Signed-off-by: Seung-Woo Kim
---
fs/9p/acl.c |7 ---
From: Al Viro
preparation for similar switch in ->setxattr() (see the next commit for
rationale).
Signed-off-by: Al Viro
[sw0312.kim: backport to 3.18 including ext3]
Signed-off-by: Seung-Woo Kim
---
fs/9p/acl.c |7 +++
fs/9p/xattr_security.c |5 +++--
From: Al Viro
commit b96809173e94ea2fa8c19c2e40e8545a1821bf57 upstream.
Signed-off-by: Al Viro
[sw0312.kim: backport to 3.18]
Signed-off-by: Seung-Woo Kim
---
fs/dcache.c | 18 +++---
1 files changed, 7 insertions(+), 11 deletions(-)
diff --git a/fs/dcache.c b/fs/dcache.c
On Thu, Aug 9, 2018 at 12:39 PM, Hans de Goede wrote:
> On 09-08-18 11:35, Rafael J. Wysocki wrote:
>> On Thu, Aug 9, 2018 at 11:15 AM, Hans de Goede
>> wrote:
>> I've applied the v4 of this patch and I don't think there are any
>> changes from it here.
>
>
> Correct, there were only changes to
On Thu, Aug 9, 2018 at 12:39 PM, Hans de Goede wrote:
> On 09-08-18 11:35, Rafael J. Wysocki wrote:
>> On Thu, Aug 9, 2018 at 11:15 AM, Hans de Goede
>> wrote:
>> I've applied the v4 of this patch and I don't think there are any
>> changes from it here.
>
>
> Correct, there were only changes to
On 09/08/18 10:14, Patrick Bellasi wrote:
> On 07-Aug 14:35, Juri Lelli wrote:
> > On 06/08/18 17:39, Patrick Bellasi wrote:
> >
> > [...]
> >
> > > @@ -4218,6 +4245,13 @@ static int __sched_setscheduler(struct task_struct
> > > *p,
> > > return retval;
> > > }
> > >
> > >
On 09/08/18 10:14, Patrick Bellasi wrote:
> On 07-Aug 14:35, Juri Lelli wrote:
> > On 06/08/18 17:39, Patrick Bellasi wrote:
> >
> > [...]
> >
> > > @@ -4218,6 +4245,13 @@ static int __sched_setscheduler(struct task_struct
> > > *p,
> > > return retval;
> > > }
> > >
> > >
On some platforms it has been noted that a pop noise can be
witnessed when capturing audio, mainly for first time after a
headset jack has been inserted. This is due to a DC offset in the
Mic PGA and so to avoid this delays are required when powering
up the capture path.
This commit rectifies the
On some platforms it has been noted that a pop noise can be
witnessed when capturing audio, mainly for first time after a
headset jack has been inserted. This is due to a DC offset in the
Mic PGA and so to avoid this delays are required when powering
up the capture path.
This commit rectifies the
This new symbol needs to be in the workaround-list for buggy
binutils, otherwise the build with gcc-4.6 fails.
Fixes: 39d668e04eda ('x86/mm/pti: Make pti_clone_kernel_text() compile on 32
bit')
Signed-off-by: Joerg Roedel
---
arch/x86/tools/relocs.c | 1 +
1 file changed, 1 insertion(+)
diff
This new symbol needs to be in the workaround-list for buggy
binutils, otherwise the build with gcc-4.6 fails.
Fixes: 39d668e04eda ('x86/mm/pti: Make pti_clone_kernel_text() compile on 32
bit')
Signed-off-by: Joerg Roedel
---
arch/x86/tools/relocs.c | 1 +
1 file changed, 1 insertion(+)
diff
On Wed, Aug 08, 2018 at 02:18:18PM -0700, skan...@codeaurora.org wrote:
> On 2018-08-08 01:47, Sudeep Holla wrote:
> >On Tue, Aug 07, 2018 at 12:37:07PM -0700, skan...@codeaurora.org wrote:
> >>On 2018-08-07 09:41, Rob Herring wrote:
> >>>On Wed, Aug 01, 2018 at 05:57:41PM -0700, Saravana Kannan
On Wed, Aug 08, 2018 at 02:18:18PM -0700, skan...@codeaurora.org wrote:
> On 2018-08-08 01:47, Sudeep Holla wrote:
> >On Tue, Aug 07, 2018 at 12:37:07PM -0700, skan...@codeaurora.org wrote:
> >>On 2018-08-07 09:41, Rob Herring wrote:
> >>>On Wed, Aug 01, 2018 at 05:57:41PM -0700, Saravana Kannan
Hi Stephen,
On Thu, Aug 09, 2018 at 09:24:20AM +1000, Stephen Rothwell wrote:
> Invalid absolute R_X86_64_32S relocation: __end_rodata_aligned
> /kisskb/src/arch/x86/boot/compressed/Makefile:127: recipe for target
> 'arch/x86/boot/compressed/vmlinux.relocs' failed
>
> Caused by commit
>
>
Hi Stephen,
On Thu, Aug 09, 2018 at 09:24:20AM +1000, Stephen Rothwell wrote:
> Invalid absolute R_X86_64_32S relocation: __end_rodata_aligned
> /kisskb/src/arch/x86/boot/compressed/Makefile:127: recipe for target
> 'arch/x86/boot/compressed/vmlinux.relocs' failed
>
> Caused by commit
>
>
Hi,
On 09-08-18 11:35, Rafael J. Wysocki wrote:
On Thu, Aug 9, 2018 at 11:15 AM, Hans de Goede wrote:
Since commit 63347db0affa ("ACPI / scan: Use acpi_bus_get_status() to
initialize ACPI_TYPE_DEVICE devs") the status field of normal acpi_devices
gets set to 0 by acpi_bus_type_and_status()
Hi,
On 09-08-18 11:35, Rafael J. Wysocki wrote:
On Thu, Aug 9, 2018 at 11:15 AM, Hans de Goede wrote:
Since commit 63347db0affa ("ACPI / scan: Use acpi_bus_get_status() to
initialize ACPI_TYPE_DEVICE devs") the status field of normal acpi_devices
gets set to 0 by acpi_bus_type_and_status()
On Thursday 09 Aug 2018 at 11:30:57 (+0200), Vincent Guittot wrote:
> On Tue, 24 Jul 2018 at 14:26, Quentin Perret wrote:
> >
> > From: Morten Rasmussen
> >
> > Energy-aware scheduling is only meant to be active while the system is
> > _not_ over-utilized. That is, there are spare cycles
On Thursday 09 Aug 2018 at 11:30:57 (+0200), Vincent Guittot wrote:
> On Tue, 24 Jul 2018 at 14:26, Quentin Perret wrote:
> >
> > From: Morten Rasmussen
> >
> > Energy-aware scheduling is only meant to be active while the system is
> > _not_ over-utilized. That is, there are spare cycles
On Thu, Aug 9, 2018 at 11:15 AM, Hans de Goede wrote:
> Since commit 63347db0affa ("ACPI / scan: Use acpi_bus_get_status() to
> initialize ACPI_TYPE_DEVICE devs") the status field of normal acpi_devices
> gets set to 0 by acpi_bus_type_and_status() and filled with its actual
> value later when
On Thu, Aug 9, 2018 at 11:15 AM, Hans de Goede wrote:
> Since commit 63347db0affa ("ACPI / scan: Use acpi_bus_get_status() to
> initialize ACPI_TYPE_DEVICE devs") the status field of normal acpi_devices
> gets set to 0 by acpi_bus_type_and_status() and filled with its actual
> value later when
внимания;
Ваши сообщения превысил лимит памяти, который составляет 5 Гб, определенных
администратором, который в настоящее время работает на 10.9GB, Вы не сможете
отправить или получить новую почту, пока вы повторно не проверить ваш почтовый
ящик почты. Чтобы восстановить работоспособность
внимания;
Ваши сообщения превысил лимит памяти, который составляет 5 Гб, определенных
администратором, который в настоящее время работает на 10.9GB, Вы не сможете
отправить или получить новую почту, пока вы повторно не проверить ваш почтовый
ящик почты. Чтобы восстановить работоспособность
On Wed, Aug 08, 2018 at 02:22:13PM -0500, Gustavo A. R. Silva wrote:
> @@ -518,7 +518,8 @@ static int adau1761_setup_digmic_jackdetect(struct
> snd_soc_component *component)
> ARRAY_SIZE(adau1761_jack_detect_controls));
> if (ret)
>
On Wed, Aug 08, 2018 at 02:22:13PM -0500, Gustavo A. R. Silva wrote:
> @@ -518,7 +518,8 @@ static int adau1761_setup_digmic_jackdetect(struct
> snd_soc_component *component)
> ARRAY_SIZE(adau1761_jack_detect_controls));
> if (ret)
>
On Tue, 24 Jul 2018 at 14:26, Quentin Perret wrote:
>
> From: Morten Rasmussen
>
> Energy-aware scheduling is only meant to be active while the system is
> _not_ over-utilized. That is, there are spare cycles available to shift
> tasks around based on their actual utilization to get a more
>
On Tue, 24 Jul 2018 at 14:26, Quentin Perret wrote:
>
> From: Morten Rasmussen
>
> Energy-aware scheduling is only meant to be active while the system is
> _not_ over-utilized. That is, there are spare cycles available to shift
> tasks around based on their actual utilization to get a more
>
On Wed, Aug 08, 2018 at 02:19:33PM -0500, Gustavo A. R. Silva wrote:
> @@ -648,6 +648,7 @@ static int adav80x_set_pll(struct snd_soc_component
> *component, int pll_id,
> pll_ctrl1 |= ADAV80X_PLL_CTRL1_PLLDIV;
> break;
> }
> +
On Wed, Aug 08, 2018 at 02:19:33PM -0500, Gustavo A. R. Silva wrote:
> @@ -648,6 +648,7 @@ static int adav80x_set_pll(struct snd_soc_component
> *component, int pll_id,
> pll_ctrl1 |= ADAV80X_PLL_CTRL1_PLLDIV;
> break;
> }
> +
On Wed, 2018-08-08 at 22:22 +0200, Wolfram Sang wrote:
> On Mon, Aug 06, 2018 at 08:54:07PM +0200, Alexandre Belloni wrote:
> > Switch to device_get_match_data in probe to match the device
> > specific data
> > instead of using the acpi specific function.
> >
> > Suggested-by: Andy Shevchenko
>
On Wed, 2018-08-08 at 22:22 +0200, Wolfram Sang wrote:
> On Mon, Aug 06, 2018 at 08:54:07PM +0200, Alexandre Belloni wrote:
> > Switch to device_get_match_data in probe to match the device
> > specific data
> > instead of using the acpi specific function.
> >
> > Suggested-by: Andy Shevchenko
>
[dropping everyone else while we discuss the code]
Thanks. I assume that branch as all the code that there is. Let me
look and get back to you.
On Thu, Aug 9, 2018 at 2:19 PM, Mikko Perttunen wrote:
> Here's my current code:
>
> https://github.com/cyndis/linux/commits/wip/t194-tcu-4
>
> "fixup!
[dropping everyone else while we discuss the code]
Thanks. I assume that branch as all the code that there is. Let me
look and get back to you.
On Thu, Aug 9, 2018 at 2:19 PM, Mikko Perttunen wrote:
> Here's my current code:
>
> https://github.com/cyndis/linux/commits/wip/t194-tcu-4
>
> "fixup!
Hi,
> I believe the reason for these api is because some arch changed to can
> not do DMA on stack recently. Maybe we should have dma_mapping to bounce
It is not only arch dependent. You can enable virtual stacks in Kconfig,
too.
> buffer like it bounce un-dma-able address for those arch? or we
Hi,
> I believe the reason for these api is because some arch changed to can
> not do DMA on stack recently. Maybe we should have dma_mapping to bounce
It is not only arch dependent. You can enable virtual stacks in Kconfig,
too.
> buffer like it bounce un-dma-able address for those arch? or we
On 09.08.2018 10:14, Michal Hocko wrote:
> On Wed 08-08-18 16:20:54, Kirill Tkhai wrote:
>> [Added two more places needed srcu_dereference(). All ->shrinker_map
>> dereferences must be under SRCU, and this v2 adds missed in previous]
>>
>> The patch makes shrinker list and shrinker_idr SRCU-safe
On 09.08.2018 10:14, Michal Hocko wrote:
> On Wed 08-08-18 16:20:54, Kirill Tkhai wrote:
>> [Added two more places needed srcu_dereference(). All ->shrinker_map
>> dereferences must be under SRCU, and this v2 adds missed in previous]
>>
>> The patch makes shrinker list and shrinker_idr SRCU-safe
On 09.08.2018 11:06, Cornelia Huck wrote:
> On Wed, 8 Aug 2018 10:44:14 -0400
> Tony Krowiak wrote:
>
>> From: Harald Freudenberger
>>
>> Move all the inline functions from the ap bus header
>> file ap_asm.h into the in-kernel api header file
>> arch/s390/include/asm/ap.h so that KVM can make
On 09.08.2018 11:06, Cornelia Huck wrote:
> On Wed, 8 Aug 2018 10:44:14 -0400
> Tony Krowiak wrote:
>
>> From: Harald Freudenberger
>>
>> Move all the inline functions from the ap bus header
>> file ap_asm.h into the in-kernel api header file
>> arch/s390/include/asm/ap.h so that KVM can make
Some devices have multiple I2cSerialBus resources and for things to work
an i2c-client must be instantiated for each, each with its own
i2c_device_id.
Normally we only instantiate an i2c-client for the first resource, using
the ACPI HID as id.
This commit adds a list of HIDs of devices, which
Some devices have multiple I2cSerialBus resources and for things to work
an i2c-client must be instantiated for each, each with its own
i2c_device_id.
Normally we only instantiate an i2c-client for the first resource, using
the ACPI HID as id.
This commit adds a list of HIDs of devices, which
Since commit 63347db0affa ("ACPI / scan: Use acpi_bus_get_status() to
initialize ACPI_TYPE_DEVICE devs") the status field of normal acpi_devices
gets set to 0 by acpi_bus_type_and_status() and filled with its actual
value later when acpi_add_single_object() calls acpi_bus_get_status().
This means
Since commit 63347db0affa ("ACPI / scan: Use acpi_bus_get_status() to
initialize ACPI_TYPE_DEVICE devs") the status field of normal acpi_devices
gets set to 0 by acpi_bus_type_and_status() and filled with its actual
value later when acpi_add_single_object() calls acpi_bus_get_status().
This means
On systems with ACPI instantiated i2c-clients, normally there is 1 fw_node
per i2c-device and that fw-node contains 1 I2cSerialBus resource for that 1
i2c-device.
But in some rare cases the manufacturer has decided to describe multiple
i2c-devices in a single ACPI fwnode with multiple
On systems with ACPI instantiated i2c-clients, normally there is 1 fw_node
per i2c-device and that fw-node contains 1 I2cSerialBus resource for that 1
i2c-device.
But in some rare cases the manufacturer has decided to describe multiple
i2c-devices in a single ACPI fwnode with multiple
Now that we init the status field to ACPI_STA_DEFAULT rather then to 0,
the workaround for acpi_match_device_ids() always returning -ENOENT when
status is 0 is no longer needed.
Signed-off-by: Hans de Goede
---
Changes in v3:
-New patch in v3 of this patch-set
---
drivers/acpi/x86/utils.c | 10
Now that we init the status field to ACPI_STA_DEFAULT rather then to 0,
the workaround for acpi_match_device_ids() always returning -ENOENT when
status is 0 is no longer needed.
Signed-off-by: Hans de Goede
---
Changes in v3:
-New patch in v3 of this patch-set
---
drivers/acpi/x86/utils.c | 10
Hi All,
Here is v5 of my patch-series for dealing with multiple independent i2c
devices being described in a single ACPI fwnode.
Changes in v5:
-s/no_clients/num_clients/
-Change patch 4 Subject prefix to platform/x86
Changes in v4:
-Rewrite commit message of first patch as this is NOT a bug
On Wed, Aug 08, 2018 at 10:24:13AM -0700, Stephen Boyd wrote:
> Now that the /firmware/coreboot node in DT is populated by the core DT
> platform code with commit 3aa0582fdb82 ("of: platform: populate
> /firmware/ node from of_platform_default_populate_init()") we should and
> can remove the
Hi,
On 08-08-18 19:00, Wolfram Sang wrote:
$subject still says "i2c:"
Ah, good point I will send a v5 with this fixed, I will also
do s/no_clients/num_clients/ for v5 as Andy requested.
Regards,
Hans
On Wed, Aug 08, 2018 at 10:24:13AM -0700, Stephen Boyd wrote:
> Now that the /firmware/coreboot node in DT is populated by the core DT
> platform code with commit 3aa0582fdb82 ("of: platform: populate
> /firmware/ node from of_platform_default_populate_init()") we should and
> can remove the
Hi,
On 08-08-18 19:00, Wolfram Sang wrote:
$subject still says "i2c:"
Ah, good point I will send a v5 with this fixed, I will also
do s/no_clients/num_clients/ for v5 as Andy requested.
Regards,
Hans
Hi All,
Here is v5 of my patch-series for dealing with multiple independent i2c
devices being described in a single ACPI fwnode.
Changes in v5:
-s/no_clients/num_clients/
-Change patch 4 Subject prefix to platform/x86
Changes in v4:
-Rewrite commit message of first patch as this is NOT a bug
On 07-Aug 14:35, Juri Lelli wrote:
> On 06/08/18 17:39, Patrick Bellasi wrote:
>
> [...]
>
> > @@ -4218,6 +4245,13 @@ static int __sched_setscheduler(struct task_struct
> > *p,
> > return retval;
> > }
> >
> > + /* Configure utilization clamps for the task */
> > +
On 07-Aug 14:35, Juri Lelli wrote:
> On 06/08/18 17:39, Patrick Bellasi wrote:
>
> [...]
>
> > @@ -4218,6 +4245,13 @@ static int __sched_setscheduler(struct task_struct
> > *p,
> > return retval;
> > }
> >
> > + /* Configure utilization clamps for the task */
> > +
On Wed, 2018-08-08 at 22:57 +0200, Wolfram Sang wrote:
> On Sat, Jul 07, 2018 at 05:29:54PM +0800, Jun Gao wrote:
> > From: Jun Gao
> >
> > This function is needed by i2c_get_dma_safe_msg_buf() potentially.
> > It is used to free DMA safe buffer when DMA operation fails.
> >
> > Signed-off-by:
On Wed, 2018-08-08 at 22:57 +0200, Wolfram Sang wrote:
> On Sat, Jul 07, 2018 at 05:29:54PM +0800, Jun Gao wrote:
> > From: Jun Gao
> >
> > This function is needed by i2c_get_dma_safe_msg_buf() potentially.
> > It is used to free DMA safe buffer when DMA operation fails.
> >
> > Signed-off-by:
On Wed, 8 Aug 2018 10:44:14 -0400
Tony Krowiak wrote:
> From: Harald Freudenberger
>
> Move all the inline functions from the ap bus header
> file ap_asm.h into the in-kernel api header file
> arch/s390/include/asm/ap.h so that KVM can make use
> of all the low level AP functions.
>
>
On Wed, 8 Aug 2018 10:44:14 -0400
Tony Krowiak wrote:
> From: Harald Freudenberger
>
> Move all the inline functions from the ap bus header
> file ap_asm.h into the in-kernel api header file
> arch/s390/include/asm/ap.h so that KVM can make use
> of all the low level AP functions.
>
>
1001 - 1100 of 1264 matches
Mail list logo
