> -Original Message-
> From: devel [mailto:driverdev-devel-boun...@linuxdriverproject.org] On
> Behalf Of K. Y. Srinivasan
> Sent: Wednesday, April 29, 2015 9:00
> To: da...@davemloft.net; net...@vger.kernel.org; linux-
> ker...@vger.kernel.org; de...@linuxdriverproject.org; o...@aepfle.de;
From: Micky Ching
The new data structure for SD4.0 including follows:
register: SD4.0 IO space register define.
protocol: host and card handshake data.
tlp: tlp request data structure for SD4.0 mode.
uhsii ios: UHSII bus control data structure.
Signed-off-by: Micky Ching
Signed-off-by: Wei Wan
From: Micky Ching
SD4.0 operations include UHSII interface detect, go/exit dormant
and uhsii ios settings.
Signed-off-by: Micky Ching
Signed-off-by: Wei Wang
---
drivers/mmc/host/sdhci.c | 183 ++-
1 file changed, 182 insertions(+), 1 deletion(-)
d
From: Micky Ching
Skip clock control settings for UHSII mode. When card is in UHSII mode,
we only allow poweroff.
Signed-off-by: Micky Ching
Signed-off-by: Wei Wang
---
drivers/mmc/host/sdhci.c | 22 ++
1 file changed, 14 insertions(+), 8 deletions(-)
diff --git a/drivers
From: Micky Ching
Add support for SD4.0 card.
Signed-off-by: Micky Ching
Signed-off-by: Wei Wang
---
drivers/mmc/host/sdhci.c | 108 ---
1 file changed, 102 insertions(+), 6 deletions(-)
diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhc
From: Micky Ching
SD4.0 mode not using SDMA any more, and UHSII mode using different register
to specify block size/count.
Signed-off-by: Micky Ching
Signed-off-by: Wei Wang
---
drivers/mmc/host/sdhci.c | 22 +-
1 file changed, 17 insertions(+), 5 deletions(-)
diff --git
From: Micky Ching
Add support for SD4.0 card, which introduce UHSII mode and tlp transfer.
Micky Ching (12):
mmc: core: add data structure define for SD4.0
mmc: core: modify mmc_app_cmd interface for SD4.0
mmc: core: add SD4.0 operation function
mmc: core: add tlp request handler for SD4
From: Micky Ching
We alloc card before init card, if init UHSII mode failed, then
try to init legacy mode.
Since we card is allocated before do init operations, so mmc/sdio
card init should do some modify. To reduce many diff hunks, the old
labels are reserved(we can remove them in the future).
From: Micky Ching
SD4.0 mode using tlp for cmd/data transfer, add tlp functions to handle
this case.
Signed-off-by: Micky Ching
Signed-off-by: Wei Wang
---
drivers/mmc/host/sdhci.c | 244 ++-
1 file changed, 220 insertions(+), 24 deletions(-)
diff
From: Micky Ching
add SD4.0 register define and host data structure for
handshake with SD4.0 card.
Signed-off-by: Micky Ching
Signed-off-by: Wei Wang
---
drivers/mmc/host/sdhci.h | 136 ++-
1 file changed, 135 insertions(+), 1 deletion(-)
diff --gi
From: Micky Ching
We should not do power cycle when card is in SD4.0 mode,
if we power off, we should detect UHSII interface again.
so we can disable it when card is in UHSII mode.
Signed-off-by: Micky Ching
Signed-off-by: Wei Wang
---
drivers/mmc/core/core.c | 3 ++-
1 file changed, 2 insert
From: Micky Ching
when card is work in SD4.0 mode, we should send tlp instead of cmd.
add this function to handle tlp request.
Signed-off-by: Micky Ching
Signed-off-by: Wei Wang
---
drivers/mmc/core/core.c | 111 +---
1 file changed, 104 insertions(
From: Micky Ching
When card running in SD4.0 mode, ACMD is not need to send two command,
we only need to mark a flag for the CMD which is to be send.
Signed-off-by: Micky Ching
Signed-off-by: Wei Wang
---
drivers/mmc/card/block.c | 2 +-
drivers/mmc/core/sd_ops.c | 17 -
inc
From: Micky Ching
SD4.0 add some new operations, which include follows:
UHSII interface detect: when UHSII interface is detected, the power is up.
go/exit dormant: enter or exit dormant state.
device init: device init CCMD.
enumerate: enumerate CCMD.
config space read/write CCMD.
when we send S
Commit b08cc79155fc26d0d112b1470d1ece5034651a4b eliminated memory
allocation in the packet send path:
"hv_netvsc: Eliminate memory allocation in the packet send path
The network protocol used to communicate with the host is the remote ndis
(rndis)
protocol. We need to decorate each o
> -Original Message-
> From: Sergei Shtylyov [mailto:sergei.shtyl...@cogentembedded.com]
> Sent: Tuesday, April 28, 2015 11:27 AM
> To: KY Srinivasan; da...@davemloft.net; net...@vger.kernel.org; linux-
> ker...@vger.kernel.org; de...@linuxdriverproject.org; o...@aepfle.de;
> a...@canonic
Hello.
On 04/28/2015 04:14 AM, K. Y. Srinivasan wrote:
Commit commit b08cc79155fc26d0d112b1470d1ece5034651a4b eliminated memory
One "commit" is enough. :-)
And please also specify that commit's summary in parens.
allocation in the packet send path. This commit introduced a bug since i
- Migrated MC bus driver to use DPRC flib 0.6.
- Changed IRQ setup infrastructure to be able to program MSIs
for MC objects in an object-independent way.
Signed-off-by: J. German Rivera
---
drivers/staging/fsl-mc/bus/dpmcp-cmd.h | 79
drivers/staging/fsl-mc/bus/dprc-cmd.h
All the IRQs for DPAA2 objects in the same DPRC must use
the ICID of that DPRC, as their device Id in the GIC-ITS.
Thus, all these IRQs must share the same ITT table in GIC. As
a result, a pool of IRQs with the same device Id must be
preallocated per DPRC (fsl-mc bus instance). So, the fsl-mc
bus o
- Refactored fsl_mc_io object to have a DPMCP object attached to it
- Created DPMCP object for DPRC's built-in portal, so that waiting
on MC command completions for MC commands sent on the DPRC's built-in
portal can be done using a DPMCP interrupt and a Linux completion
variable. For most ca
When a child DPRC is bound to the vfio_fsl_mc driver via driver_override,
its own children should not be bound to corresponding host kernel
drivers, but instead should be bound to the vfio_fsl_mc driver as
well.
Currently, when a child container is scanned by the vfio_fsl_mc driver,
child devices
From: Bharat Bhushan
This patch is required for vfio-fsl-mc meta driver to successfully bind
layerscape container devices for device passthrough. This patch adds
a mechanism to allow a layerscape device to specify a driver rather than
a layerscape driver provide a device match.
This patch is bas
Add a locking mechanism to serialize mc_send_command() calls that use
the same fsl_mc_io object (same MC portal). All mc_send_command() calls
with the same fsl_m_io object have to be either from non-atomic context
or from atomic context, but not both. When the fsl_mc_io object is
created the owner
This patch series includes new functionality for the Freescale fsl-mc
bus driver.
Patch 1: MC bus IRQ support
Patch 2: add device binding path 'driver_override'
Patch 3: Propagate driver_override for a child DPRC's children
Patch 4: Upgraded MC bus driver to match MC fw 7.0.0
Patch 5: Allow the MC
If the lpi-parent property is not present in the fsl,qoriq-mc node
of the device tree, the MC bus driver will assume that the GIC is not
supported.
This change is made in order to be able to use the MC bus driver in a
KVM VM, without having GIC-ITS support in guests. Added function
fsl_mc_interrup
On Mon, Apr 27, 2015 at 02:36:53PM +, Teddy Wang 王力强 wrote:
> The image->depth != 1 case means the image is color.
>
> The current driver only does 2d in mono color image. I think we can let the
> driver fall back to cfb_imageblit() currently. Then we implement the color
> image 2d later.
>
drivers/staging/media/bcm2048/radio-bcm2048.c: In function
'bcm2048_i2c_driver_probe':
drivers/staging/media/bcm2048/radio-bcm2048.c:2596:11: warning: variable
'skip_release' set but not used [-Wunused-but-set-variable]
int err, skip_release = 0;
^
Signed-off-by: Mauro Carvalho Cheh
On Tuesday 28 April 2015 09:03:41 Mauro Carvalho Chehab wrote:
> drivers/staging/media/bcm2048/radio-bcm2048.c: In function
> 'bcm2048_i2c_driver_probe':
> drivers/staging/media/bcm2048/radio-bcm2048.c:2596:11: warning: variable
> 'skip_release' set but not used [-Wunused-but-set-variable]
> in
On Tue 2015-04-28 09:03:41, Mauro Carvalho Chehab wrote:
> drivers/staging/media/bcm2048/radio-bcm2048.c: In function
> 'bcm2048_i2c_driver_probe':
> drivers/staging/media/bcm2048/radio-bcm2048.c:2596:11: warning: variable
> 'skip_release' set but not used [-Wunused-but-set-variable]
> int err,
Gentle ping for feedback - some of our future work depends on this and
we would like to know whether this has a chance of being accepted?
On 04/14/2015 08:36 PM, Lauri Peltonen wrote:
Modify sync_fence_create to accept a 'struct fence' instead of
'struct sync_pt'. This will allow drm drivers t
30 matches
Mail list logo
