From: Radha Mohan Chintakuntla
This patch series adds MDIO support to ThunderX NIC driver by making use
of existing mdio-octeon driver. In the process modified the mdio-octeon
driver to work on both Octeon and ThunderX platforms.
Radha Mohan Chintakuntla (3):
net: mdio-octeon: Modify driver
Hi Daniel,
On Fri, 2015-07-24 at 19:18 +0800, Daniel Kurtz wrote:
> On Fri, Jul 24, 2015 at 11:02 AM, James Liao
> wrote:
> > +static const struct mtk_gate_regs cg_regs_4_8_0 = {
>
> All of these regs tables can be __initconst.
It will be added in next patch.
Best regards,
James
--
To
On 27-07-15, 16:48, Bartlomiej Zolnierkiewicz wrote:
> s/will not/will now/ ?
> Probably doesn't matter currently but how's about:
>
> list_dev->dev = dev;
> list_add_rcu(_dev->node, _opp->dev_list);
> Otherwise:
>
> Reviewed-by: Bartlomiej Zolnierkiewicz
On 27-07-15, 23:56, Rafael J. Wysocki wrote:
> OK, I've just seen that patch, but it doesn't modify bus_probe_device()
> AFAICS.
Why is bus_probe_device() required to be modified?
I wrote this patch to propagate -EPROBE_DEFER from the ->init()
callback, which is called from
Hi,
Thanks for the review.
(2015/07/27 23:34), Michal Hocko wrote:
> On Mon 27-07-15 10:58:50, Hidehiro Kawai wrote:
> [...]
>> diff --git a/arch/x86/kernel/nmi.c b/arch/x86/kernel/nmi.c
>> index d05bd2e..5b32d81 100644
>> --- a/arch/x86/kernel/nmi.c
>> +++ b/arch/x86/kernel/nmi.c
>> @@ -230,7
Hi Shawn,
> -Original Message-
> From: Shawn Guo [mailto:shawn...@kernel.org]
> Sent: Tuesday, July 28, 2015 9:50 AM
> To: Wang Huan-B18965
> Cc: shawn@linaro.org; linux-arm-ker...@lists.infradead.org; linux-
> ker...@vger.kernel.org; Wang Dongsheng-B40534; Wang Huan-B18965
> Subject:
On Mon, Jul 27, 2015 at 11:50 AM, Igor Plyatov wrote:
> Dear all,
>
> very often we observe issue with Ethernet cable detection during cable
> unplugging and plugging.
>
> We use Voipac i.MX51 SOMs (System On Modules). They are based on Freescale
> i.MX51 CPU with LAN7800 PHY in MII mode. The
In the cases where the gpio chip fails to acquire the current state an
error is reported back to gpio_keys. This is currently interpreted as if
the line went high, which just confuses the developer.
This patch introduces an error print in this case and skipps the
reporting of a input event; to
As gpio_keys_setup_key() only operates on the device, pass a pointer to
this from the probe instead of a platform_device and make the usage
consistent. Also make probe() more consistent by dropping the local copy
of the device pointer.
Signed-off-by: Bjorn Andersson
---
On Wed, Jul 15, 2015 at 03:40:11PM +0800, Alison Wang wrote:
> Add ftm0 node, cause of ftm0 can be set as a alarm before system
> going to deep sleep.
>
> Signed-off-by: Wang Dongsheng
> Signed-off-by: Alison Wang
> ---
> Changes since v1:
> - Add my SoB.
> - Use "ARM:" as subject prefix.
>
>
Hi Jakub Kiciński,
Jakub Kiciński 於 2015/7/25 下午 05:35 寫道:
Please make sure you correct the rs485 configuration with what you can
actually support. Look at 8250_lpc18xx.c as an example. In your case
when the function returns it should have SER_RS485_ENABLED and one of
SER_RS485_RTS_ON_SEND |
On 07/27/2015 05:46 PM, Christopher Hall wrote:
* art_to_mono64
* art_to_rawmono64
* art_to_realtime64
Intel audio and PCH ethernet devices use the Always Running Timer (ART) to
relate their device clock to system time
Signed-off-by: Christopher Hall
---
arch/x86/Kconfig | 12
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
net/ipv4/ip_fragment.c
between commit:
0e60d245a0be ("inet: frag: change *_frag_mem_limit functions to take
netns_frags as argument")
from the net tree and commit:
14fe22e33462 ("Revert "ipv4: use skb coalescing
On Mon, Jul 27, 2015 at 02:29:59PM -0500, Shenwei Wang wrote:
> diff --git a/drivers/irqchip/irq-imx-gpcv2.c b/drivers/irqchip/irq-imx-gpcv2.c
> new file mode 100644
> index 000..3084f16
> --- /dev/null
> +++ b/drivers/irqchip/irq-imx-gpcv2.c
> @@ -0,0 +1,254 @@
> +/*
> + * Copyright (C) 2015
From: Igor Plyatov Sent: Monday, July 27, 2015 10:51 PM
> To: linux-kernel@vger.kernel.org; net...@vger.kernel.org
> Cc: Florian Fainelli; Joe Perches; Zhou Luwei-B45643; Duan Fugang-B38611;
> Richard Cochran; David S. Miller; Uwe Kleine-König; Estevam Fabio-R49496;
> Lothar Waßmann; Li
Given that some features were added (/dev/toshiba_acpi device), some
clean-ups and minor changes, bump the driver version to 0.23.
Signed-off-by: Azael Avalos
---
drivers/platform/x86/toshiba_acpi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Currently the driver prints "*not supported" if any of the features
queried are in fact not supported, let us print the available
features instead.
This patch removes all instances pr_info printing "*not supported",
and add a new function called "print_supported_features", which will
print the
This patch changes the default return value of the driver *{get, set}
functions from 0 (success) to -EIO, since the driver default error
value is -EIO.
All the functions now check for TOS_FAILURE, TOS_NOT_SUPPORTED and
TOS_SUCCESS.
On TOS_FAILURE a pr_err message is printed informing the user of
These patches changes the *{get, set} and *available functions,
changes the printed messages of the supported features and bumps the
driver version to 0.23.
Changes since v1:
- Fixed typos in patch 01 description and use newly created
*led_registered variables to unregister leds
- Adapt *{lcd,
This patch adds a new function named "set_fan_status" to complement
its get* counterpart, as well as to avoid code duplication between
"fan_proc_write" and "fan_store".
Also, both functions (get*, set*) are now checking for TOS_FAILURE,
TOS_NOT_SUPPORTED and TOS_SUCCESS (to be on par with the
This patch changes the *available functions return type from int to
void.
The checks for support of their respective features are done inside
such functions and there was no need to return anything as we can
flag the queried feature as supported inside these functions.
The code was adapted
On Mon, Jul 27, 2015 at 06:42:40PM +0200, Stefan Agner wrote:
> The eigth revision fixes some rough spots in the device trees.
>
> More information and the full test log of earlier patchset version
> can be found in the cover letter of the last revision v6:
>
On 2015/7/27 16:23, Michal Simek wrote:
On 07/27/2015 10:04 AM, Shawn Lin wrote:
This patch adds the interface to get quirks from dts, and
there is no need to assign different quirks by condition statement
of arasan IP version.
Signed-off-by: Shawn Lin
---
On Mon, Jul 27, 2015 at 06:42:43PM +0200, Stefan Agner wrote:
> Signed-off-by: Bill Pringlemeir
> Signed-off-by: Stefan Agner
Acked-by: Shawn Guo
> ---
> .../devicetree/bindings/mtd/vf610-nfc.txt | 45
> ++
> 1 file changed, 45 insertions(+)
> create mode
On Mon, Jul 27, 2015 at 06:24:26PM +, Shenwei Wang wrote:
> > > @@ -87,6 +87,8 @@ obj-$(CONFIG_SOC_IMX7D) += mach-imx7d.o
> > >
> > > ifeq ($(CONFIG_SUSPEND),y)
> > > AFLAGS_suspend-imx6.o :=-Wa,-march=armv7-a
> > > +AFLAGS_suspend-imx7.o :=-Wa,-march=armv7-a
> > > +obj-$(CONFIG_IMX_GPCV2)
On 07/22/15 at 04:47pm, Yinghai Lu wrote:
> On Tue, Jul 21, 2015 at 5:59 PM, Baoquan He wrote:
> >> That commit should only be used to workaround some systems that
> >> have partial iommu support.
> >
> > Those big servers mostly has hardware iommu. But they still can
> > enable swiotlb suport.
On 2015/7/27 23:19, Lars-Peter Clausen wrote:
On 07/27/2015 10:04 AM, Shawn Lin wrote:
This patch adds the interface to get quirks from dts, and
there is no need to assign different quirks by condition statement
of arasan IP version.
Signed-off-by: Shawn Lin
---
On Thu, Jul 23, 2015 at 3:52 PM, Florian Fainelli wrote:
> Our irq-bcm7120-l2 interrupt controller driver utilizes the same handler
> function for the different parent interrupts it services: UPG_MAIN, UPG_BSC
> for
> instance.
>
> The problem is that function reads the IRQSTAT register which
On Wed, Jul 22, 2015 at 10:04:45PM +0200, Sebastian Reichel wrote:
> The GPIOD API can be used from boardcode, so that
> the DT check can be removed. To avoid breaking
> existing boardcode, _optional() variant has been
> chosen. For completly removing the DT check, the
> regulator has also been
On Mon, Jul 27, 2015 at 02:50:15PM +, Shenwei Wang wrote:
> The following structure is currently used in both drivers. The members
> "gpc_base/
> wakeup_sources/enabled_irqs" are now shared to PM driver. And the macro
> IMR_NUM
> will be referred by both drivers too.
>
> struct
* counter_to_rawmono64
* counter_to_mono64
* counter_to_realtime64
Enables drivers to translate a captured system clock counter to system
time. This is useful for network and audio devices that capture timestamps
in terms of both the system clock and device clock.
Signed-off-by: Christopher Hall
* tsc_to_rawmono64
* tsc_to_realtime64
* tsc_to_mono64
These function build on the counter_to_* time translation function
specifically for TSC based system clock
Signed-off-by: Christopher Hall
---
arch/x86/include/asm/tsc.h | 5 +
arch/x86/kernel/tsc.c | 18 ++
2
This patch allows system and device time ("cross-timestamp") to be
performed by the driver. Currently, the cross-timestamping is performed
in the PTP_SYS_OFFSET ioctl. The PTP clock driver reads gettimeofday()
and the gettime64() callback provided by the driver. The cross-timestamp
is best effort
* art_to_mono64
* art_to_rawmono64
* art_to_realtime64
Intel audio and PCH ethernet devices use the Always Running Timer (ART) to
relate their device clock to system time
Signed-off-by: Christopher Hall
---
arch/x86/Kconfig | 12
arch/x86/include/asm/art.h | 42 ++
Next generation Intel platforms will have an Always Running
Timer (ART) that always runs when the system is powered and
is available to both the CPU and various on-board devices.
Initially, those devices include audio and network. The
ART will give these devices the capability of precisely
cross
Adds getsynctime64() callback which captures "raw" cross timestamp
between ART and Ethernet device clock
Translates captured ART to REALTIME clock
Signed-off-by: Christopher Hall
---
drivers/net/ethernet/intel/e1000e/defines.h | 7 +++
drivers/net/ethernet/intel/e1000e/ptp.c | 83
On 2015/07/28 0:16, Arnaldo Carvalho de Melo wrote:
> Em Mon, Jul 27, 2015 at 11:03:20PM +0900, Namhyung Kim escreveu:
>> On Fri, Jul 24, 2015 at 12:52:37PM -0300, Arnaldo Carvalho de Melo wrote:
If we agreed to extend the event format, I'd like to keep it simple
and to make it optional
On Mon, Jul 27, 2015 at 5:35 PM, H. Peter Anvin wrote:
> However... perhaps we can do the flags stuff first? There are certainly a
> ton of changes we ought to do.
>
Fine with me. Flags are probably more generally useful, especially
because of the silly lack of output constraints on asm goto.
On 28.07.2015 06:24, Javier Martinez Canillas wrote:
> Hello Michal,
>
> The patch looks good to me, just one small comment below.
>
> On Mon, Jul 27, 2015 at 10:11 PM, Michal Suchanek wrote:
>> Although there is only one choice of chipselect it is necessary to
>> specify it. The driver cannot
However... perhaps we can do the flags stuff first? There are certainly a ton
of changes we ought to do.
On July 27, 2015 4:58:29 PM PDT, Andy Lutomirski wrote:
>On Mon, Jul 27, 2015 at 4:56 PM, H. Peter Anvin wrote:
>> Sure... but now you have to wrap things in stac/clac. I'm not sure I
On Mon, Jul 27, 2015 at 4:43 PM, Luis R. Rodriguez wrote:
> On Mon, Jul 27, 2015 at 04:31:09PM -0700, Dan Williams wrote:
>> On Mon, Jul 27, 2015 at 4:17 PM, Luis R. Rodriguez wrote:
>> > On Fri, Jul 24, 2015 at 10:38:42PM -0400, Dan Williams wrote:
>> >> Existing users of ioremap_cache() are
He Kuang writes:
> Function find_module_all() searches for module by name and must be
> called with module_mutex. module_kallsyms_lookup_name() calls it without
> this mutex which emits a warning message (CONFIG_LOCKDEP=y) by failed
> assertion for testing this module_mutex lock, as following:
>
simple_strtoul() is deprecated; replace with kstrtoul() and kstrtouint().
Return an error if the value passed to the sysfs attribute is not
a number.
Drop the definition of strtoul() since it is no longer needed.
Signed-off-by: Guenter Roeck
---
v2: An additional use of strtoul() was introduced
2015-07-27 오후 10:58에 Vlastimil Babka 이(가) 쓴 글:
On 07/13/2015 10:35 AM, Gioh Kim wrote:
From: Gioh Kim
Migration is completely generalized so that migrating mobile page
is processed with lru-pages in move_to_new_page.
Signed-off-by: Gioh Kim
Acked-by: Rafael Aquini
Why not just fold
On Mon, Jul 27, 2015 at 4:55 PM, Vlastimil Babka wrote:
On 07/13/2015 10:35 AM, Gioh Kim wrote:
From: Gioh Kim
Add framework to register callback functions and check page mobility.
There are some modes for page isolation so that isolate interface
has arguments of page address and
On 06/16/2015 06:00 PM, Stephen Boyd wrote:
> Every tracepoint creates two functions, the usual one 'trace_*()'
> and the rcuidle one 'trace_*_rcuidle()'. Add regex for the
> rcuidle variant so that we can jump to the tracepoints that use
> rcuidle.
>
> Cc: Steven Rostedt
> Signed-off-by: Stephen
During unbinding the driver was dereferencing a pointer to memory
already freed by power_supply_unregister().
Driver was freeing its internal description of battery through pointers
stored in power_supply structure. However, because the core owns the
power supply instance, after calling
Hi Linus,
Could you please pull the following bug-fix patches?
Thanks,
The following changes since commit 33b40178cb3bd75294d1a758b3f509a0d38682ab:
Merge branch 'for-linus' of git://git.kernel.dk/linux-block (2015-07-24
17:00:04 -0700)
are available in the git repository at:
On at least one platform the kernel prints a warning on resume saying
"Unbalanced IRQ 37 wake disable". This is because enable_irq_wake in the
suspend function is failing. This patch checks to see if the call to
enable_irq_wake succeeded before calling disable_irq_wake.
Signed-off-by: Andrew
ngs settle [1]. This v3 series adds these define callers to
help get this merged at any point in time, so its doesnt' have to wait
to go in to the very last minute. This series was rebased on top of
linux-next next-20150727.
[0] http://lkml.kernel.org/r/20150601085332.ga14...@gmail.co
From: "Luis R. Rodriguez"
dma_alloc_writecombine()'s call and return value check is tangled in all
in one call. Untangle both calls according to kernel coding style.
Signed-off-by: Luis R. Rodriguez
Cc: Dan Williams
Cc: dmaeng...@vger.kernel.org
Cc: Vinod Koul
Cc: x...@kernel.org
Link:
From: "Luis R. Rodriguez"
Rename dma_*_writecombine() to dma_*_wc(), so that the naming
is coherent across the various write-combining APIs.
Also provide a mapping for old API users, at least for one
release. We can remove the old mapping names later after this
merged on one release.
The
There are certainly applications. That just isn't one of them.
On July 27, 2015 4:58:29 PM PDT, Andy Lutomirski wrote:
>On Mon, Jul 27, 2015 at 4:56 PM, H. Peter Anvin wrote:
>> Sure... but now you have to wrap things in stac/clac. I'm not sure I
>see the point since the code is already
On Mon, Jul 27, 2015 at 4:56 PM, H. Peter Anvin wrote:
> Sure... but now you have to wrap things in stac/clac. I'm not sure I see the
> point since the code is already pretty much optimal.
Ick. I forgot about that.
It would benefit all the users who aren't using the _ex functions,
though.
On Sat, Jul 18, 2015 at 05:42:42AM +0200, Ingo Molnar wrote:
>
> * Luis R. Rodriguez wrote:
>
> > On Thu, Jul 09, 2015 at 06:34:22PM -0700, Luis R. Rodriguez wrote:
> > > From: "Luis R. Rodriguez"
> > >
> > > Ingo,
> > >
> > > You had asked for this to be kept in my tree until the end of the
Dear Sir/ Madam.
Are You In Financial Crisis And You Need a Loan If Yes Kindly Contact Us At 2%
Interest Rate From Minimum of 3000 to Maximum 100,000,000. In Any Currency
Around The World
(BORROWERS DETAILS)
(1) NAME:
(2) SEX:
(3) COUNTRY:
(4) STATE:
(5) ADDRESS:
(6) LOAN AMOUNT:
(7) LOAN
Sure... but now you have to wrap things in stac/clac. I'm not sure I see the
point since the code is already pretty much optimal.
On July 27, 2015 4:49:46 PM PDT, Andy Lutomirski wrote:
>On Mon, Jul 27, 2015 at 4:46 PM, H. Peter Anvin wrote:
>> Sure, but that is different than getting rid of
Now get_res_add_size and get_res_add_align all have same printout
from res_to_dev_res(), and it is confusing.
Move out debug messages printout from res_to_dev_res(),
and later we will reuse res_to_dev_res() in other functions.
Signed-off-by: Yinghai Lu
---
drivers/pci/setup-bus.c | 34
Current code try to get align as small as possible and use that to
align final size. But it does not handle resource that size is bigger
than align in optimal way, kernel only use max align for them.
For example:
when we have resources with align/size: 1M/2M, 512M/512M,
bus resource
The COSM client driver running on the MIC cards is implemented as a
kernel mode SCIF client. It responds to a "shutdown" message from the
host by triggering a card shutdown and also communicates the shutdown
or reboot status back the host. It is also responsible for syncing the
card time to that
Now res_to_dev_res() does not print out debug message anymore, so
reuse it in reassign_resource_sorted().
Signed-off-by: Yinghai Lu
---
drivers/pci/setup-bus.c | 11 +--
1 file changed, 1 insertion(+), 10 deletions(-)
diff --git a/drivers/pci/setup-bus.c b/drivers/pci/setup-bus.c
index
Hi,
After 5b28541552ef (PCI: Restrict 64-bit prefetchable bridge windows
to 64-bit resources), we have several reports on resource allocation
failure, and we try to fix the problem with resource clip, and get
more problems.
One is realloc fail with two graphics cards above 4G.
One is from sparc
We don't do sorting in those functions anymore, so change "sort" to "check"
instead.
Signed-off-by: Yinghai Lu
---
drivers/pci/setup-bus.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/pci/setup-bus.c b/drivers/pci/setup-bus.c
index 6642a60..292f2a5
Now __sort_resources, and pdev_sort_resources all have sorting
code.
As we are going to call __sort_resources several places later, so
choose to keep __sort_resources, and remove related code in
pdev_sort_resources.
Signed-off-by: Yinghai Lu
---
drivers/pci/setup-bus.c | 22
On Mon, Jul 27, 2015 at 4:46 PM, H. Peter Anvin wrote:
> Sure, but that is different than getting rid of the _ex forms.
>
If we did that and got rid of the _ex forms, though, then the code
that matters (the no-fault case) would just be a bunch of movs, right?
That's basically the same as the
On Mon, Jul 27, 2015 at 4:17 PM, Luis R. Rodriguez wrote:
> On Fri, Jul 24, 2015 at 10:38:42PM -0400, Dan Williams wrote:
>> Existing users of ioremap_cache() are mapping memory that is known in
>> advance to not have i/o side effects. These users are forced to cast
>> away the __iomem
Use res instead of dev_res->res.
Signed-off-by: Yinghai Lu
---
drivers/pci/setup-bus.c | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/drivers/pci/setup-bus.c b/drivers/pci/setup-bus.c
index 6dff258..06664db 100644
---
Move comment from caller to callee, as we will have one new caller
for alt_size support later.
Signed-off-by: Yinghai Lu
---
drivers/pci/setup-bus.c | 27 +++
1 file changed, 15 insertions(+), 12 deletions(-)
diff --git a/drivers/pci/setup-bus.c
Need to put aligned with max align before not aligned.
For example:
alt align/size: 8M/9M, 4M/8M
before this patch we have 8M/20M.
After this patch we will have 8M/17M.
Signed-off-by: Yinghai Lu
---
drivers/pci/setup-bus.c | 80 +++--
1 file changed,
On booting path, we don't pass realloc at first, and treat all optional just
as must, in some case we can smaller size/align with optional than must only.
04:00.0 has four child bridges: 05:01.0, 05:02.0, 05:03.0, 05:04.0
pref layout after booting path like followings:
pci :04:00.0: BAR 9:
Use new generic version skip_isa_ioresource_align() instead.
Signed-off-by: Yinghai Lu
---
drivers/pci/setup-bus.c | 17 +++--
1 file changed, 7 insertions(+), 10 deletions(-)
diff --git a/drivers/pci/setup-bus.c b/drivers/pci/setup-bus.c
index d4610a8..f8f89cd 100644
---
So we could unify calculate_iosize and calculate_memsize later.
when one bridge have several children devices, and every devices
have several io port resources and resource size < 0x400.
We need to check size, and add extra size to make sure bit8/9
to be zero.
Signed-off-by: Yinghai Lu
---
Same as patch for mmio (PCI: Don't add too much optional size for hotplug
bridge mmio), and this one is addressing io port.
It will compare must+optional with min_sum_size to get smaller
optional size.
Signed-off-by: Yinghai Lu
---
drivers/pci/setup-bus.c | 26 --
1
Since card side COSM functionality, to trigger MIC device shutdowns
and communicate shutdown status to the host, is now moved into a
separate COSM client driver, this patch removes this functionality
from the base MIC card driver. The mic_bus driver is also updated to
use the device index provided
On 27.07.2015 22:10, H.J. Lu wrote:
> Hi,
>
> This commit:
>
> commit 297d716f6260cc9421d971b124ca196b957ee458
> Author: Krzysztof Kozlowski
> Date: Thu Mar 12 08:44:11 2015 +0100
>
> power_supply: Change ownership from driver to core
>
> Change the ownership of power_supply
It will not hold lock, so we could use it in other functions that
hold the resource lock already.
-v2: according to Linus, using "bool lock" as parameter
aka "conditionally take lock" is *wrong*.
Signed-off-by: Yinghai Lu
Acked-by: Linus Torvalds
---
kernel/resource.c | 70
If any bridge up to root only have 32bit pref mmio, We don't need to
treat device non-pref mmio64 as as pref mmio64.
We need to move pci_bridge_check_ranges calling early.
for parent bridges pref mmio BAR may not allocated by BIOS, res flags
is still 0, we need to have it correct set before we
We should check size+size1 with min_size for io port.
For example, when hotplug bridge has two children bridges,
every child bridge will need 0x1000, so size1 will be 0x2000
and size is 0. The min_size for the hotplug bridge is 0x100.
with old version calculate_iosize, we get 0x3000 for final
size
If host bridge does not have mmio64 above 4G, We don't need to
treat device non-pref mmio64 as as pref mmio64.
Signed-off-by: Yinghai Lu
---
drivers/pci/setup-bus.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pci/setup-bus.c b/drivers/pci/setup-bus.c
index
For device resource PREF bit setting under bridge 64-bit pref resource,
we need to make sure only set PREF for 64bit resource, so set
IORESOUCE_MEM_64 for 64bit resource during of device resource flags
parsing.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=96261
Link:
On hotplug path, we can not touch sibling bridges that is out
side of the slot.
That could happen when BIOS does not assign some bridge BARs and
later can not assign resource to them in first try.
Check if fail dev is the parent bridge, then just use subordinate
bus instead use parent bus.
On Mon, Jul 27, 2015 at 04:31:09PM -0700, Dan Williams wrote:
> On Mon, Jul 27, 2015 at 4:17 PM, Luis R. Rodriguez wrote:
> > On Fri, Jul 24, 2015 at 10:38:42PM -0400, Dan Williams wrote:
> >> Existing users of ioremap_cache() are mapping memory that is known in
> >> advance to not have i/o side
Current code will always add 2M for hotplug bridge mmio even
there is child device under it.
For example:
40:03.0 --- 43:00.0 --- 44:02.0 -+- 45:00.0
\- 45:00.1
44:02.0 will need 1M as must for 45:00.0 and 45:00.1
When we calculate add_size for
ACK
> -Original Message-
> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On
> Behalf Of Alex Williamson
> Sent: Monday, July 27, 2015 4:19 PM
> To: intel-wired-...@lists.osuosl.org; Kirsher, Jeffrey T
> Cc: net...@vger.kernel.org; linux-kernel@vger.kernel.org
>
On Mon, Jul 27, 2015 at 03:03:12PM -0700, Kees Cook wrote:
> Hi Greg,
>
> Have you had a chance to look at this? I think we need to either
> include the ASLR improvements in stable or revert
> a87938b2e246b81b4fb713edb371a9fa3c5c3c86, which breaks existing
> userspace tools.
Not yet, it's behind
After we update size and alignment for must+optional resource, we
reorder them with new alignment, but this is only for STARTALIGN.
For SIZEALIGN type resource, after add back add_size, the alignment
get changed, so need to do the sorting like STARTALIGN type resources.
Also we need to reorder
ACK
> -Original Message-
> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On
> Behalf Of Alex Williamson
> Sent: Monday, July 27, 2015 4:19 PM
> To: intel-wired-...@lists.osuosl.org; Kirsher, Jeffrey T
> Cc: net...@vger.kernel.org; linux-kernel@vger.kernel.org
>
We need to reserve them before pci_bus_add().
During driver loading kernel will check if those reource get reserved.
On remove/rescan path, we will leave those fixed resource
not reserved, as we don't call pcibios_resource_survery() before
pci_assign_unassigned_bus_resources(), and that is
Find all suitable empty slots and pick one just fit, so we could save
the big slot for needed ones later when we have several pcie switches
and some bridges get assigned bios and we need to assign others in kernel.
Signed-off-by: Yinghai Lu
---
kernel/resource.c | 81
We will need to share that saved list for alt_size support.
Signed-off-by: Yinghai Lu
---
drivers/pci/setup-bus.c | 30 --
1 file changed, 16 insertions(+), 14 deletions(-)
diff --git a/drivers/pci/setup-bus.c b/drivers/pci/setup-bus.c
index 64ef516..1c0b4c5 100644
We check the realloc list, as list must be empty after allocation.
Separate the realloc list checking to another function.
Add checking that is missed in acpiphp driver.
Signed-off-by: Yinghai Lu
Cc: "Rafael J. Wysocki"
Cc: Len Brown
Cc: linux-a...@vger.kernel.org
---
We try to assign must+optional at first, and we only accept the result if
all resources get allocated. Otherwise will release assigned in the list,
and try to assign must and expand to optional.
We have to do that to make sure any must has priority than any optional
addon.
When that happens, we
to take alt_size, alt_align.
preparation patch for alt_size support.
Signed-off-by: Yinghai Lu
---
drivers/pci/setup-bus.c | 51 ++---
1 file changed, 31 insertions(+), 20 deletions(-)
diff --git a/drivers/pci/setup-bus.c b/drivers/pci/setup-bus.c
Skip allocated resource in the list, as pci_assign_resource()
only can handle not assigned resource. And we could have
assigned resource already in the list before alt_size trying.
Signed-off-by: Yinghai Lu
---
drivers/pci/setup-bus.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
If the bridge does not support hotplug or no child with sriov support
we could get out early and don't try must+optional allocation.
Also in the loop that update res with optional add info, skip resource
that add_size is 0.
Signed-off-by: Yinghai Lu
---
drivers/pci/setup-bus.c | 32
>From 5b2854155 (PCI: Restrict 64-bit prefetchable bridge windows to 64-bit
resources), we change the logic for pref mmio allocation:
When bridge pref support mmio64, we will only put children pref
that support mmio64 into it, and will put children pref mmio32
into bridge's non-pref mmio32.
That
We still get "no compatible bridge window" warning on sparc T5-8
after we add support for 64bit resource parsing for root bus.
PCI: scan_bus[/pci@300/pci@1/pci@0/pci@6] bus no 8
PCI: Claiming :00:01.0: Resource 15: 8001..8004afff
[220c]
PCI: Claiming :01:00.0:
From: Sudeep Dutt
This patch implements the SCIF mmap/munmap interface. A similar
capability is provided to kernel clients via the
scif_get_pages()/scif_put_pages() APIs. The SCIF mmap interface
queries to check if a window is valid and then remaps the local
virtual address to the remote
So could reallocate pref mmio64 above 4G later.
Signed-off-by: Yinghai Lu
---
arch/x86/include/asm/pci_x86.h | 1 +
arch/x86/pci/common.c | 3 +++
arch/x86/pci/i386.c| 56 ++
3 files changed, 39 insertions(+), 21 deletions(-)
diff
From: Sudeep Dutt
This patch adds the SCIF kernel node QP control messages required to
enable SCIF RMAs. Examples of such node QP control messages include
registration, unregistration, remote memory allocation requests,
remote memory unmap and SCIF remote fence requests.
The patch also updates
101 - 200 of 2262 matches
Mail list logo