This patch improve handling of write behind in the following ways:
- introduce behind master bio to hold all write behind pages
- fast clone bios from behind master bio
- avoid to change bvec table directly
- use bio_copy_data() and make code more clean
Suggested-by: Shaohua Li <shli@fb.com>
Signed-off-by: Ming Lei <tom.leiming@gmail.com>
Signed-off-by: Shaohua Li <shli@fb.com>
The 'offset' local variable can't be changed inside the loop, so
move it out.
Signed-off-by: Ming Lei <tom.leiming@gmail.com>
Signed-off-by: Shaohua Li <shli@fb.com>
Turns out we can use bio_copy_data in raid1's write behind,
and we can make alloc_behind_pages() more clean/efficient,
but we need to partial version of bio_copy_data().
Signed-off-by: Ming Lei <tom.leiming@gmail.com>
Reviewed-by: Jens Axboe <axboe@fb.com>
Signed-off-by: Shaohua Li <shli@fb.com>
Now one page array is allocated for each resync bio, and we can
retrieve page from this table directly.
Signed-off-by: Ming Lei <tom.leiming@gmail.com>
Signed-off-by: Shaohua Li <shli@fb.com>
Now we allocate one page array for managing resync pages, instead
of using bio's vec table to do that, and the old way is very hacky
and won't work any more if multipage bvec is enabled.
The introduced cost is that we need to allocate (128 + 16) * raid_disks
bytes per r1_bio, and it is fine because the inflight r1_bio for
resync shouldn't be much, as pointed by Shaohua.
Also the bio_reset() in raid1_sync_request() is removed because
all bios are freshly new now and not necessary to reset any more.
This patch can be thought as a cleanup too
Suggested-by: Shaohua Li <shli@kernel.org>
Signed-off-by: Ming Lei <tom.leiming@gmail.com>
Signed-off-by: Shaohua Li <shli@fb.com>
This patch gets each page's reference of each bio for resync,
then r1buf_pool_free() gets simplified a lot.
The same policy has been taken in raid10's buf pool allocation/free
too.
Signed-off-by: Ming Lei <tom.leiming@gmail.com>
Signed-off-by: Shaohua Li <shli@fb.com>
Now resync I/O use bio's bec table to manage pages,
this way is very hacky, and may not work any more
once multipage bvec is introduced.
So introduce helpers and new data structure for
managing resync I/O pages more cleanly.
Signed-off-by: Ming Lei <tom.leiming@gmail.com>
Signed-off-by: Shaohua Li <shli@fb.com>
Both raid1 and raid10 share common resync
block size and page count, so move them into md.h.
Signed-off-by: Ming Lei <tom.leiming@gmail.com>
Signed-off-by: Shaohua Li <shli@fb.com>
All bio_add_page() is for adding one page into resync bio,
which is big enough to hold RESYNC_PAGES pages, and
the current bio_add_page() doesn't check queue limit any more,
so it won't fail at all.
remove unused label (shaohua)
Signed-off-by: Ming Lei <tom.leiming@gmail.com>
Signed-off-by: Shaohua Li <shli@fb.com>
multi_v7_defconfig, so that we can switch to it by default in the
following release.
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEE/JuuFDWp9/ZkuCBXtdYpNtH8nugFAljRfpgACgkQtdYpNtH8
nuiSyhAArtREuNR38T9LIBdl6lbwkej62AGIRXAnAk4bS2fJksep8ZV/XmehNBwT
NYjkugRiyoqG2kem5jifOzWpZad5V1Ta66dI1kLiEnduHsngDTrX9sqHTV4RhIpA
cE/+GlsbC37uCjBYwlHOjwjPR3S/enkIXeia+WCOhiylXu/SxXY58Er+PSdUFJSr
jM+ejxYlFMoH7E6SDyW7OuWbShLJO4yYneeK6P8Sg24uEbi8lB3OguGene/F5B/9
IbP7EpIJYPK/yCtaUFndb87WKE02edJ3b/djIuAj7S/9fZ+sQkOHAl+2ORJXSZk+
mlmKsYXme+bJPw73I2FNEEQ8/yf1aAquiS4ixVVQE/qdC6rR50NLPrtb7wRB3er6
BlGnjTsjpl44uVHVnp8CXN2JAxlY3L40oT/vkTc8Qt+lTptK6YPjFLn0lKHkTkOL
rDCPnIVqfMoGMzcxNmugOxGv58O7xZI20cURGmrGdWk3uGxCQlVWP3lfjB9rIPwx
2yx/qNyO66PrYyiGB/aYf6/X9L5ochbVpNbwk4gtmlfHTG0o6vO4m2pawpR0Ckrf
g2nM5HiX1pcWJ/uoMYmQP82YakE1vL9hFTGny6OPd749R9+9pMt2Wj1K8bVqCmHi
An+yFqftw0Cb2OUHli86gYuipnazQu8zgInfLT70/qPEzX+VQYw=
=JXRd
-----END PGP SIGNATURE-----
gpgsig -----BEGIN PGP SIGNATURE-----
iQIcBAABCAAGBQJY1VPvAAoJEIfQlpxEBwcEcqAQAJUr6cay8ElI2mlbYHI0PY9T
NTBE2N7azqHpxwN7KmQKY4/Vzv/gAZNym9uCyI1yypJIoojmMVP3FzTYRVhUhGC+
bc+iQY+NpiwKWk5jg0x38bjBQ74eSIPeYZyexBN1pl28AZigJkfdt+OvJrBqbhod
AVk3GE8pLAq+HsMegICD7aadqTqn/0UNynKN7U4t0NeJar7T/QsxkH34DTdWdcat
4ue93fOFRDLOx5RLEBRtmLJNn4W4jJYpQ66rPIbfXm2oQi2RQTpOskbdSF5SYYcx
VfTrA/LWq1cUZ6aS34ZhFAmWo2+sRsj4aLoMR3ea8I44cGhjQpJ+3XaFEYkua6WB
Ron9Tz5ESuICu7S2mqpHp6+gghNI8CcImaawgMvUNH95uTTnYFrfYwsaAuGLlTGV
vG0FVqDBA1sXtqzvGhmnW9EHxAAQXfPOGjwzOzYSZPoAUuBvNCfZgYRhCuCgFT8/
TraAJnjkQ3gAqCVQLE89omS9ppw0lxoyaLqk96PH1dgC9tG0uW6MjumfovkPtmDH
fYlUIeE03W7c8EwIEXC2leZAS7xxk+iBGYyj1AMEmU1B7saDhdjiwXWCI4AC41dQ
+b0G6jFm8RtaeZ54CHZ8XMSNMca8JpspdTi6TwBZtwdiFDnotrTgoD53VFgDbpNS
k5rvjUzPV4jwq25RoHv1
=3ZMH
-----END PGP SIGNATURE-----
Merge tag 'bcm2835-defconfig-64-next-2017-03-21' into defconfig-arm64/next
This pull request starts building the new SDHOST MMC driver on
multi_v7_defconfig, so that we can switch to it by default in the
following release.
Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
and starts building the new SDHOST MMC driver on multi_v7_defconfig,
so that we can switch to it by default in the following release.
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEE/JuuFDWp9/ZkuCBXtdYpNtH8nugFAljRfm0ACgkQtdYpNtH8
nuhYPA//dPiynAoyS6+Rc4bbTDBFcbAL1Ta18bw4XyzffD7odyQuXvmAT++70ONE
OXva+2lVCb5N/VXT02NsVZnQdRzFKB2z2QUYnuUnSYLnJDbPND8sSNKK9tEGuFMC
LF7CprMXwuUpgfDELZQbS8Kz2nLdg5PjkSYHLM6TslsJQ8PerLX7rrdMeXLSHCyl
+p7lBXz6QHmmYZPuaXR7k9jBdcxyFyl5ly58Aqd9jDbLAok+z6M7VOe2NSb7Af56
xNFkumHt0t9KlvdJr0uYKM6g83mQHfrQH7h8GnDk2EztnpOdFkMsVVJsgTJkBX9b
d9sVV2r5Iua+1hnvww+Luh1B1WXTJGfpiHwHvVt20xCRVj5NUUFEs5ctTz9acLae
1OMgu4kb5aTRv0Xc5n9zX7p/Dj0Vj7HKk0dX4gPPBm3t7HuiFUTtsYPaWltLfPIJ
Xg5gnxdp6MCaV303IRpcRwXSfroiiu9A9CmppI+at9IkobH2YHs7D+Ow3tDHth29
4vJCLaNkrABQ1sRmE77NEHwG7kuLQ77iAOYR+Mex8OTzlLAXk0E4jNLl/q1ZqVQ3
lOlxaufHjC+pSUnNIz6t/2uoHyPQ9maLOBTQZ235f4vaA+Mt2ZppH3ALVWePPGZU
k9ywjXHKimn1UX57djMKbL7HS7azcSnUrF/sSI+KFsvm0IsEggc=
=BgLm
-----END PGP SIGNATURE-----
gpgsig -----BEGIN PGP SIGNATURE-----
iQIcBAABCAAGBQJY1VO/AAoJEIfQlpxEBwcElfkP/1onb9IF5Rt8iIhf6C6yHAsR
HAvPMRZnFtoI9F203NMHk4m0JBBiRnQHWvIQoD5gVV2scJZYvaLDesvXHlNt+CDE
WKMPbLrT0BPAnCwCA8GJPotygZi2Lc4O0NKlkuu/mwUyTpNBYnOdS5NV4I8xPSK5
mifaQlwLXHIEAmElSj5FxvGnNXKrGDlVBbJhWWVVdPgN83uXDB2jglu6rrsPE9r9
XPLXR6jI1mS6NTKQujPnxvtb0eKbBRzdVQfzOtpw1qWfgqJrkS2YPS2n8Y9zAgqD
ZEWJeCvrF4G5YOFX84EUvRSFmGBhOugiYjHxaCDnOyjCq8EJHrk4cgx2K6xJ98dn
wzpLBMEvwHQiBVbhVaLa+3OH8A/9/VMgIv0oopJgqsFpl6XitL4BxZ+5q16Dba90
EadMt5T+Q731Xxvt8UK0s0xLIu+p8ekSRKlv/rcyvltgHjhaxJCGceks+lqsz5Qf
LW4vhdP2khfotR5DQ0MQ2Rl3EmmGEg7qXhlA8nrgLRl+E99NYXFxQlk+OAEB565M
XHzcHG/UklpUA7wBzM8fIKBPbhgqlf4Fx6x3ACQ4apS3KY0XnZhOj8gHSMAcpj6k
5PWVaca5p72l6ByQ/SA05aIvnbOXqPrUcDv2eacDgXs0RNJtg92inYfVgif7rhOy
UVHPAC08x/bX89Mgpr+x
=SIyu
-----END PGP SIGNATURE-----
Merge tag 'bcm2835-defconfig-next-2017-03-21' into defconfig/next
This pull request fixes graphics in bcm2835_defconfig by enabling CMA,
and starts building the new SDHOST MMC driver on multi_v7_defconfig,
so that we can switch to it by default in the following release.
Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Raspberry Pi, and nodes to describe the DSI and SDHOST hardware
modules (which are still disabled by default).
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEE/JuuFDWp9/ZkuCBXtdYpNtH8nugFAljRfb8ACgkQtdYpNtH8
nugDzhAApB5GSQOTsWUWijmrHVHjEjHxWKRCitLIipN18EPRRJCGzulH/ZSs0DQN
jOxJadeuZPU7/My26gk40BVmMgE0v/9i+jKUQx6nMgpLzWPy/9XNAscH/vmqblNe
4GBmFCUbhOB++GWOxqnNw8AzvKXKSMKrAzS0Io/NxgeKkGWJHOk+vnx8p6QDXpI9
B8AoSUVfSRmQV/gwMMP44FPV3FrTmj9D+IY2zR62XMzaDkn3krdMqhZVn+LetiUx
A5MiRUIqiU1lKeydTe1GdtXtKyHhhknUSUe/poICRaumr0BLCYlPA54gWzwrEMd9
Cp3QCCaQ+dYQXtxVWgwtXQim8nRT6iVY4NjbXM3f9KoiVXQ6v9HgIcwyWU9wbqoL
pbQLltc4vuhJCXEnZmqumfA/TrB35UTaQ11fIYQK4YDVhNete3fNhbK2QwqRV5Om
/dlc/xVYZE9D8JSfuPZ4OjFrcz602QpX8MzIw3jjYirs+d6gVN5dmAjWI5GdzSeH
hM7Oh4IZdCxEIDTFSzu/qlvikAOt4CizeFA7JXobCJdR5+hNkpWbVFYncMJCxl6c
kHbpeXK/nRatGHcz0//0F2/1JSIo7fTQa7xxUjQHul4c/eTvCyIFd/mDQmVeGfBR
a7fYgDvuYC+OHoetqgkP63kKrRAotohMbFur8hJit6cBmCGgvCo=
=bTSQ
-----END PGP SIGNATURE-----
gpgsig -----BEGIN PGP SIGNATURE-----
iQIcBAABCAAGBQJY1VOJAAoJEIfQlpxEBwcE7KoP/3B9blNn/T0vJwVkw0KxkKHL
nvgRLiu9Rnb103aZlPA89cXxa21E9bjb6fQIt+Oxvh4gg/+L1fKqId3Xah8x8gNw
FRuYZxbAKw0EmOgBT1cshLp3gKQhA2s2nTvt7BQzNvKFe2aBqTcZF98Y/8NTco25
7SmDvZCAzsAYUDPtxnAbHU+VrwhS3o8nVIDlWxlkULAU9chkBs6hCIpOR/0+dxgL
XXZUtrBphF4E9A4lW70QpFjN7cdOuRBFGS1MG2VcIw67s7CDXP47RWh8V9RVWRmk
gN5uUuxGfMN5YHhULNUF8sK0dhd4LXKDbRDyTzBlkKbHsYWiHk9wKVAzYajIi+w9
F8z6o7sOugmPuGxUI+lH1pNo5QTvVMb6rHI7+T+XoM3ElnB+SJUaboJhwZLk2zj1
7P21Gl47XJT0qhtoBv1HLxT/+zOp3jQJeWEpqEejYUW9ebFgYicy2xLZVnMGlyXQ
+Mqc2wX5VmtrnvWZjH820ncBoOs6MBgu+hKDiPpiuQxgsaDb8UyQG9qVwAbWKVz0
5Pqx/Yp9lhF2575Ucmz0IB54daQa35kvivnmpMYrcnMNM2rRlQ7Cau0ENOj7Zk3z
9OE4y/TMFaa8AfBOfdv634QFwR8kMkSCdxoYzAu5P7yuRBbD3946Q0wvgU8YMmaG
TpS93aglnjv5pzCdfq+a
=cLA3
-----END PGP SIGNATURE-----
Merge tag 'bcm2835-dt-next-2017-03-21' into devicetree/next
This pull request brings in the DT nodes for enabling HDMI audio on
Raspberry Pi, and nodes to describe the DSI and SDHOST hardware
modules (which are still disabled by default).
Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
The required number of dwords for semaphore emission on BDW RCS is 8,
not 6 - leading to ring buffer corruption and immediate GPU hangs when
using ringbuffer submission.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Link: http://patchwork.freedesktop.org/patch/msgid/20170324151724.32640-2-chris@chris-wilson.co.uk
Reviewed-by: Michał Winiarski <michal.winiarski@intel.com>
Initialize the ftrace records immediately after memory initialization, as
that is all that is required for the records to be created. This will allow
for future work to get function tracing started earlier in the boot process.
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Create an early_trace_init() function that will initialize the buffers and
allow for ealier use of trace_printk(). This will also allow for future work
to have function tracing start earlier at boot up.
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
please pull the following:
- Jon adds missing "dma-coherent" property to the Northstar 2 DTS include file
in order to fix both performance and cache problems for: PCIe, Ethernet,
PDC/mailbox, SATA3 and SDHCI
-----BEGIN PGP SIGNATURE-----
iQIcBAABCAAGBQJY0rXOAAoJEIfQlpxEBwcEcCwQAI6nyawZL32CW5cRKcDqHeVG
l7bZJEdfcYA6TojvIGhdWh4VGSb2sLJsB7cU+eAtdHxI55sp1YR1HMEv5GBNthiq
JKtwnVKWpaM6lbJGJnQwvGCzrGWSIXJH7KjPHh+Krb8ZV7GWQiJ3neEe3jh7Pp5u
KEWIin22AowWo/5Hk8reEOoei9E+zer6Bo8YI2SVQ426epXnCocHzfaVIMq28310
xzlhR8xFACoJTPJBJ8keyjL/9UYoge4Q1PM4VH89ti3juF4ELNGJP2yZyTbXWjOg
gHDbQ13KWxE6xvCZbRLkiyBkIL5MZ8xKsP6ePqFtNU4STnPvnenWoEpBuY+8+lmz
YOCoWf+TzyfvFV6BsnbnvBPE09tzeqtY43+kLOAsizqPY1+MzflDNW1MLBKRzQBV
yGI6NhNB8wgKtCrYAGAd4O+Mb1GkGigw/C7l+/L68aBNqwy3pfPEM1zkobX7sBUi
T+CjYQoF5ZUNx+p6cQfZFnr7ygC/iUyo7jODY9fTbCQ51PiTw1uMcOUmaV2DbQ2T
Fq4jZRTVRubzBlCTNG1hRPqycGoXzjRS/uGKOLX5+XqRNKUBfFzy+XNoGqRlSO9n
E6ef1ZbCO5GwxG6otgmlARHgCigSusKvfccQ9WWcB+1CegeCFSbyG1YzYkhQZ281
te/nPRCmU/Uq0YvUoogd
=5KXs
-----END PGP SIGNATURE-----
Merge tag 'arm-soc/for-4.11/devicetree-arm64-fixes' of http://github.com/Broadcom/stblinux into fixes
Pull "Broadcom arm64 Device Tree fixes for 4.11" from Florian Fainelli:
This pull request contains Broadcom ARM64-based SoCs Device Tree fixes for 4.11,
please pull the following:
- Jon adds missing "dma-coherent" property to the Northstar 2 DTS include file
in order to fix both performance and cache problems for: PCIe, Ethernet,
PDC/mailbox, SATA3 and SDHCI
* tag 'arm-soc/for-4.11/devicetree-arm64-fixes' of http://github.com/Broadcom/stblinux:
arm64: dts: NS2: Add dma-coherent to relevant DT entries
please pull the following:
- Jon fixes a reboot issue on most Northstar Plus platforms by adding the
"open-source" property to the "gpio-restart" Device Tree nodes
-----BEGIN PGP SIGNATURE-----
iQIcBAABCAAGBQJY0rfzAAoJEIfQlpxEBwcEzCAQALNT1HOloxI7D+Ki1w5/ANum
IsZIfzffFV/gJW1tZDhbLnNcPU+H8W9hGi3veAOihlbJSMHkEV5ECYzx9CImwLyg
0le6H68w4eZwJQ4ZCyyu3qXPjhic6v3Dtzw2nqvWytRAbcyGh8k8z6riVRucCXJU
wvzjARTga1u2UffvVsQEw6o7MQE0B+1KcqGh+g069IQVQzTjTxPGOvQF2hfqabUt
45x2w5wlUKGX+SodqweDzFQu1tKErjkt8EH5zvqjeMRGFxHaDFXw4FuRWrkzp9ic
gE+3d/IuHxYivNsPg90y029e+ihTTxPfT1cLRJkN7kbzBKYngH+/T1HLb7EFJbcO
/haqnevKaWp3MCwkpH4LDQ3akKIaZvbo16qdxCNvQ80biTwHqOo5e+roMyk9Y9Ka
vYw22yW0LfeRHPnkQBIBOwS9b31r2D9FePKRrkNFZXy0247w0TW4lSUovvnIdwTq
awBBBkTS56ovnjmU08/72DVj4JE2/3mwqkYHUfEXls4RA8oYF4maHSEZI/FF16/2
YiMVE9fBaRjLKXthxuVaMsGUz94QR2W9gaOq8UV5E/ZM9YCckR+J28mhHehV+S2U
jsDv3iXgLpnYOnBqdoXLbcHr9QFx0OtItgACs3AlYP0SMmUryXrPdzVUY9cQBjJR
drXgohtIcxX1j0CHxDWf
=CKev
-----END PGP SIGNATURE-----
Merge tag 'arm-soc/for-4.11/devicetree-fixes-2' of http://github.com/Broadcom/stblinux into fixes
Pull "Broadcom arm Device Tree fixes for 4.11 (part 2)" from Florian Fainelli:
This pull request contains Broadcom ARM-based SoCs Device Tree fixes for 4.11,
please pull the following:
- Jon fixes a reboot issue on most Northstar Plus platforms by adding the
"open-source" property to the "gpio-restart" Device Tree nodes
* tag 'arm-soc/for-4.11/devicetree-fixes-2' of http://github.com/Broadcom/stblinux:
ARM: dts: NSP: GPIO reboot open-source
Make the kerneldoc comment for usb_find_common_endpoints_reverse()
self-contained by adding a full description and removing the reference
to usb_find_common_endpoints().
Reported-by: kbuild test robot <fengguang.wu@intel.com>
Signed-off-by: Johan Hovold <johan@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
When a new event is queued while processing to resize the FIFO in
snd_seq_fifo_clear(), it may lead to a use-after-free, as the old pool
that is being queued gets removed. For avoiding this race, we need to
close the pool to be deleted and sync its usage before actually
deleting it.
The issue was spotted by syzkaller.
Reported-by: Dmitry Vyukov <dvyukov@google.com>
Cc: <stable@vger.kernel.org>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
The forcewake_get call in the guc_send_mmio function was added to
avoid getting and releasing forcewake on each register access.
While this makes sense, all GuC registers are in the blitter range
so no need to wake all the wells.
Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/1490366919-34715-1-git-send-email-daniele.ceraolospurio@intel.com
Reviewed-by: Sagar Arun Kamble <sagar.a.kamble@intel.com>
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
The arm64 defconfig covers the Allwinner A64 SoC boards quite well,
but USB support is not enabled.
Add the PHY config symbol to allow defconfig kernels to use USB.
Signed-off-by: Andre Przywara <andre.przywara@arm.com>
Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
This SATA controller is quite similar to the one present on the DA850
SoC, but the PHY configuration is different and it supports two HBA
ports.
The IP suffers from the same PMP issue the DA850 does - if we enable
PMP but don't use it - softreset fails. Appropriate workaround was
implemented in this driver as well.
Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
Add a host bridge driver for the Faraday Technology FPPCI100 host bridge,
used for Cortina Systems Gemini SoC (SL3516) PCI Host Bridge.
This code is inspired by the out-of-tree OpenWRT patch and then extensively
rewritten for device tree and using the modern helpers to cut down and
modernize the code to all new PCI frameworks. A driver exists in U-Boot as
well.
Tested on the ITian Square One SQ201 NAS with the following result in the
boot log (trimmed to relevant parts):
OF: PCI: host bridge /soc/pci@50000000 ranges:
OF: PCI: IO 0x50000000..0x500fffff -> 0x00000000
OF: PCI: MEM 0x58000000..0x5fffffff -> 0x58000000
ftpci100 50000000.pci: PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [bus 00-ff]
pci_bus 0000:00: root bus resource [io 0x0000-0xfffff]
pci_bus 0000:00: root bus resource [mem 0x58000000-0x5fffffff]
ftpci100 50000000.pci:
DMA MEM1 BASE: 0x0000000000000000 -> 0x0000000007ffffff config 00070000
ftpci100 50000000.pci:
DMA MEM2 BASE: 0x0000000000000000 -> 0x0000000003ffffff config 00060000
ftpci100 50000000.pci:
DMA MEM3 BASE: 0x0000000000000000 -> 0x0000000003ffffff config 00060000
PCI: bus0: Fast back to back transfers disabled
pci 0000:00:00.0: of_irq_parse_pci() failed with rc=-22
pci 0000:00:0c.0: BAR 0: assigned [mem 0x58000000-0x58007fff]
pci 0000:00:09.2: BAR 0: assigned [mem 0x58008000-0x580080ff]
pci 0000:00:09.0: BAR 4: assigned [io 0x1000-0x101f]
pci 0000:00:09.1: BAR 4: assigned [io 0x1020-0x103f]
pci 0000:00:09.0: enabling device (0140 -> 0141)
pci 0000:00:09.0: HCRESET not completed yet!
pci 0000:00:09.1: enabling device (0140 -> 0141)
pci 0000:00:09.1: HCRESET not completed yet!
pci 0000:00:09.2: enabling device (0140 -> 0142)
rt61pci 0000:00:0c.0: enabling device (0140 -> 0142)
ieee80211 phy0: rt2x00_set_chip: Info - Chipset detected -
rt: 2561, rf: 0003, rev: 000c
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ehci-pci 0000:00:09.2: EHCI Host Controller
ehci-pci 0000:00:09.2: new USB bus registered, assigned bus number 1
ehci-pci 0000:00:09.2: irq 125, io mem 0x58008000
ehci-pci 0000:00:09.2: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 4 ports detected
uhci_hcd: USB Universal Host Controller Interface driver
uhci_hcd 0000:00:09.0: UHCI Host Controller
uhci_hcd 0000:00:09.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:09.0: HCRESET not completed yet!
uhci_hcd 0000:00:09.0: irq 123, io base 0x00001000
hub 2-0:1.0: USB hub found
hub 2-0:1.0: config failed, hub doesn't have any ports! (err -19)
uhci_hcd 0000:00:09.1: UHCI Host Controller
uhci_hcd 0000:00:09.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:09.1: HCRESET not completed yet!
uhci_hcd 0000:00:09.1: irq 124, io base 0x00001020
hub 3-0:1.0: USB hub found
hub 3-0:1.0: config failed, hub doesn't have any ports! (err -19)
scsi 0:0:0:0: Direct-Access USB Flash Disk 1.00 PQ: 0 ANSI: 2
sd 0:0:0:0: [sda] 7900336 512-byte logical blocks: (4.04 GB/3.77 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] No Caching mode page found
sd 0:0:0:0: [sda] Assuming drive cache: write through
sda: sda1 sda2 sda3
sd 0:0:0:0: [sda] Attached SCSI removable disk
ieee80211 phy0: rt2x00lib_request_firmware: Info -
Loading firmware file 'rt2561s.bin'
ieee80211 phy0: rt2x00lib_request_firmware: Info -
Firmware detected - version: 0.8
IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
$ lspci
00:00.0 Class 0600: 159b:4321
00:09.2 Class 0c03: 1106:3104
00:09.0 Class 0c03: 1106:3038
00:09.1 Class 0c03: 1106:3038
00:0c.0 Class 0280: 1814:0301
$ cat /proc/interrupts
CPU0
123: 0 PCI 0 Edge uhci_hcd:usb2
124: 0 PCI 1 Edge uhci_hcd:usb3
125: 159 PCI 2 Edge ehci_hcd:usb1
126: 1082 PCI 3 Edge rt61pci
$ cat /proc/iomem
50000000-500000ff : /soc/pci@50000000
58000000-5fffffff : Gemini PCI MEM
58000000-58007fff : 0000:00:0c.0
58000000-58007fff : 0000:00:0c.0
58008000-580080ff : 0000:00:09.2
58008000-580080ff : ehci_hcd
The EHCI USB hub works fine; I can mount and manage files and the IRQs just
keep ticking up. I can issue iwlist wlan0 scanning and see all the WLANs
here. I don't have wpa_supplicant so have not tried connecting to them.
[bhelgaas: fold in %pap change from Arnd Bergmann <arnd@arndb.de>]
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
CC: Janos Laube <janos.dev@gmail.com>
CC: Paulius Zaleckas <paulius.zaleckas@gmail.com>
CC: Hans Ulli Kroll <ulli.kroll@googlemail.com>
CC: Florian Fainelli <f.fainelli@gmail.com>
CC: Feng-Hsin Chiang <john453@faraday-tech.com>
CC: Greentime Hu <green.hu@gmail.com>
Add device tree bindings for the Faraday technology PCI Host Bridge. This
IP is found in the Storlink/Storm/Cortina Gemini SoC platform.
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Acked-by: Rob Herring <robh@kernel.org>
CC: Janos Laube <janos.dev@gmail.com>
CC: Paulius Zaleckas <paulius.zaleckas@gmail.com>
CC: Hans Ulli Kroll <ulli.kroll@googlemail.com>
CC: Florian Fainelli <f.fainelli@gmail.com>
CC: devicetree@vger.kernel.org
CC: Feng-Hsin Chiang <john453@faraday-tech.com>
CC: Greentime Hu <green.hu@gmail.com>
Allow working IBSS also when working in DQA mode.
This is done by setting it to treat the queues the
same as a BSS AP treats the queues.
Fixes: 7948b87308 ("iwlwifi: mvm: enable dynamic queue allocation mode")
Signed-off-by: Liad Kaufman <liad.kaufman@intel.com>
Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
This is a static analysis fix. The warning is:
drivers/net/wireless/intel/iwlwifi/mvm/fw-dbg.c:912 iwl_mvm_fw_dbg_collect()
warn: integer overflows 'sizeof(*desc) + len'
I guess this code is supposed to take a NUL character, but if we write
zero bytes then it tries to write -1 characters and crashes.
Fixes: c91b865cb1 ("iwlwifi: mvm: support description for user triggered fw dbg collection")
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
ptep_notify and gmap_shadow_notify both need a guest address and
therefore retrieve them from the available virtual host address.
As they operate on the same guest address, we can calculate it once
and then pass it on. As a gmap normally has more than one shadow gmap,
we also do not recalculate for each of them any more.
Signed-off-by: Janosch Frank <frankja@linux.vnet.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
There is no need to always call blocking console_lock() in
console_cpu_notify(), it's quite possible that console_sem can
be locked by other CPU on the system, either already printing
or soon to begin printing the messages. console_lock() in this
case can simply block CPU hotplug for unknown period of time
(console_unlock() is time unbound). Not that hotplug is very
fast, but still, with other CPUs being online and doing
printk() console_cpu_notify() can stuck.
Use console_trylock() instead and opt-out if console_sem is
already acquired from another CPU, since that CPU will do
the printing for us.
Link: http://lkml.kernel.org/r/20170121104729.8585-1-sergey.senozhatsky@gmail.com
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Signed-off-by: Petr Mladek <pmladek@suse.com>
Access should be by rcu_dereference. Issue was found by sparse.
Fixes: 65e254821c ("iwlwifi: mvm: use firmware station PM notification for AP_LINK_PS")
Signed-off-by: Sara Sharon <sara.sharon@intel.com>
Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
A PCI_EJECT message can arrive at the same time we are calling
pci_scan_child_bus() in the workqueue for the previous PCI_BUS_RELATIONS
message or in create_root_hv_pci_bus(). In this case we could potentially
modify the bus from multiple places.
Properly lock the bus access.
Thanks Dexuan Cui <decui@microsoft.com> for pointing out the race condition
in create_root_hv_pci_bus().
Reported-by: Xiaofeng Wang <xiaofwan@redhat.com>
Signed-off-by: Long Li <longli@microsoft.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Acked-by: K. Y. Srinivasan <kys@microsoft.com>
hv_pci_devices_present() is called in hv_pci_remove() when we remove a PCI
device from the host, e.g., by disabling SR-IOV on a device. In
hv_pci_remove(), the bus is already removed before the call, so we don't
need to rescan the bus in the workqueue scheduled from
hv_pci_devices_present().
By introducing bus state hv_pcibus_removed, we can avoid this situation.
Reported-by: Xiaofeng Wang <xiaofwan@redhat.com>
Signed-off-by: Long Li <longli@microsoft.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Acked-by: K. Y. Srinivasan <kys@microsoft.com>
My email address may be found in the git commit logs and in MAINTAINERS.
Remove duplicate addresses so they won't have to be kept up-to-date.
Signed-off-by: Finn Thain <fthain@telegraphics.com.au>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
This patch fix spelling typos found in
Documentation/output/xml/driver-api/basics.xml.
It is because the xml file was generated from comments in source,
so I had to fix the comments.
Signed-off-by: Masanari Iida <standby24x7@gmail.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
There are repeated compiler flags "-Wall" in the Makefile.
The redundant compiler flag appears to have been there from the
introduction of the Makefile.
Signed-off-by: Chijun Sima <simachijun@qq.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
There is a new clone of the XIN MO arcade controller which has same issue with
out of range like the original. This fix will solve the issue where 2
directions on the joystick are not recognized by the new THT 2P arcade
controller with device ID 0x75e1. In details the new device ID is added the
hid-id list and the hid-xinmo source code.
Signed-off-by: Peter Stein <peter@stuntstein.dk>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Currently the slope and offset values for calculating the
hot spot temperature of a particular thermal zone is part
of driver data. Pass them here instead and obtain the values
while of node parsing.
Signed-off-by: Keerthy <j-keerthy@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
Currently the slope and offset values for calculating the
hot spot temperature of a particular thermal zone is part
of driver data. Pass them here instead and obtain the values
while of node parsing.
Signed-off-by: Keerthy <j-keerthy@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
Currently the slope and offset values for calculating the
hot spot temperature of a particular thermal zone is part
of driver data. Pass them here instead and obtain the values
while of node parsing.
Signed-off-by: Keerthy <j-keerthy@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
Currently the slope and offset values for calculating the
hot spot temperature of a particular thermal zone is part
of driver data. Pass them here instead and obtain the values
while of node parsing.
Signed-off-by: Keerthy <j-keerthy@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
