From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maxime Coquelin Subject: Holes management in syscon driver Date: Thu, 25 Sep 2014 18:44:05 +0200 Message-ID: <54244655.1090801@st.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Return-path: Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Dong Aisheng , "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" , "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" Cc: Seraphin BONNAFFE , Lee Jones , Samuel Ortiz , Grant Likely , Rob Herring List-Id: devicetree@vger.kernel.org Hi Dong, all, We use syscon driver on our STi platforms to manage our system config registers. We declare one syscon instance per sysconf bank. The problem we are facing is that these banks have holes, and when using regmap's debugfs interface to dump the registers, we get imprecise aborts. My first idea would be do implement the .readable_reg and .writeable_reg callbacks offered by regmap in syscon driver, and provide ranges where there are registers via DT. But I am not sure how would look the DT bindings. What is your view on this? Are other syscon users having the same issue? Regards, Maxime -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html