Hello Andrew,
>> This patch set is to follow up modifications of struct page for
>> makedumpfile which filters dump file.
>> It's necessary to filter unnecessary compound pages in newer kernel
>> as usual.
>>
>> Incidentally, [PATCH 1/2] was post in:
>>
>> https://lkml.org/lkml/2016/1/27/92
>>
Hello Andrew,
>> This patch set is to follow up modifications of struct page for
>> makedumpfile which filters dump file.
>> It's necessary to filter unnecessary compound pages in newer kernel
>> as usual.
>>
>> Incidentally, [PATCH 1/2] was post in:
>>
>> https://lkml.org/lkml/2016/1/27/92
>>
The wake_up_all_idle_cpus API always wake up all the online
cpus, but sometimes we only want to wake up a set of cpus.
Use a generic function to wake up a group of cpus that is
specified by the cpumask parameter. This generic API can
benefit to the cases that only need to wake up a set of
cpus.
The wake_up_all_idle_cpus API always wake up all the online
cpus, but sometimes we only want to wake up a set of cpus.
Use a generic function to wake up a group of cpus that is
specified by the cpumask parameter. This generic API can
benefit to the cases that only need to wake up a set of
cpus.
Hi,
Mark Brown writes:
> On Thu, Mar 31, 2016 at 09:42:58AM +0300, Felipe Balbi wrote:
>> Baolin Wang writes:
>
>> > I want to use bus structure to manage the charger device. Maybe choose
>> > class to manage them?
>
>> I guess a class would fit
Hi,
Mark Brown writes:
> On Thu, Mar 31, 2016 at 09:42:58AM +0300, Felipe Balbi wrote:
>> Baolin Wang writes:
>
>> > I want to use bus structure to manage the charger device. Maybe choose
>> > class to manage them?
>
>> I guess a class would fit better in this case.
>
> IIRC Greg didn't want
From: Wan Zongshun
AMD Uart DMA belongs to ACPI HID type device, and its driver
is basing on AMBA Bus, need also IOMMU support.
This patch is just to set the AMD iommu callbacks for amba bus.
Signed-off-by: Wan Zongshun
---
drivers/iommu/amd_iommu.c
From: Suravee Suthikulpanit
This patch modifies the existing struct ivhd_header,
which currently only support IVHD type 0x10, to add
new fields from IVHD type 11h and 40h.
It also modifies the pointer calculation to allow
support for IVHD type 11h and 40h
From: Wan Zongshun
AMD Uart DMA belongs to ACPI HID type device, and its driver
is basing on AMBA Bus, need also IOMMU support.
This patch is just to set the AMD iommu callbacks for amba bus.
Signed-off-by: Wan Zongshun
---
drivers/iommu/amd_iommu.c | 13 -
1 file changed, 12
From: Suravee Suthikulpanit
This patch modifies the existing struct ivhd_header,
which currently only support IVHD type 0x10, to add
new fields from IVHD type 11h and 40h.
It also modifies the pointer calculation to allow
support for IVHD type 11h and 40h
Signed-off-by: Suravee Suthikulpanit
From: Wan Zongshun
This patch introduces acpihid_map, which is used to store
the new IVHD device entry extracted from BIOS IVRS table.
It also provides a utility function add_acpi_hid_device(),
to add this types of devices to the map.
Signed-off-by: Wan Zongshun
From: Wan Zongshun
This patch introduces acpihid_map, which is used to store
the new IVHD device entry extracted from BIOS IVRS table.
It also provides a utility function add_acpi_hid_device(),
to add this types of devices to the map.
Signed-off-by: Wan Zongshun
Signed-off-by: Suravee
From: Wan Zongshun
There are some devices indentified using ACPI HID format in AMD chip.
This patch series enable iommu support for those ACPI HID device,
since the existing AMD iommu only supports PCI bus based device.
The latest public version of AMD IOMMU specification
From: Wan Zongshun
There are some devices indentified using ACPI HID format in AMD chip.
This patch series enable iommu support for those ACPI HID device,
since the existing AMD iommu only supports PCI bus based device.
The latest public version of AMD IOMMU specification that describes
the
Sorry, my fault. I made a typo mistake when sending the patch. I will
fix it and resend the patch.
On Thu, Mar 31, 2016 at 1:24 AM, kbuild test robot <l...@intel.com> wrote:
> Hi Lianwei,
>
> [auto build test ERROR on pm/linux-next]
> [also build test ERROR on v4.6-rc1 next-20
Sorry, my fault. I made a typo mistake when sending the patch. I will
fix it and resend the patch.
On Thu, Mar 31, 2016 at 1:24 AM, kbuild test robot wrote:
> Hi Lianwei,
>
> [auto build test ERROR on pm/linux-next]
> [also build test ERROR on v4.6-rc1 next-20160331]
> [if your p
On Fri, 01 Apr 2016 00:26:18 +0200,
Luis R. Rodriguez wrote:
>
> On Wed, Mar 30, 2016 at 08:07:04AM +0200, Takashi Iwai wrote:
> > On Tue, 29 Mar 2016 23:37:32 +0200,
> > Andy Lutomirski wrote:
> > >
> > > Would it be possible to revert:
> > >
> > > commit
On Fri, 01 Apr 2016 00:26:18 +0200,
Luis R. Rodriguez wrote:
>
> On Wed, Mar 30, 2016 at 08:07:04AM +0200, Takashi Iwai wrote:
> > On Tue, 29 Mar 2016 23:37:32 +0200,
> > Andy Lutomirski wrote:
> > >
> > > Would it be possible to revert:
> > >
> > > commit
From: Suravee Suthikulpanit
This patch introduces a new kernel parameter, ivrs_acpihid.
This is used to override existing ACPI-HID IVHD device entry,
or add an entry in case it is missing in the IVHD.
Signed-off-by: Wan Zongshun
From: Wan Zongshun
Current IOMMU driver make assumption that the downstream devices are PCI.
With the newly added ACPI-HID IVHD device entry support, this is no
longer true. This patch is to add dev type check and to distinguish the
pci and acpihid device code path.
From: Wan Zongshun
This patch is to make the call-sites of get_device_id aware of its
return value.
Signed-off-by: Wan Zongshun
---
drivers/iommu/amd_iommu.c | 51 +--
1 file changed, 41 insertions(+), 10
From: Suravee Suthikulpanit
This patch introduces a new kernel parameter, ivrs_acpihid.
This is used to override existing ACPI-HID IVHD device entry,
or add an entry in case it is missing in the IVHD.
Signed-off-by: Wan Zongshun
Signed-off-by: Suravee Suthikulpanit
---
From: Wan Zongshun
Current IOMMU driver make assumption that the downstream devices are PCI.
With the newly added ACPI-HID IVHD device entry support, this is no
longer true. This patch is to add dev type check and to distinguish the
pci and acpihid device code path.
Signed-off-by: Wan Zongshun
From: Wan Zongshun
This patch is to make the call-sites of get_device_id aware of its
return value.
Signed-off-by: Wan Zongshun
---
drivers/iommu/amd_iommu.c | 51 +--
1 file changed, 41 insertions(+), 10 deletions(-)
diff --git
From: Wan Zongshun
This patch creates a new function for finding or creating an IOMMU
group for acpihid(ACPI Hardware ID) device.
The acpihid devices with the same devid will be put into same group and
there will have the same domain id and share the same page table.
From: Wan Zongshun
This patch creates a new function for finding or creating an IOMMU
group for acpihid(ACPI Hardware ID) device.
The acpihid devices with the same devid will be put into same group and
there will have the same domain id and share the same page table.
Signed-off-by: Wan
From: Suravee Suthikulpanit
The IVRS in more recent AMD system usually contains multiple
IVHD block types (e.g. 0x10, 0x11, and 0x40) for each IOMMU.
The newer IVHD types provide more information (e.g. new features
specified in the IOMMU spec), while maintain
From: Suravee Suthikulpanit
The IVHD header type 11h and 40h introduce the PCSup bit in
the EFR Register Image bit fileds. This should be used to
determine the IOMMU performance support instead of relying
on the PNCounters and PNBanks.
Note also that the PNCouters
From: Suravee Suthikulpanit
The IVRS in more recent AMD system usually contains multiple
IVHD block types (e.g. 0x10, 0x11, and 0x40) for each IOMMU.
The newer IVHD types provide more information (e.g. new features
specified in the IOMMU spec), while maintain compatibility with
the older IVHD
From: Suravee Suthikulpanit
The IVHD header type 11h and 40h introduce the PCSup bit in
the EFR Register Image bit fileds. This should be used to
determine the IOMMU performance support instead of relying
on the PNCounters and PNBanks.
Note also that the PNCouters and PNBanks bits in the IOMMU
From: Andrey Vagin
__vfs_write() returns a negative value in a error case.
Cc: Ian Kent
Signed-off-by: Andrey Vagin
---
fs/autofs4/waitq.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/fs/autofs4/waitq.c
From: Andrey Vagin
__vfs_write() returns a negative value in a error case.
Cc: Ian Kent
Signed-off-by: Andrey Vagin
---
fs/autofs4/waitq.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/fs/autofs4/waitq.c b/fs/autofs4/waitq.c
index 0146d91..631f155 100644
---
Hi,
IMO, there is already a similar function upstreamed:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c85cc81
Could it work for your use case?
> From: linux-acpi-ow...@vger.kernel.org [mailto:linux-acpi-
> ow...@vger.kernel.org] On Behalf Of Octavian Purdila
>
Hi,
IMO, there is already a similar function upstreamed:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c85cc81
Could it work for your use case?
> From: linux-acpi-ow...@vger.kernel.org [mailto:linux-acpi-
> ow...@vger.kernel.org] On Behalf Of Octavian Purdila
>
On Thu, Mar 31, 2016 at 09:29:30PM -0600, Jens Axboe wrote:
> On 03/31/2016 06:56 PM, Dave Chinner wrote:
> >I'm not changing the host kernels - it's a production machine and so
> >it runs long uptime testing of stable kernels. (e.g. catch slow
> >memory leaks, etc). So if you've disabled
On Thu, Mar 31, 2016 at 09:29:30PM -0600, Jens Axboe wrote:
> On 03/31/2016 06:56 PM, Dave Chinner wrote:
> >I'm not changing the host kernels - it's a production machine and so
> >it runs long uptime testing of stable kernels. (e.g. catch slow
> >memory leaks, etc). So if you've disabled
Hi,
> From: linux-acpi-ow...@vger.kernel.org [mailto:linux-acpi-
> ow...@vger.kernel.org] On Behalf Of Octavian Purdila
> Subject: [RFC PATCH 10/10] acpi: add support for loading SSDTs via configfs
>
> Add support for acpi_user_table configfs items that allows the user to
> load new tables. The
Hi,
> From: linux-acpi-ow...@vger.kernel.org [mailto:linux-acpi-
> ow...@vger.kernel.org] On Behalf Of Octavian Purdila
> Subject: [RFC PATCH 10/10] acpi: add support for loading SSDTs via configfs
>
> Add support for acpi_user_table configfs items that allows the user to
> load new tables. The
On 04/01/2016 10:55 AM, Eric Dumazet wrote:
> On Fri, 2016-04-01 at 10:13 +0800, Jason Wang wrote:
>
>
>> The problem is we want to support busy polling for tun. This needs
>> napi_id to be passed to tun socket by sk_mark_napi_id() during
>> tun_net_xmit(). But before reaching this, XPS will set
On 04/01/2016 10:55 AM, Eric Dumazet wrote:
> On Fri, 2016-04-01 at 10:13 +0800, Jason Wang wrote:
>
>
>> The problem is we want to support busy polling for tun. This needs
>> napi_id to be passed to tun socket by sk_mark_napi_id() during
>> tun_net_xmit(). But before reaching this, XPS will set
From: Len Brown
For x86 processors with APERF/MPERF and TSC,
return meaningful and consistent MHz in
/proc/cpuinfo and
/sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq
MHz is computed like so:
MHz = base_MHz * delta_APERF / delta_MPERF
MHz is the average frequency of
From: Len Brown
For x86 processors with APERF/MPERF and TSC,
return meaningful and consistent MHz in
/proc/cpuinfo and
/sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq
MHz is computed like so:
MHz = base_MHz * delta_APERF / delta_MPERF
MHz is the average frequency of the busy processor
Hi all,
Changes since 20160331:
My fixes tree contains:
perf tools: Fix build break on powerpc
The qcom tree gained a build failure so I used the version from
next-20160331.
The pm tree gained a build failure so I used the verison from
next-20160331.
The gpio tree lost its build failure
Hi all,
Changes since 20160331:
My fixes tree contains:
perf tools: Fix build break on powerpc
The qcom tree gained a build failure so I used the version from
next-20160331.
The pm tree gained a build failure so I used the verison from
next-20160331.
The gpio tree lost its build failure
Hi Буди,
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on v4.6-rc1 next-20160331]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/info-are-ma/DVB-driver-for-Earthsoft
Hi Буди,
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on v4.6-rc1 next-20160331]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/info-are-ma/DVB-driver-for-Earthsoft
Hi Буди,
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on v4.6-rc1 next-20160331]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/info-are-ma/DVB-driver
Hi Буди,
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on v4.6-rc1 next-20160331]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/info-are-ma/DVB-driver
Hi Буди,
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on v4.6-rc1 next-20160331]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/info-are-ma/DVB-driver-for-Earthsoft
Hi Буди,
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on v4.6-rc1 next-20160331]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/info-are-ma/DVB-driver-for-Earthsoft
Hi Linus,
Nothing too crazy in here, a bunch of AMD fixes/quirks,
two msm, some rockchip fixes, and a udl warning fix,
along with one locking fix for displayport that seems
to fix some dodgy monitors.
Thanks,
Dave.
The following changes since commit c05c2ec96bb8b7310da1055c7b9d786a3ec6dc0c:
Hi Linus,
Nothing too crazy in here, a bunch of AMD fixes/quirks,
two msm, some rockchip fixes, and a udl warning fix,
along with one locking fix for displayport that seems
to fix some dodgy monitors.
Thanks,
Dave.
The following changes since commit c05c2ec96bb8b7310da1055c7b9d786a3ec6dc0c:
On Mon, Mar 28, 2016 at 11:30:56PM +0900, Minchan Kim wrote:
> On Fri, Mar 18, 2016 at 04:58:31PM +0900, Minchan Kim wrote:
>> "remove compressed copy from zram in-memory"
>> applied swap_slot_free_notify call in *end_swap_bio_read* to
>> remove duplicated memory between zram and memory.
>>
>>
On Mon, Mar 28, 2016 at 11:30:56PM +0900, Minchan Kim wrote:
> On Fri, Mar 18, 2016 at 04:58:31PM +0900, Minchan Kim wrote:
>> "remove compressed copy from zram in-memory"
>> applied swap_slot_free_notify call in *end_swap_bio_read* to
>> remove duplicated memory between zram and memory.
>>
>>
> -Original Message-
> From: Mathias Nyman [mailto:mathias.ny...@linux.intel.com]
> Sent: Thursday, March 31, 2016 8:07 PM
> To: Rajesh Bhagat
> Cc: gre...@linuxfoundation.org; linux-...@vger.kernel.org; linux-
> ker...@vger.kernel.org; Sriram Dash
> -Original Message-
> From: Mathias Nyman [mailto:mathias.ny...@linux.intel.com]
> Sent: Thursday, March 31, 2016 8:07 PM
> To: Rajesh Bhagat
> Cc: gre...@linuxfoundation.org; linux-...@vger.kernel.org; linux-
> ker...@vger.kernel.org; Sriram Dash
> Subject: Re: [PATCH] usb: xhci: Fix
Build errors on aarch64:
libperf.a(libperf-in.o): In function `convert_timestamp':
util/jitdump.c:356: undefined reference to `tsc_to_perf_time'
collect2: error: ld returned 1 exit status
Makefile.perf:347: recipe for target 'perf' failed
make[1]: *** [perf] Error 1
Makefile:68:
Build errors on aarch64:
libperf.a(libperf-in.o): In function `convert_timestamp':
util/jitdump.c:356: undefined reference to `tsc_to_perf_time'
collect2: error: ld returned 1 exit status
Makefile.perf:347: recipe for target 'perf' failed
make[1]: *** [perf] Error 1
Makefile:68:
Hi Heiko,
I also updated some clock patches for RK3399 recently, and I will
continue to update clock patches_V7 in future.
Please note them. :-)
Thanks.
On 2016年04月01日 11:23, Heiko Stuebner wrote:
Hi Jianqun,
Am Freitag, 1. April 2016, 10:55:09 schrieb jay.xu:
After talking with xing,
Hi Heiko,
I also updated some clock patches for RK3399 recently, and I will
continue to update clock patches_V7 in future.
Please note them. :-)
Thanks.
On 2016年04月01日 11:23, Heiko Stuebner wrote:
Hi Jianqun,
Am Freitag, 1. April 2016, 10:55:09 schrieb jay.xu:
After talking with xing,
On Thu, Mar 31, 2016 at 05:23:27PM -0700, Peter Hurley wrote:
> On Sun, Feb 7, 2016 at 6:21 PM, Greg KH wrote:
> > On Mon, Feb 08, 2016 at 01:16:29PM +1100, Stephen Rothwell wrote:
> >> Hi Greg,
> >>
> >> Today's linux-next merge of the tty tree got a conflict in:
> >>
> >>
On Thu, Mar 31, 2016 at 05:23:27PM -0700, Peter Hurley wrote:
> On Sun, Feb 7, 2016 at 6:21 PM, Greg KH wrote:
> > On Mon, Feb 08, 2016 at 01:16:29PM +1100, Stephen Rothwell wrote:
> >> Hi Greg,
> >>
> >> Today's linux-next merge of the tty tree got a conflict in:
> >>
> >> drivers/tty/tty_io.c
Hi Буди,
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on v4.6-rc1 next-20160331]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/info-are-ma/DVB-driver-for-Earthsoft
Hi Буди,
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on v4.6-rc1 next-20160331]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/info-are-ma/DVB-driver-for-Earthsoft
On 03/31/2016 09:29 PM, Jens Axboe wrote:
I can't seem to reproduce this at all. On an nvme device, I get a
fairly steady 60K/sec file creation rate, and we're nowhere near
being IO bound. So the throttling has no effect at all.
That's too slow to show the stalls - your likely concurrency
On 03/31/2016 09:29 PM, Jens Axboe wrote:
I can't seem to reproduce this at all. On an nvme device, I get a
fairly steady 60K/sec file creation rate, and we're nowhere near
being IO bound. So the throttling has no effect at all.
That's too slow to show the stalls - your likely concurrency
On 03/31/2016 09:29 PM, Jens Axboe wrote:
I'm not changing the host kernels - it's a production machine and so
it runs long uptime testing of stable kernels. (e.g. catch slow
memory leaks, etc). So if you've disabled throttling in the guest, I
can't test the throttling changes.
Right, that'd
On 03/31/2016 09:29 PM, Jens Axboe wrote:
I'm not changing the host kernels - it's a production machine and so
it runs long uptime testing of stable kernels. (e.g. catch slow
memory leaks, etc). So if you've disabled throttling in the guest, I
can't test the throttling changes.
Right, that'd
The global utilities block controls power management, I/O device
enabling, power-onreset(POR) configuration monitoring, alternate
function selection for multiplexed signals,and clock control.
This patch adds GUTS driver to manage and access global utilities
block.
Signed-off-by: Yangbo Lu
The global utilities block controls power management, I/O device
enabling, power-onreset(POR) configuration monitoring, alternate
function selection for multiplexed signals,and clock control.
This patch adds GUTS driver to manage and access global utilities
block.
Signed-off-by: Yangbo Lu
---
On 03/31/2016 06:33 PM, Greg Ungerer wrote:
On 01/04/16 10:53, Guenter Roeck wrote:
On Fri, Apr 01, 2016 at 10:29:11AM +1000, Greg Ungerer wrote:
Hi Guenter,
On 01/04/16 01:11, Guenter Roeck wrote:
Since commit ff2b13592299 ("gpio: make the gpiochip a real device"),
attempts to add a gpio
On 03/31/2016 06:33 PM, Greg Ungerer wrote:
On 01/04/16 10:53, Guenter Roeck wrote:
On Fri, Apr 01, 2016 at 10:29:11AM +1000, Greg Ungerer wrote:
Hi Guenter,
On 01/04/16 01:11, Guenter Roeck wrote:
Since commit ff2b13592299 ("gpio: make the gpiochip a real device"),
attempts to add a gpio
On Thu, Mar 31, 2016 at 09:24:57PM -0500, Eric Biggers wrote:
> I feel it's a small improvement as it reduces the chance of bugs. However, if
> you look at all the system calls, they are, in general, inconsistent about
> using
> 'const'. So may be right that changing just a few isn't
On Thu, Mar 31, 2016 at 09:24:57PM -0500, Eric Biggers wrote:
> I feel it's a small improvement as it reduces the chance of bugs. However, if
> you look at all the system calls, they are, in general, inconsistent about
> using
> 'const'. So may be right that changing just a few isn't
On 03/31/2016 06:56 PM, Dave Chinner wrote:
On Thu, Mar 31, 2016 at 10:21:04AM -0600, Jens Axboe wrote:
On 03/31/2016 08:29 AM, Jens Axboe wrote:
What I see in these performance dips is the XFS transaction
subsystem stalling *completely* - instead of running at a steady
state of around 350,000
From: Ma Jun
When the CPU of a non-balanced irq bounded is off line, the irq will be
migrated to other CPUs,
usually the first cpu on-line.
We can suppose the situation if a system has more than one non-balanced irq.
At extreme case, these irqs will be migrated to the same
From: Ma Jun
When the CPU of a non-balanced irq bounded is off line, the irq will be
migrated to other CPUs,
usually the first cpu on-line.
We can suppose the situation if a system has more than one non-balanced irq.
At extreme case, these irqs will be migrated to the same CPU and will cause
On 03/31/2016 06:56 PM, Dave Chinner wrote:
On Thu, Mar 31, 2016 at 10:21:04AM -0600, Jens Axboe wrote:
On 03/31/2016 08:29 AM, Jens Axboe wrote:
What I see in these performance dips is the XFS transaction
subsystem stalling *completely* - instead of running at a steady
state of around 350,000
On 03/31/2016 06:46 PM, Dave Chinner wrote:
On Thu, Mar 31, 2016 at 08:29:35AM -0600, Jens Axboe wrote:
On 03/31/2016 02:24 AM, Dave Chinner wrote:
On Wed, Mar 30, 2016 at 09:07:48AM -0600, Jens Axboe wrote:
Hi,
This patchset isn't as much a final solution, as it's demonstration
of what I
On 03/31/2016 06:46 PM, Dave Chinner wrote:
On Thu, Mar 31, 2016 at 08:29:35AM -0600, Jens Axboe wrote:
On 03/31/2016 02:24 AM, Dave Chinner wrote:
On Wed, Mar 30, 2016 at 09:07:48AM -0600, Jens Axboe wrote:
Hi,
This patchset isn't as much a final solution, as it's demonstration
of what I
Hi Jianqun,
Am Freitag, 1. April 2016, 10:55:09 schrieb jay.xu:
> After talking with xing, we plan to summit dtsi after xing's patches are
> applied,
> and I will update the patch for rk3399 core dtsi quickly
Not sure if you have seen it, but I picked up Xing's most recent clock
patches already
In the ppc64 big endian ABI, function symbols point to function
descriptors. The symbols which point to the function entry points
have a dot in front of the function name. Consequently, when the
ftrace filter mechanism searches for the symbol corresponding to
an entry point address, it gets the
Hi Jianqun,
Am Freitag, 1. April 2016, 10:55:09 schrieb jay.xu:
> After talking with xing, we plan to summit dtsi after xing's patches are
> applied,
> and I will update the patch for rk3399 core dtsi quickly
Not sure if you have seen it, but I picked up Xing's most recent clock
patches already
In the ppc64 big endian ABI, function symbols point to function
descriptors. The symbols which point to the function entry points
have a dot in front of the function name. Consequently, when the
ftrace filter mechanism searches for the symbol corresponding to
an entry point address, it gets the
Hi David,
[auto build test ERROR on v4.6-rc1]
[also build test ERROR on next-20160331]
[cannot apply to tip/x86/core]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Richard-Weinberger
Hi David,
[auto build test ERROR on v4.6-rc1]
[also build test ERROR on next-20160331]
[cannot apply to tip/x86/core]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Richard-Weinberger
The eSDHC of T4240-R1.0-R2.0 has incorrect vender version and spec version.
Acturally the right version numbers should be VVN=0x13 and SVN = 0x1.
This patch adds the GUTS driver support for eSDHC driver to get SVR(System
version register). And fix host version to avoid that incorrect version
Move mpc85xx.h to include/linux/fsl and rename it to svr.h as
a common header file. It has been used for mpc85xx and it will
be used for ARM-based SoC as well.
Signed-off-by: Yangbo Lu
Acked-by: Wolfram Sang
---
Changes for v2:
- None
Changes for
Move mpc85xx.h to include/linux/fsl and rename it to svr.h as
a common header file. It has been used for mpc85xx and it will
be used for ARM-based SoC as well.
Signed-off-by: Yangbo Lu
Acked-by: Wolfram Sang
---
Changes for v2:
- None
Changes for v3:
- None
Changes for v4:
The eSDHC of T4240-R1.0-R2.0 has incorrect vender version and spec version.
Acturally the right version numbers should be VVN=0x13 and SVN = 0x1.
This patch adds the GUTS driver support for eSDHC driver to get SVR(System
version register). And fix host version to avoid that incorrect version
Move guts devicetree doc to Documentation/devicetree/bindings/soc/fsl/
since it's used by not only PowerPC but also ARM. And add a specification
for 'little-endian' property.
Signed-off-by: Yangbo Lu
---
Changes for v2:
- None
Changes for v3:
- None
Changes for
Move guts devicetree doc to Documentation/devicetree/bindings/soc/fsl/
since it's used by not only PowerPC but also ARM. And add a specification
for 'little-endian' property.
Signed-off-by: Yangbo Lu
---
Changes for v2:
- None
Changes for v3:
- None
Changes for v4:
-
Add the dts node for device configuration unit that provides
general purpose configuration and status for the device.
Signed-off-by: Yangbo Lu
---
Changes for v2:
- None
Changes for v3:
- None
Changes for v4:
- None
Changes for v5:
- Added this
This patchset is used to fix a host version register bug in the T4240-R1.0-R2.0
eSDHC controller. To get the SoC version and revision, it's needed to add the
GUTS driver to access the global utilities registers.
So, the first three patches are to add the GUTS driver.
The following two patches are
Add the dts node for device configuration unit that provides
general purpose configuration and status for the device.
Signed-off-by: Yangbo Lu
---
Changes for v2:
- None
Changes for v3:
- None
Changes for v4:
- None
Changes for v5:
- Added this patch
Changes for
This patchset is used to fix a host version register bug in the T4240-R1.0-R2.0
eSDHC controller. To get the SoC version and revision, it's needed to add the
GUTS driver to access the global utilities registers.
So, the first three patches are to add the GUTS driver.
The following two patches are
Hi Boris,
[auto build test ERROR on spi/for-next]
[also build test ERROR on v4.6-rc1 next-20160331]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Boris-Brezillon/scatterlist-sg_table-from
Hi Boris,
[auto build test ERROR on spi/for-next]
[also build test ERROR on v4.6-rc1 next-20160331]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Boris-Brezillon/scatterlist-sg_table-from
On Wed, Mar 30, 2016 at 02:47:48PM +0200, Cyrille Pitchen wrote:
> Hi all,
>
> [...]
> > But this is interesting: I see the latest datasheet for Spansion
> > s25fl064k says it supports the Block Protect bits in the Status
> > Register, so presumably *some* version of s25fl064k should support
> >
On Wed, Mar 30, 2016 at 02:47:48PM +0200, Cyrille Pitchen wrote:
> Hi all,
>
> [...]
> > But this is interesting: I see the latest datasheet for Spansion
> > s25fl064k says it supports the Block Protect bits in the Status
> > Register, so presumably *some* version of s25fl064k should support
> >
1 - 100 of 2460 matches
Mail list logo