[Patch v2] firmware: qcom: scm: Convert to platform driver

This patch creates a platform driver for the SCM so that we can adequately manage resources. This removes clients having to carry the necessary clocks to use the SCM resources. Signed-off-by: Andy Gross --- .../devicetree/bindings/firmware/qcom,scm.txt | 25

[PATCH v1] scsi: ufs: add ioctl interface for query request

This patch exposes the ioctl interface for UFS driver via SCSI device ioctl interface. As of now UFS driver would provide the ioctl for query interface to connected UFS device. Signed-off-by: Dolev Raviv Signed-off-by: Noa Rubens Signed-off-by: Raviv

Re: [PATCH v4 2/5] mtd: nand: Qualcomm NAND controller driver

Hi, On 10/06/2015 02:47 PM, Brian Norris wrote: Hi Archit, On Mon, Oct 05, 2015 at 12:21:54PM +0530, Archit Taneja wrote: On 10/02/2015 08:35 AM, Brian Norris wrote: On Wed, Aug 19, 2015 at 10:19:03AM +0530, Archit Taneja wrote: The Qualcomm NAND controller is found in SoCs like IPQ806x,

Re: [PATCH v2 1/2] PM / Domains: Make pm_genpd_{add,remove}_subdomain() available to modules

On 10/05, Rafael J. Wysocki wrote: > On Thursday, October 01, 2015 12:22:53 PM Stephen Boyd wrote: > > > > /** > > * pm_genpd_remove_subdomain - Remove a subdomain from an I/O PM domain. > > @@ -1395,6 +1396,7 @@ out: > > > > return ret; > > } > >

Re: [PATCH v2 2/2] clk: qcom: Make oxili GDSC parent of oxili_cx GDSC

On 10/01, Stephen Boyd wrote: > The oxili_cx GDSC is inside the power domain of the oxili GDSC. > Add the dependency so that the CX domain can properly power up. > > Reported-by: Rob Clark > Cc: Rajendra Nayak > Signed-off-by: Stephen Boyd

Re: [PATCH] soc/qcom: add OCMEM driver

Hi Rob, > + > +struct ocmem_config { > + uint8_t num_regions; u8 > + uint32_t macro_size; u32 > +static const struct ocmem_config ocmem_8974_config = { > + .num_regions = 3, .macro_size = SZ_128K, > +}; > + > +static const struct of_device_id ocmem_dt_match[] = { > + {

[RFC v2 2/5] drm/dsi: Try to match non-DT dsi devices

Add a device name field in mipi_dsi_device. This name is different from the actual dev name (which is of the format "hostname.reg"). When the device is created via DT, this name is set to the modalias string. In the non-DT case, the driver creating the DSI device provides the name by populating a

[RFC v2 3/5] drm/dsi: Check for used channels

We don't check whether a previously registered mipi_dsi_device under the same host shares the same virtual channel. Before registering, check if any of the registered devices doesn't already have the same virtual channel. This wasn't crucial when all the devices under a host were populated via

[RFC v2 1/5] drm/dsi: Refactor device creation

Simplify the mipi dsi device creation process. device_initialize and device_add don't need to be called separately when creating mipi_dsi_device's. Use device_register instead to simplify things. Create a helper function mipi_dsi_device_new which takes in struct mipi_dsi_device_info and

Re: [RFC v2 5/5] drm/dsi: Get DSI host by DT device node

Hi Archit, [auto build test WARNING on v4.3-rc4 -- if it's inappropriate base, please ignore] reproduce: make htmldocs All warnings (new ones prefixed by >>): drivers/gpu/drm/i915/i915_irq.c:491: warning: No description found for parameter 'dev' drivers/gpu/drm/i915/i915_irq.c:2217:

Re: [PATCH v4 2/5] mtd: nand: Qualcomm NAND controller driver

Hi Archit, On Mon, Oct 05, 2015 at 12:21:54PM +0530, Archit Taneja wrote: > On 10/02/2015 08:35 AM, Brian Norris wrote: > >On Wed, Aug 19, 2015 at 10:19:03AM +0530, Archit Taneja wrote: > >>The Qualcomm NAND controller is found in SoCs like IPQ806x, MSM7xx, > >>MDM9x15 series. > >> > >>It exists

[RFC v2 5/5] drm/dsi: Get DSI host by DT device node

mipi_dsi_devices are inherently aware of their host because they share a parent-child hierarchy in the device tree. Non-dsi drivers that create a dummy dsi device don't have this data. In order to get this information, they require to a phandle to the dsi host in the device tree. Maintain a list

[RFC v2 4/5] drm/dsi: Add routine to unregister dsi device

A driver calling mipi_dsi_device_new might want to unregister the device once it's done. It might also require it in an error handling path in case something didn't go right. When the dsi host driver calls mipi_dsi_host_unregister, the devices created by both DT and and without DT will be

[RFC v2 0/5] drm/dsi: DSI for devices with different control bus

We are currently restricted when it comes to supporting DSI on devices that have a non-DSI control bus. For example, DSI encoder chips are available in the market that are configured via i2c. Configuring their registers via DSI bus is either optional or not available at all. These devices still

[PATCH] qcom-scm: add support to restore secure config

Needed by OCMEM driver. Signed-off-by: Rob Clark --- Note: no objections to the device-id enum on mailing list and positive feedback on ##linux-msm so squashing that part in and re-sending drivers/firmware/qcom_scm-32.c | 20

[PATCH] qcom-scm: add OCMEM lock/unlock interface

Needed to enable device access to OCMEM. Signed-off-by: Rob Clark --- Note: no objections to the client-id enum on mailing list and positive feedback on ##linux-msm so squashing that part in and re-sending drivers/firmware/qcom_scm-32.c | 34

Re: [PATCH] soc/qcom: add OCMEM driver

On Tue, Oct 6, 2015 at 4:35 AM, Stanimir Varbanov wrote: > Hi Rob, > > > >> + >> +struct ocmem_config { >> + uint8_t num_regions; > > u8 > >> + uint32_t macro_size; > > u32 tbh, only place where stdint types are potentially an issue is in uapi. I changed the